back
loading skill details...
Create and maintain Architecture Decision Records (ADRs) optimized for agentic coding workflows. Use when you need to propose, write, update, accept/reject,…
ADR Skill
Philosophy
ADRs created with this skill are executable specifications for coding agents. A human approves the decision; an agent implements it. The ADR must contain everything the agent needs to write correct code without asking follow-up questions.
This means:
Constraints must be explicit and measurable, not vibes
Decisions must be specific enough to act on ("use PostgreSQL 16 with pgvector" not "use a database")
Consequences must map to concrete follow-up tasks
Non-goals must be stated to prevent scope creep
The ADR must be self-contained — no tribal knowledge assumptions
The ADR must include an implementation plan — which files to touch, which patterns to follow, which tests to write, and how to verify the decision was implemented correctly
When to Write an ADR
Write an ADR when a decision:don't have the plugin yet? install it then click "run inline in claude" again.