What problem does it solve?
Teams lose the reasoning behind architectural choices over time, leaving future engineers unable to understand why a system was built a certain way. This Skill records settled decisions as structured, dated ADRs so the context, rejected alternatives, and consequences stay on the record permanently.
Core Features & Use Cases
- Structured ADR authoring: Creates numbered ADR files (NNNN-title.md) from a template with exactly Context, Decision, and Consequences sections, plus frontmatter for status, date, deciders, and supersedes.
- Supersedes chain management: Wires replacement decisions in both directions, flipping the old record to superseded and adding a forward link without rewriting frozen history.
- Prior-art scanning and validation: Searches existing decisions and proposals before writing, then audits links and frontmatter so the decision log stays consistent.
- Use Case: After your team agrees to adopt event sourcing for the orders service, ask the agent to record the decision; it allocates the next ADR number, documents the rejected alternatives, links the parent proposal, and supersedes the outdated REST API record.
Quick Start
Ask your AI agent to record the architecture decision we just made about adopting event sourcing for orders as an ADR in the decisions folder.