adr-author

To draft an Architecture Decision Record consistently, use a template-driven generation process that enforces required sections like Context, Decision, Status, and Consequences. This skill outputs complete Markdown ADRs with validated slugs to ensure uniform governance documentation.

An Architecture Decision Record should include Title, Context, Decision, Status, Consequences, Alternatives, Impacted Modules, Compliance Notes, and Review sections. This skill enforces this specific template structure to align with governance standards during documentation generation.

Documenting architecture decisions for compliance tracking is best handled by generating ADRs with dedicated Compliance Notes and Review sections. This skill enforces these specific template sections to ensure decisions meet governance requirements and reference necessary compliance documents.

You can automatically generate ADR Markdown files into a specific directory structure. This skill writes the complete ADR directly to docs/backend/architecture/ADR/<slug>.md, validating the slug and enforcing the template sections during the file creation process.

Enforcing a standard ADR template when documenting engineering patterns requires a structured generation tool that validates required sections. This skill applies the template consistently across architecture changes and outputs a complete Markdown file for every documented decision.