Capture architectural decisions and store them in the repository's ADR directory.
npx skills add https://github.com/8Dionysus/aoa-skills --skill aoa-adr-write
Please help me install this Agent Skill. Skill: aoa-adr-write Source: https://github.com/8Dionysus/aoa-skills/tree/main/.agents/skills/aoa-adr-write Command: npx skills add https://github.com/8Dionysus/aoa-skills --skill aoa-adr-write
Teams often lose the rationale behind structural, tooling, or workflow changes, making future maintenance and onboarding difficult. This skill ensures those decisions are clearly recorded, placed in a canonical location, and kept in sync with the actual code changes.
docs/adr directory.Use the aoa-adr-write skill to record a new architectural decision and place it in the canonical ADR directory.
High-intent search queries and answers about installing and using this skill.
To document architectural decisions, you need to record the context, options, chosen path, and tradeoffs in an Architecture Decision Record. This creates a searchable record that preserves the rationale behind structural, tooling, or workflow changes for future maintenance and onboarding.
You should create an ADR when structural, tooling, or process changes require a clear record. Apply this practice when introducing a new build system or refactoring a core module to ensure the decision context and tradeoffs are documented.
To verify an ADR aligns with code changes, validate that the documented decision is kept in sync with the implementation. This verification process checks that the recorded rationale matches the actual structural modifications and is reachable from the expected location.
The best way to store ADRs is by placing them in the repository's canonical decision surface, such as a dedicated docs/adr directory. This ensures the architectural documentation is automatically stored in a location for easy discovery by contributors.
No specific dependencies are required to generate ADRs. The process focuses on capturing the decision context and placing the concise record directly into the repository's decision surface without relying on external components.
az9713Compare current page state against stored baselines to detect UI regressions.
ZendevveCreate standardized Architecture Decision Records with templates and Mermaid diagrams.
timblaktuDocument architectural decisions using the Design It! ADR methodology.
hgflimaCreate and manage architectural decision records using markdown templates.