adr

This skill should be used when the user asks about "structured MADR", "structured-madr", "frontmatter ADR", "comprehensive ADR", "auditable ADR", or needs guidance on creating ADRs using the Structured MADR format with YAML frontmatter and audit sections.

This skill should be used when the user asks about "ADR compliance", "architecture compliance", "ADR audit", "enforce ADRs", "check code against ADRs", "ADR violations", or needs guidance on auditing code compliance with accepted architectural decision records.

This skill should be used when the user asks about "business case ADR", "MBA-style ADR", "cost-benefit ADR", "SWOT ADR", "executive ADR", "ROI ADR", or needs guidance on creating ADRs using the business case format for executive and financial analysis.

This skill should be used when the user asks about "MADR format", "MADR template", "Markdown Architectural Decision Records", "MADR 4.0", "MADR sections", or needs guidance on creating ADRs using the MADR (Markdown Architectural Decision Records) format.

This skill should be used when the user asks about "Nygard format", "Nygard ADR", "classic ADR format", "simple ADR template", "Michael Nygard ADR", or needs guidance on creating ADRs using the original Nygard format.

This skill should be used when the user asks about "Y-statement format", "Y-statement ADR", "concise ADR", "one-sentence ADR", "Olaf Zimmermann ADR", or needs guidance on creating ADRs using the Y-Statement format for concise decision documentation.

This skill should be used when the user asks about "ADR integration", "ADR CI/CD", "ADR tooling", "ADR automation", "export ADRs", "ADR documentation site", or needs guidance on integrating ADRs with CI/CD, documentation sites, and other tools.

This skill should be used when the user asks about "decision drivers", "architectural forces", "quality attributes", "how to identify trade-offs", "non-functional requirements for ADRs", or needs help identifying, documenting, and weighing the forces that influence architectural decisions.

This skill should be used when the user asks about "Alexandrian format", "Alexandrian ADR", "pattern-based ADR", "forces-based ADR", "Christopher Alexander ADR", or needs guidance on creating ADRs using the Alexandrian pattern format.

This skill should be used when the user asks about "Tyree-Akerman format", "sophisticated ADR", "comprehensive ADR", "enterprise ADR", "formal ADR template", or needs guidance on creating ADRs using the Tyree-Akerman format for enterprise and formal documentation.

This skill should be used when the user asks "what is an ADR", "when should I create an ADR", "ADR best practices", "architecture decision records", "ADR lifecycle", "how to document architecture decisions", or needs guidance on ADR fundamentals, when to create ADRs, or ADR lifecycle management.

This skill should be used when the user asks about "ADR quality", "review ADR", "ADR checklist", "improve ADR", "ADR validation", "good ADR examples", or needs guidance on evaluating, improving, and maintaining high-quality architectural decision records.