What problem does it solve? Teams repeatedly re-argue the same design choices, and new members cannot understand why a particular approach was chosen. This Skill captures every "why A over B" decision as a structured Architecture Decision Record (ADR), preserving context, alternatives, and tradeoffs for long-term traceability. ## Core Features & Use Cases - Structured ADR Generation: Converts JSON input, natural language, or other Skill outputs into formatted decision records with unique sequential IDs (D-001, D-002...) appended to DECISIONS.md. - Automatic Decision Extraction: Detects implicit decisions in outputs from skills like layout-optimizer or component-generator and infers category, options, and rationale. - Lifecycle Management: Tracks decision status (proposed, accepted, deprecated, superseded) and links related or superseding decisions. - Use Case: After choosing backend pagination over frontend pagination for a 100k-row user list, record the context, evaluated options, chosen solution, and tradeoffs so future iterations can revisit the rationale without re-debating. ## Quick Start Ask the assistant to record a decision by providing the title, context, at least two options, the chosen one, and the reason, and it will append a formatted ADR entry to DECISIONS.md.
