adr-generatorlisted

Create comprehensive Architectural Decision Records (ADRs). Researches the destination directory to detect existing template conventions, gathers context, determines next ADR number, generates the ADR, validates completeness, and saves. Supports multiple ADR formats (MADR, Nygard, Alexandrian, project canonical). Use when documenting technical decisions, creating new ADR files, or capturing rationale so future readers can revisit a choice. Use when you say "write an ADR", "document this decision", "document these design choices", "record why we chose this", "capture the rationale", or "for future maintainers", or when creating an ADR-like markdown file under docs/decisions/, docs/adr/, docs/architecture/, architecture/decisions/, or .agents/architecture/. Do NOT use to debate or review an existing ADR (use adr-review).
rjmurillo/ai-agents · ★ 45 · AI & Automation · score 80

Install: claude install-skill rjmurillo/ai-agents

# ADR Generator Create well-structured Architectural Decision Records that document technical decisions with clear context, rationale, consequences, and alternatives. ## Triggers | Trigger Phrase | Operation | |----------------|-----------| | `write an ADR` | Full ADR generation workflow | | `write an architecture decision record` | Full ADR generation workflow | | `create an ADR` | Full ADR generation workflow | | `generate ADR for` | Full ADR generation workflow | | `document these design choices` | Capture rationale for durable architecture or design decisions | --- ## Quick Start ```text # These all work: write an ADR for the event model write an architecture decision record for database selection create an ADR for database selection new ADR for authentication strategy document this architecture decision about event sourcing generate ADR for switching from REST to gRPC document these design choices for future us to revisit as models change record why we chose this instruction-file structure for future maintainers ``` --- ## When to Use | Situation | Use This Skill? | |-----------|----------------| | New architectural decision needs documenting | Yes | | Durable design choices or rationale need capturing for future readers | Yes | | Changing an existing system or pattern | Yes (includes Prior Art Investigation) | | Reviewing or validating an existing ADR | No, use `adr-review` skill | | Minor implementation detail, not architectural | No | --- ## Process ### Ph