'decisions' 검색 결과

Turn saved regression decisions into evidence-linked HTML, Markdown, and JSON reports. Validate records and coverage, preserve assigned ratings, and distinguish confirmed defects from existing bugs, rejected claims, and unresolved work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Compile saved decisions into a regression report
• Refresh reports after evidence or decisions change
• Review coverage gaps and unresolved findings

Save decisions, research findings, and work updates to Obsidian, then update related notes, daily entries, and task boards. Maintain existing pages, preserve changing facts with their history, and check for duplicates and broken links.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Save decisions and tasks from a conversation
• Connect development logs to project notes
• Check a vault for duplicates and broken links

Two-layer memory for executive decisions, separating raw deliberation from approved decisions to prevent hallucinated consensus. Use when logging decisions, reviewing past decisions, or checking overdue action items.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage per-feature living documents that capture decisions, constraints, and reasoning across AI sessions during active development. Scoped to feature-level work — design, implementation, bugfix, refactor — not for codebase-wide assessments or product-wide specifications (those define their own document lifecycles). Handles creating new context documents, loading existing ones, and enriching them with new decisions. Use when starting a new feature, resuming work, making technical decisions, resolving questions, or when context needs to persist across sessions. Use this skill whenever the user mentions 'load context', 'update context', 'context doc', 'decisions', 'continue where we left off', 'what did we decide', or 'capture this decision'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Determine technologies needed to build the product, making build/buy/integrate decisions during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on requests to select tech stack, evaluate technologies, make build vs. buy decisions, discover existing assets, or when user asks "what technologies?", "select tech stack", "build or buy?", "what do we reuse?", "existing stack", "technical decisions", "what tools do we need?", "evaluate solutions". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and trade-offs. Feeds v0.6 Architecture Design.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Update a product spec from a meeting transcript — extract decisions, open questions, spec changes, and flowchart updates. Use this skill when: - A meeting discussed changes to a product spec and you need to update the local .md + wiki page - The user shares a meeting URL or transcript ID and says "update the spec" - The user says "what needs to change in the spec from this meeting" - After processing a meeting, when decisions affect a spec's content (not just action items) Trigger phrases: "update spec from meeting", "what changed in the spec", "meeting to spec", "sync meeting decisions to spec", "add meeting decisions to spec"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Maintain clear business definitions and relationships in an existing glossary or CONTEXT.md. Flag unresolved meanings and refer lasting design choices to the existing architecture decision record workflow, keeping terminology separate from decision rationale and task status.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Document business terms that need repeated explanation
• Clarify terms with multiple meanings
• Track domain interpretations awaiting confirmation

제품 요청과 기획서를 개발에 필요한 구체적인 요구 사항으로 정리합니다. 업무 규칙, 데이터 소유권, 서비스 간 접점과 미결 사항을 문서로 남겨 다음 담당자에게 전달합니다.

• 제품 요구 문서를 개발 요구 사항으로 정리
• 여러 서비스에 걸친 기능 요구 사항 정리
• 검토 때마다 확인하는 전제 문서화

상품 반품 접수부터 검수, 환불, 재판매와 폐기 판단까지 지원합니다. 부정행위 징후, 보증 청구, 공급업체 비용 회수도 포함해 대응 방침을 정리합니다.

• 반품 접수 조건과 환불 방침을 확인할 때
• 반품 상품의 상태와 처리 경로를 정할 때
• 비정상적인 반품 패턴을 조사할 때

회의 메모나 전사문에서 근거가 있는 결정 사항과 담당자·기한을 정리합니다. 기존 작업과 중복을 확인하고 회의록, 티켓, 후속 메시지 초안을 만듭니다.

• 회의 메모에서 작업 추출
• 결정 사항과 담당자·기한 확인
• 회의 약속과 기존 작업 대조

설계 결정의 이유와 비교한 대안을 기록하고 README, API 문서, 변경 이력을 정리합니다. 새 담당자와 AI 에이전트가 구현 배경을 이해하도록 돕습니다.

• 설계 결정과 채택하지 않은 대안 기록
• 공개 API 변경 문서화
• README의 시작 절차 정리

Paperclip의 이슈, 댓글, 문서를 읽고 프로젝트 현황, 결정 사항, 위험과 다음 행동을 설명하는 위키 페이지로 정리하며 기존 지식을 갱신합니다.

• 최근 활동을 위키에 정리
• 과거 활동으로 위키 구축
• 결정 사항과 근거 기록

여러 AI 에이전트의 지식과 판단을 모아 공유 메모리를 동기화하고 전문성을 반영한 투표로 합의를 이끌어 냅니다. 작업 부하 분산과 판단 이력 기록도 다룹니다.

• 여러 에이전트의 의견 취합
• 에이전트 사이의 지식 동기화
• 담당별 작업 부하 분산

Revise an existing OpenSpec change plan and reconcile related planning documents. Incorporate new decisions, identify contradictions or gaps, and apply proposed document edits after confirmation, while leaving implementation code untouched.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Incorporating new decisions into an existing change plan
• Checking planning documents for contradictions
• Reconciling related documents after an edit

Work through project decisions one question at a time, with a recommendation and brief reasoning. Record each settled answer immediately in project documentation, keeping unresolved questions visible and documents marked as drafts until explicitly accepted.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarify goals and boundaries before implementation
• Record decisions as an interview progresses
• Preserve decisions when discussions are interrupted

Search and read Slack messages, channels, and threads to catch up on team discussions and decisions. Using the installed CLI and Slack’s official MCP server, it also supports channel posts and replies, with approval required for changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Catch up on team discussions
• Find messages about past decisions
• Post updates to a channel

Review Zoom meetings, calls, recordings, and transcripts to catch up on discussions and extract decisions, action items, and owners. Use Zoom's official connections to manage meetings and access supported chat, document, task, and whiteboard features.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Catch up on a missed meeting from recordings or transcripts
• Extract decisions, action items, and owners
• Create, update, or delete Zoom meetings

Organize treatment decisions already supplied and verified by authorized licensed professionals into local JSON documents. Check document structure, source references, declared review status, and supplied dates to support documentation handoffs without making clinical decisions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Organize verified clinician-authored treatment records
• Check source references and missing documentation fields
• List checkpoint dates already supplied by clinicians

Use Hindsight to recall past context, save reusable facts, and reason across accumulated memories. Supports continuity between conversations by preserving preferences, project decisions, and lessons learned, while helping explain the reasoning behind earlier choices.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Resuming earlier work with relevant context
• Saving lasting preferences and project decisions
• Reviewing the reasons behind past decisions

Retrieve relevant Hindsight memories before planning or answering a request. Searches the agent’s own and shared memory stores, plus other relevant stores when needed, to bring past decisions, user preferences, and project context into the task.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking past decisions before planning work
• Answering with previously recorded user preferences
• Finding context saved by other Bots or AI tools

Find context from past coding sessions in Hindsight long-term memory. Reuse memories already loaded for the session, search for missing details, and reason over accumulated records when answering questions about decisions, project context, or preferences.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Revisit the reasons behind past implementation decisions
• Recover project context discussed in earlier sessions
• Check previously discussed preferences

Document major technical choices as Architecture Decision Records, or ADRs. Capture the context, alternatives, reasons, and consequences, then organize related records and track whether decisions are proposed, accepted, retired, or replaced.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording reasons for choosing a framework or database
• Comparing design options and their trade-offs
• Sharing past decisions with new team members

Make system architecture decisions by clarifying requirements and constraints, comparing benefits and drawbacks, and considering simpler alternatives. Record the reasoning in ADRs, architecture decision records, so significant choices and their rationale are documented.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying requirements before system design
• Comparing architecture patterns
• Documenting decisions and rationale in ADRs

Give an agent rules for consulting long-term memory before work and saving decisions, corrections, and failures afterwards. It helps carry preferences and project conventions across sessions while preserving dated history and making conflicting memories visible.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Carry preferences and project conventions across sessions
• Record user corrections for future tasks
• Preserve the history of changed decisions