What problem does it solve?
Organizes informal architecture decisions, PR/issue discussions, and git history into a consistent, MADR-compliant Architectural Decision Record so teams can track and communicate design choices reliably.
Core Features & Use Cases
- Create MADR ADRs: Convert freeform decision notes, meeting outcomes, or PR descriptions into a structured MADR-format markdown file with metadata, context, drivers, options, outcome, pros/cons, and links.
- Reverse-engineer from repository artifacts: Infer ADRs from git logs, commits, PRs, and issues while flagging assumptions when information is missing.
- Update existing ADRs: Accept an existing ADR and a list of changes and regenerate a single, updated ADR file following the repository's naming and placement rules.
- Use Case: When a design decision is reached in a PR discussion, run this skill to produce a one-file MADR ADR, propose a docs/adr filename, and surface any information gaps for follow-up.
Quick Start
Create a MADR ADR from the provided decision notes, git log excerpt, or PR text and suggest a docs/adr filename using the repository conventions.