--- name: decide description: Record an architectural decision as a numbered ADR and update architecture.md to match. Use right after a decision is made in conversation. --- # /orient:decide Record one architectural decision as a numbered, append-only ADR. Resolve the docs directory from `CLAUDE_PLUGIN_OPTION_DOCS_DIR` (default `docs`). 1. Find the highest existing ADR number in `/decisions/` and add one. Filenames are the number alone, `NNNN.md`, numbered from 0001 (count older `NNNN-title.md` files too). Never reuse a number. The number-only name is what makes two branches that pick the same number hit a git merge conflict (ADR-0018). 2. Fill `templates/adr.md`. Interview the user **only** for what can't be inferred from the session — the alternatives that were considered and the trade-off accepted are the parts worth asking about. Infer the rest. 3. Show the drafted ADR and write it on approval. Supersede rule: if this decision supersedes an earlier ADR, set `Supersedes:` in the new file and update **only** the `Superseded by:` line of the old one. No other edit to a past ADR is permitted — decisions are append-only. Number clash: a merge conflict on `/decisions/NNNN.md` means another branch took that number first. Keep the base branch's file, save this ADR as the next free number, update its `# ADR-NNNN:` heading and any reference to it, then commit. ## Keep architecture and the shape diagram in sync After the ADR is written, check whether this decision changes structure — entry points, module boundaries, or critical paths. If so, update two things, each shown as a before/after preview and written **only after a separate approval** (the user can accept the ADR but decline these): - `/architecture.md` — touch only the affected lines, refresh the `updated:` marker. - the `## Shape` mermaid diagram in `/STATE.md` — only if the decision adds, removes, or reconnects a major component. Keep it to 6 nodes. Skip whichever target doesn't exist, and skip the whole step for a non-structural decision.