# Decide > Record an architectural decision as a numbered ADR and update architecture.md to match. Use right after a decision is made in conversation. - Skill: `chaitanya299/decide` (Agent Skill) - Install (CLI): `npx skillmds@latest add chaitanya299/decide` - Raw SKILL.md: https://api.skillmd.com/api/skills/chaitanya299/decide/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: Chaitanya299 (https://skillmd.com/u/chaitanya299) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/chaitanya299/decide --- # /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 `NNNN-kebab-title.md`, numbered from 0001. 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. ## 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.