'decision' 검색 결과

Write architecture decision records, short documents explaining a software design choice, its context, and its consequences. It helps decide what deserves a record, select a template, organize files, and link replacement decisions to earlier records.

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

• Record why a database or library was chosen
• Set up a directory for decision records
• Choose an ADR template that fits the decision

Keeps board meeting transcripts separate from founder-approved decisions, with owners, deadlines, and action items. Supports decision searches, overdue reviews, and conflict checks so later meetings can refer to approved outcomes without treating rejected proposals as agreements.

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

• Recording approved decisions after a board meeting
• Finding past decisions by topic or owner
• Reviewing upcoming and overdue action items

Turns one decision discussion (meeting transcript, chat thread, email chain or notes) into a DRAFT one-page decision memo: the decision as stated, status, options considered, evidence cited, dissent recorded verbatim, owner, effective date and review date, with UNKNOWN for anything the discussion did not settle. Use when the user asks to "write up the decision", "record what we decided", "capture the decision from this thread", "draft the decision memo" or "add this to the decision log". Do not use for full minutes or action items, use transcript-to-actions instead; for a technical design decision, use architecture-decision-record; for a paper seeking a decision not yet taken, use board-paper-skeleton. Drafts for human review; never approves, authorises or signs off.

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

Write and maintain Architecture Decision Records (ADRs), documents explaining important technical choices. Capture the context, options, decision, and consequences, then organize records and track their status so teams can revisit the reasoning.

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

• Record the reasons for choosing a framework or database
• Document design options and their trade-offs
• Explain past technical decisions to new team members

Record founder-approved decisions with chosen options, success measures, stop conditions, and dissent. Keep approved decisions separate from discussion transcripts so future advisory sessions use confirmed choices, with a review scheduled after 90 days.

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

• Recording an approved management decision
• Preserving dissent and stop conditions
• Scheduling a decision review after 90 days

Document a technical decision in an architecture decision record, or ADR. Capture its context, alternatives, and consequences, assign a record number, and distinguish a proposed decision from an accepted one so dependent work reflects its actual status.

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

• Recording the reasons behind a technical choice
• Documenting alternatives and consequences of a design decision
• Creating numbered records alongside existing architecture decisions

Records an architecture decision as a Nygard/MADR-shaped ADR under decisions/ — capturing the context that forced the choice, the options weighed, the decision itself, and its consequences in both directions, plus the supersedes chain that keeps a decision log honest. Read when asked to record an architecture decision, write an ADR, log the decision we made, document why we chose X over Y, capture this decision for the record, or supersede an old decision with a new one. Do NOT read to frame a proposal or explore an idea not yet decided (frame-a-proposal), to write a spec or implementation plan (write-a-spec), to write an incident postmortem (write-a-postmortem), or to judge whether a design is sound (review-a-design). This skill records a decision already made; it does not make one.

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

Drafts an architecture or design decision record (ADR) from the discussion notes, design review minutes, chat threads and diagram descriptions the user provides: context, decision drivers, options considered with arguments as stated, the decision as the group worded it, consequences and a review date, with every factual claim tagged evidenced, asserted or UNKNOWN so unsupported claims are marked for the author to substantiate. Use when the user asks to "write an ADR", "document the architecture decision", "record why we chose this design", "turn these design review notes into a decision record" or "draft the design decision log entry". Do not use for a business or governance decision with no technical design, use decision-memo-builder instead; for the change ticket that implements the decision, use change-request-pack. Drafts for human review; never approves, authorises or signs off.

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

Review an executed business decision against its original success and stopping criteria. Compare actual results, revisit assumptions and dissenting views, and create a retrospective record with lessons and follow-up actions.

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

• Reviewing a decision at its 90-day checkpoint
• Assessing a decision when stopping criteria are triggered
• Examining why a major decision was reversed

Maintain a collection of architecture decision record templates, examples, translations, and tool links. It explains which files to update for each contribution and how to review pull requests for completeness, consistent formatting, and relevant content.

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

• Add an ADR template to the collection
• Add a worked decision record example
• Update links to ADR tools and pull request checks

When you have a decision to make and want a structured workflow that picks the load-bearing questions, walks through them, reaches a call (or "wait"), and archives the rationale for future reference. Based on the 37signals Guide to Making Decisions (38 questions) plus house additions like Q39 opportunity cost ("what does saying yes displace?"). Triages to 6–8 relevant questions per decision instead of forcing the full set. Archives every decision to ~/.config/makerskills/decide/archive/ with a revisit date so you can check later whether the call was right. Triggers on "/decide," "help me decide," "should I [X]," "I need to make a decision about," "stuck on a decision," "deciding between," "go/no-go on," "what should I do about." This is both the decision-making workflow AND the decision log — making the decision is the act of logging it.

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

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

Document major technical decisions with their context, alternatives, reasoning, and consequences. The skill provides Architecture Decision Record templates and maintenance practices so teams can review past choices, track replacements, and explain decisions to new members.

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

• Recording reasons for technology choices
• Comparing design options and trade-offs
• Explaining past decisions to new team members

Set a cooling-off period for an approved strategic decision, keeping it out of repeated debate until expiry or a defined exception. It records freeze dates and early-release reasons so later reviews can trace changes.

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

• Holding a fundraising decision steady for a set period
• Preventing repeated debate after a pricing decision
• Preserving a decision made after a divided board vote

Route business questions to relevant executive advisor roles, coordinate discussions across multiple functions, and combine their findings into clear agreements, disagreements, and action items. Record decisions and flag approved decisions that are due for review.

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

• Comparing fundraising with spending cuts
• Reviewing decisions across several business functions
• Clarifying conflicting advisor opinions

Trace a decision through recorded discussions and later revisions. Build a dated account of proposals, confirmed choices, rejected alternatives, and remaining questions, keeping suggestions separate from final decisions and showing disagreements between sources.

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

• Find the recorded reasons behind a decision
• Review alternatives that were rejected
• Trace later changes to a decision

기술이나 설계를 선택한 이유를 배경, 대안, 영향과 함께 Markdown으로 기록합니다. 일련번호와 색인으로 정리하고 기존 기록에서 과거 판단의 근거도 찾습니다.

• 프레임워크나 데이터베이스 선택 이유 기록
• 설계 대안과 장단점 정리
• 과거 기술 결정의 근거 확인

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

Review and rewrite architecture decision records, documents that explain design choices, from a newcomer’s perspective. Identify missing context, buried decisions, and temporary details, then reorganize each document so future readers can follow the reasoning.

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

• Reviewing design decisions from a new team member’s perspective
• Making an ADR’s decision and reasoning easier to follow
• Removing temporary project context from long-lived records

Turn an unclear idea into linked decision tickets on a repository’s issue tracker. Work through one decision per session, record outcomes and dependencies, and prepare a brief defining the objective, scope, and exclusions for delivery.

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

• Clarifying the destination of an early idea
• Mapping decisions and their dependencies
• Resuming unresolved decisions across sessions

Maintain Composio's documentation site and record documentation decisions. Work on content, Fumadocs configuration, changelogs, automation prompts, and review guidance, including ADR-style records that capture decisions and their rationale.

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

• Update Composio documentation content and changelogs
• Revise Fumadocs settings and documentation automation prompts
• Record or update documentation decisions

Turn an approved decision into a 90-day execution plan with weekly milestones, named accountable owners, review meetings, dependencies, and risks. The plan preserves the decision’s success measures and criteria for stopping the work.

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

• Turning an approved decision into a quarterly plan
• Assigning owners and weekly milestones
• Setting progress reviews and stopping criteria

Trace changes in a game design document to related architecture decision records, which explain technical choices. Compare their assumptions with the revised design, report which decisions need review, and guide updates to decisions and requirement links.

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

• Checking architecture impact after changing game design
• Finding technical decisions based on outdated requirements
• Choosing whether to keep, revise, or replace a decision

Work through major choices such as changing jobs, moving, or choosing a partner using simple decision rules. Examine whether to decline an uncertain opportunity, compare equally viable options, and reserve time for decisions with lasting consequences.

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

• Working through a major career or relocation decision
• Reconsidering a choice after a pros-and-cons list fails
• Comparing two equally viable options