「decision」の検索結果

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a user wants to create, write, name, place, or organize an Architecture Decision Record (ADR) in a software project — e.g. "write an ADR for choosing a database", "document this architecture decision", "set up an adr/ or decisions/ directory", "which ADR template should I use", "supersede an old ADR". Covers picking a template, naming the file, filling in context/decision/consequences, and deciding whether a decision even needs an ADR.

日本語の概要は準備中です。原文の説明を表示しています。

Run a decision asynchronously — the memo, the silent-read window, the comment protocol, and the deadline that makes it land without a meeting. Use when asked to decide something async, replace a decision meeting with a document, run an Amazon-style written decision process, or when a decision keeps stalling in comment threads. Produces the decision memo plus the process wrapper: reader roles, response windows, comment-resolution rules, and the tie-breaker. For the document structure alone use decision-memo; this skill runs the process around it.

日本語の概要は準備中です。原文の説明を表示しています。

RAID log methodology with decision extraction from emails and meeting notes. Use when asked to identify risks, log assumptions, track issues, extract decisions from correspondence, create or update a RAID log, escalate a risk to an issue, assess project risks, validate or challenge assumptions, or capture scope-relevant decisions. Also triggers when the user pastes email chains and asks what decisions were made, or needs to find buried decisions and untested assumptions in correspondence. Trigger on: 'risk report', 'RAID log', 'what are the risks', 'what decisions were made', 'update the risk register', 'what assumptions are we making', 'what could go wrong', 'flag any issues', 'extract decisions from these emails'.

日本語の概要は準備中です。原文の説明を表示しています。

Manages GDPR Article 22 rights related to solely automated decision-making and profiling, including identification of automated decisions, meaningful human oversight implementation, logic explanation requirements, and contestation mechanisms. Activate for automated decision, profiling, Art. 22, algorithmic decision, AI decision queries.

日本語の概要は準備中です。原文の説明を表示しています。

Expert in decision-making frameworks - systematic approaches to making better decisions under uncertainty. Covers decision criteria, reversibility assessment, stakeholder alignment, and decision documentation. Knows when to decide fast and when to deliberate. Use when "decision framework, how to decide, making a choice, tradeoff, should we, pros and cons, decision matrix, weighing options, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Erzeugt aus einem Bestand offener und gefallener Entscheidungen einen strukturierten ASCII-Abhängigkeitsgraphen (maximal 100 Spalten) für das Terminal. Bewertet Knoten nach fünf festen Kriterien: sinnvoll, empfohlen, usertypisch (Richtung und decision-avatar-Konfidenz getrennt), zusammenpassend und widersprechend; Kanten tragen Beziehungstyp und Belegstatus. Deckt Blocker, Freischaltungen, Reihenfolgen und widersprüchliche Empfehlungen gnadenlos auf. Nutze diesen Skill bei "welche Entscheidungen hängen voneinander ab", "Abhängigkeitsgraph der Entscheidungen", "Entscheidungspfad visualisieren", "Widersprüche zwischen Entscheidungen prüfen", "Reihenfolge der Beschlüsse", /decision-path. NICHT nutzen, um Entscheidungen erst zu inventarisieren -- das macht decision-briefing; NICHT nutzen, um das empfohlene Gesamtkonzept zur Abnahme zu bündeln -- das macht decision-draw; NICHT für kompakte Fünfteiler- Einzelblöcke mit Optionen und Pro/Contra -- das macht decision-shot; NICHT für die Einzelfall-Erwägung mit Frameworks -- das macht decide.

日本語の概要は準備中です。原文の説明を表示しています。

Verdichtet gebündelte offene Entscheidungen zu EINEM zusammenhängenden, prosa-basierten Gesamtkonzept auf Basis aller empfohlenen Varianten. Zeigt, wie die Teilsysteme nach der Umsetzung konkret ineinandergreifen, statt den Nutzer durch Dutzende isolierte Einzelfragen zu zwingen. Der Nutzer nimmt das Bild als Ganzes ab oder gibt zielgerichtete Korrekturen, die automatisch in Einzelentscheidungen übersetzt und über decision-briefing Phase 4 ins Register zurückgeschrieben werden. Nutze diesen Skill bei "wie sieht das Ganze aus wenn wir allem zustimmen", "zeichne mir das Gesamtbild", "Gesamtkonzept der Entscheidungen", "decision draw", /decision-draw, "wie greifen die Systeme zusammen". NICHT nutzen, wenn Alternativen pro Einzelpunkt diskutiert werden sollen -- das macht decision-briefing; NICHT für den Abhängigkeitsgraphen -- das macht decision-path; NICHT für strukturierte Einzelblöcke mit Optionen und Pro/Contra (auch bei eng zusammengehörigen Gruppen) -- das macht decision-shot; NICHT zur Herleitung einer einzelnen Entscheidung -- das macht decide.

日本語の概要は準備中です。原文の説明を表示しています。

Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working ON the joelparkerhenderson/architecture-decision-record repository itself (this repo) — adding or editing a decision-record template, example, tool/guardrail link, or translation; reviewing a contributor's PR against it; or keeping README.md and locales/en-001/ in sync. Not for writing an ADR for some other project — use architecture-decision-record-skill for that.

日本語の概要は準備中です。原文の説明を表示しています。

Architecture Decision Records workflow skill. Use this skill when the user needs Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

Architecture Decision Records workflow skill. Use this skill when the user needs Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you want to generate Architecture Decision Records from this session. Triggers on "write ADRs", "document our decisions", "create decision records", "record the choices we made". Also useful after design discussions where decisions were reached but not documented. Does NOT extract decisions alone (use adr-decision-extraction) or provide MADR template (use adr-writing). Orchestrates the full workflow: subagent extraction, user confirmation, parallel generation, and verification.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you need to mine a conversation, session transcript, or design discussion for architectural decisions before writing ADRs. Identifies problem-solution pairs, trade-off debates, technology choices, and explicit "[ADR]" tags. Triggers on "what decisions did we make", "extract decisions from this chat", "find the choices in our discussion", or "summarize architectural decisions". Also useful after long planning sessions to capture decisions that were made implicitly. Does NOT write ADR documents — use adr-writing or write-adr for that.

日本語の概要は準備中です。原文の説明を表示しています。

Structured approaches to decisions under uncertainty and complexity. Covers expected value, decision trees, multi-criteria decision analysis, System 1 vs System 2 allocation, pre-mortems, reversible vs irreversible decisions, and the distinction between good decisions and good outcomes. Use when choosing among alternatives with uncertain or multi-dimensional consequences, especially when the stakes justify a deliberate rather than intuitive process.

日本語の概要は準備中です。原文の説明を表示しています。

Architecture Decision Records (ADR) — a lightweight method for capturing important architectural decisions with context, trade-offs, and rationale. Based on Michael Nygard's ADR pattern and Google/Meta/ByteDance's design documentation culture. USE WHEN: deciding between technology choices, designing new architecture, changing existing architecture, documenting why a decision was made, onboarding new team members, or preserving design context for future maintainers. Triggered by terms like "tech choice", "architecture decision", "why did we choose", "design rationale", "ADR", or "architectural decision record".

日本語の概要は準備中です。原文の説明を表示しています。

Writes an architecture decision record (ADR) for a decision the team has already reached: the context, the options weighed, the choice and its consequences. Use when the user says "record this decision", "write an ADR", "we decided X, capture it", or asks to document a technical choice already made. Not for making the decision itself or for tracking the work it leads to.

日本語の概要は準備中です。原文の説明を表示しています。

Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.

日本語の概要は準備中です。原文の説明を表示しています。

[omh] Previously rejected options to revisit: recall scoped reviewed rejected decisions without elevating them to approved memory. Use when the user says: decision-recall, rejected decision recall, rejected decisions, why was this rejected, previously rejected alternative, 거절된 결정, 기각된 대안.

日本語の概要は準備中です。原文の説明を表示しています。

Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.

日本語の概要は準備中です。原文の説明を表示しています。

Run a family meeting to make a big care decision together — so it's a shared, informed decision instead of a fight or one person deciding alone. Use when asked help me run a family meeting about care, we need to decide together about mom's care, my siblings and I disagree about our parent, or facilitate a care decision. Produces an agenda and structure for the meeting, how to prepare (facts, options, everyone's input), ground rules to keep old family dynamics from derailing it, how to include the person being cared for, ways to work through disagreement toward a decision, and clear next steps with owners — turning an emotional, conflict-prone conversation into a productive one. Not legal, medical, or financial advice.

日本語の概要は準備中です。原文の説明を表示しています。