What problem does it solve?
Teams often overlook architecture decisions or document them inconsistently, so this skill enforces context-rich, repeatable records that surface why a change was made.
Core Features & Use Cases
- Structured ADR Template: Generates ADR documents with sections for context, decision, alternatives, rationale, consequences, and risks, ensuring every entry follows a consistent narrative.
- Pipeline Awareness: Detects the current git branch and related issue, reads .paadhai.json, and keeps ADR numbering in sync while providing guidance depending on whether it was invoked from dev-plan or standalone.
- Commit Readiness: Saves the approved ADR to docs/adr with a kebab-case filename, then stages and commits the new file to keep documentation in version control.
- Use Case: Ideal for recording high-impact architectural choices during feature planning so every stakeholder sees the rationale, alternatives considered, and next steps.
Quick Start
Ask the dev-adr skill to document the current architectural decision with the related issue context.