cron-like-skill-placeholder

Architectural Decision Records (ADRs) capture design choices with context, decision rationale, and consequences in a structured format. This Skill generates machine-readable ADRs in Markdown with sections for Status, Context, Decision, Consequences, Alternatives Considered, and References—enabling consistent documentation across teams for architecture reviews and cross-team traceability.

To create an ADR, provide a title, context (the issue or problem being addressed), your decision, and current status. The Skill generates a complete Markdown ADR with structured sections for positive, negative, and neutral consequences, alternatives you considered, and reference links, all dated for audit trails.

Yes. This Skill supports integration via MCP gateway or REST API, allowing you to embed ADR creation directly into your architecture planning and design review workflows without manual Markdown editing.

The Skill outputs machine-readable Markdown ADRs with standardized sections: Status, Context, Decision, Consequences (categorized as Positive, Negative, Neutral), Alternatives Considered, and References, plus a timestamp for documentation and traceability.

Use ADRs during architecture planning, design reviews, and whenever significant technical decisions affect system design or cross-team development. They create permanent records of why decisions were made, helping new team members understand historical context and preventing recurring debates.