decide-adr
Use to record a post-hoc or asynchronous architecture decision as a MADR ADR when it was NOT captured during the synchronous design pass — a choice made in code, in a chat, on a whiteboard, or one a tasks/review gate flagged as missing. Triggers on "ADR for {decision}", "adr for {slug}", "document the decision on {topic}", "lock in the decision about {X}", "MADR for {topic}", "/sdd:decide-adr {slug} {title}", "створи ADR для рішення", "задокументуй рішення", "ADR на {тему}". Confirms the decision is ADR-worthy via the blast-radius gate, picks the next 4-digit number, copies design's MADR template, and fills context / drivers / considered options / outcome / honest consequences. Supports a Proposed → Accepted review flow. Output: docs/features/{slug}/adr/NNNN-{title}.md. For decisions made live with the user, use `design` — it spawns ADRs inline (Accepted).
genkovich · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add genkovich/sdd --skill decide-adr技能说明
name: decide-adr
model: inherit
effort: high
agents: []
description: >
Use to record a post-hoc or asynchronous architecture decision as a MADR ADR when it
was NOT captured during the synchronous design pass — a choice made in code, in a chat,
on a whiteboard, or one a tasks/review gate flagged as missing. Triggers on "ADR for
{decision}", "adr for {slug}", "document the decision on {topic}", "lock in the decision
about {X}", "MADR for {topic}", "/sdd:decide-adr {slug} {title}", "створи ADR для рішення",
"задокументуй рішення", "ADR на {тему}". Confirms the decision is ADR-worthy via the
blast-radius gate, picks the next 4-digit number, copies design's MADR template, and
fills context / drivers / considered options / outcome / honest consequences. Supports a
Proposed → Accepted review flow. Output: docs/features/{slug}/adr/NNNN-{title}.md.
For decisions made live with the user, use design — it spawns ADRs inline (Accepted).
Skill: decide-adr
The post-hoc / asynchronous ADR path (pipeline stage 8a). design spawns ADRs synchronously and Accepted while you walk it Socratically; decide-adr records a decision that missed that pass — already in code, agreed in a chat, sketched on a whiteboard, or flagged by a tasks/review gate as a contract with no ADR behind it. It can also run a Proposed → Accepted review flow when the decision still needs a reviewer's sign-off. One file = one decision; it reuses design's MADR template, so there is no second ADR format here.
It is a recording utility, not a Socratic design stage — it does not run the shared Socratic loop or critic. The two shared dependencies are question phrasing and the worthiness gate:
→ ../_shared/ask-style.md · ../design/references/blast-radius.md
ADR prose (context / drivers / consequences) follows artifact_language — the MADR headings and Status: values (Proposed / Accepted / …) stay English → ../_shared/artifact-language.md.
Owner
Decision author (usually the Architect or Tech Lead). A reviewer (Tech Lead, plus Security when relevant) signs off the Proposed → Accepted transition.
Inputs
<slug>— the feature slug, same as every earlier stage.<title>— kebab-case, describes the decision, not the problem (time-sortable-ids, notid-strategy).- The decision itself + its alternatives — pulled from
sad.md§4 Solution strategy / §9 ADR index / §11 Risks, or supplied by the user. - Input gate (soft). Expects
docs/features/<slug>/to exist, ideally withsad.md(decide-adr reads its §4/§9/§11 for context and drivers). If the decision is genuinely standalone — no feature folder yet — allow it, but note the missing design context in the ADR's Context section and warn the user, rather than refusing.
Protocol
- Locate the feature.
test -d docs/features/<slug>. Missing → ask whether to proceed standalone (AskUserQuestion, phrasing per../_shared/ask-style.md). On «yes», createdocs/features/<slug>/adr/and flag that design context is absent.sad.mdpresent → read its §4 (strategy), §9 (existing ADR index), §11 (risks); absent → note it and source context from the user. - Worthiness check. Score the decision against the blast-radius gate —
../design/references/blast-radius.md(irreversible / multi-module / has legitimate alternatives). 2-of-3 → proceed. Below the bar → tell the user it's likely inline-in-sad.mdmaterial, not an ADR, and confirm before writing one anyway. - Dedup.
ls docs/features/<slug>/adr/*.md 2>/dev/null. An Accepted ADR on the same topic exists → don't duplicate: propose either editing it or a new ADR that marks the old oneSuperseded by NNNN(and stamps the old one'sstatus+updated_at). - Pick the number.
NNNN= (count of existingadr/*.md) + 1, zero-padded to 4 digits (0001,0002, …). Never reuse a number. - Copy the template. Copy
../design/templates/adr.md→docs/features/<slug>/adr/NNNN-<title>.md. This is the canonical MADR shape, owned bydesignand referenced here — do not invent a variant. Patch frontmatter:owner,updated_at: <today>,feature_size(from.sizeif present),ticket. - Context. 2–4 sentences: what forced this decision (an NFR, an incident, a constraint), and — if
sad.mdis absent — an explicit note that there is no design document, so the context is reconstructed from the author. - Decision drivers. Bullets — the quality goals / constraints that pushed the choice, each traceable to a real source (spec §6 NFR, sad.md §2 Constraints, a §1 top-3 quality goal). Don't invent drivers; they filter out pet decisions.
- Considered options. List all serious options (≥2 — one option is a declaration, not a decision), one line each with its trade-off. No strawman (an option an existing constraint already rules out).
- Decision outcome. «Chosen: » + 1–2 sentences on why it won, citing the drivers above.
- Consequences. Positive and Negative and Neutral — cons included, or it's rationalisation, not a record. Name what changes in the codebase, ops, monitoring, onboarding.
<!-- TBD -->only where a number honestly needs a spike. - Status.
Proposedwhile a reviewer still has to sign off;Acceptedonce final. Run the review flow when needed: writeProposed, fillreviewers, and on sign-off flip toAcceptedand bumpupdated_at. A reader six months on must be able to tell a live plan from a settled fact. - Close the loop. Add a row to
sad.md§9 ADR index (and link fromtasks/_epic.mdif the ADR scopes a specific task). The ADR's own## Linksmust point up to the spec + the relevantsad.md§N — no orphans. - Structural self-check — per [`../_shared/se