Author Architecture Decision Records with the adr-shape 5-section convention.
npx skills add https://github.com/alexherrero/crickets --skill adr-alexherrero
Please help me install this Agent Skill. Skill: adr Source: https://github.com/alexherrero/crickets/tree/main/src/design-docs/skills/adr Command: npx skills add https://github.com/alexherrero/crickets --skill adr-alexherrero
The ADR process provides a standardized way to capture design decisions, rationale, and future audit notes so teams can reason about architecture changes over time.
Create a new ADR file following the 5-section shape and include explicit re-audit triggers.
High-intent search queries and answers about installing and using this skill.
An Architecture Decision Record (ADR) captures design decisions, rationale, and future audit notes so teams can reason about architecture changes over time. It provides a standardized way to document trade-off analysis and change traceability across releases.
To write an ADR, author a file following the canonical 5-section shape: Context, Decision, Consequences, Related, and Document History. Ensure the frontmatter includes name, description, and versioning, while the body details explicit 'why not the alternative' reasoning.
You should document a design decision whenever a software project requires formal decision documentation, trade-off analysis, or change traceability across releases. It is needed to ensure stakeholders can reason about architecture changes and constraints over time.
You keep architecture decision records current by guiding re-audit triggers and change management within the ADR. Including explicit re-audit triggers in the document ensures ADRs stay current and integrated with existing design docs and governance as constraints evolve.
The best way to document rejected alternatives is using the 5-section ADR structure, which enforces explicit 'why not the alternative' reasoning within the body. This ensures your trade-off analysis is formally captured alongside the final decision.
Yes, the ADR format supports per-project adoption and integration with existing design docs and governance. It enforces a standardized 5-section shape with frontmatter metadata, making it applicable for formal decision documentation across individual software projects.
xcrrrGuide architecture pattern selection and document decisions with ADRs.
aoecosystemApply stage-gated section edits to the Database Diagram with audit logging.
ccfDocument architectural decisions with a MADR-style template and lifecycle.
ekremmkasapDocument architecture decisions with standardized ADR templates and lifecycle tracking.
