Skill: ADR Creation
Create architectural decision records that preserve why, not just what.
When to use
- •New architectural pattern is introduced.
- •A trade-off impacts reliability/scalability/maintainability.
- •A migration boundary or deprecation gate is defined.
ADR format
Use docs/adr/ADR-XXXX-title.md.
Minimum sections:
- •Context
- •Decision
- •Options considered
- •Consequences (positive/negative)
- •Evidence (code/tests/metrics)
Rules
- •Every P0 ticket that changes architecture should produce or update an ADR.
- •Link ADR IDs in ticket JSON
done_definitionnotes. - •If a decision reverses, mark old ADR as superseded instead of deleting.