| name | create-adr |
| description | Create Architecture Decision Records (ADRs) following LCA conventions.
INVOKE THIS SKILL when user:
- Asks to "document a decision" or "record a decision"
- Mentions "ADR", "decision record", or "architectural decision"
- Wants to capture trade-offs or options considered
- Needs to supersede or update an existing decision
- Asks about decision history or rationale
Trigger keywords: ADR, decision record, architectural decision, trade-offs, options, rationale
|
| allowed-tools | ["Read","Write","Glob","AskUserQuestion"] |
Guide creation of Architecture Decision Records that capture the "why" behind architectural choices. ADRs are append-only documents that preserve decision history, enabling future maintainers to understand context and trade-offs.
<quick_start>
- Identify decision scope: What architectural choice needs documentation?
- Gather context: Why is this decision being made now? What drivers exist?
- Document options: What alternatives were considered?
- Analyze trade-offs: Explicit positive, negative, neutral consequences
- Record decision: Write ADR with proper numbering and status
- Link to architecture docs: Reference from relevant ARCHITECTURE.md
<naming_convention>
adr-NNN-{slug}.md
Examples:
adr-001-use-protocol-buffers.md
adr-002-adopt-event-sourcing.md
adr-003-schema-org-boundaries.md
Numbers are sequential and never reused. Superseded ADRs keep their number.
</naming_convention>
