extract-adrs
SolidExtract architecture decision records from existing meta documents (research, plans). Scans documents for implicit or explicit architectural decisions and converts selected ones into formal ADRs. Use when decisions are buried in research or planning documents and need to be captured formally.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- atomicinnovation
- Repository
- atomicinnovation/accelerator
- Created
- 6 months ago
- Last Updated
- yesterday
- Language
- Rust
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
create-adr
Interactively create an architecture decision record (ADR). Use when the user wants to document an architectural decision, technology choice, or significant design decision. Guides through context gathering, options analysis, and consequence documentation.
adr-capture
Capture Architecture Decision Records (ADRs) from .context/ plans, findings, and analyses. Extracts binding decisions into numbered ADRs under docs/ADR/, maintains a machine-readable index, and validates coverage. Use when creating or reviewing context files that contain decisions. DO NOT use for observational findings without decisions, retroactive documentation of long-settled decisions, or inline comments. Triggers: 'capture decision', 'create ADR', 'document decision', 'architectural decision', 'record decision as ADR', 'extract decisions', 'ADR review', 'index ADRs', 'check ADR coverage'.
adr-generator
Create comprehensive Architectural Decision Records (ADRs). Researches the destination directory to detect existing template conventions, gathers context, determines next ADR number, generates the ADR, validates completeness, and saves. Supports multiple ADR formats (MADR, Nygard, Alexandrian, project canonical). Use when documenting technical decisions, creating new ADR files, or capturing rationale so future readers can revisit a choice. Use when you say "write an ADR", "document this decision", "document these design choices", "record why we chose this", "capture the rationale", or "for future maintainers", or when creating an ADR-like markdown file under docs/decisions/, docs/adr/, docs/architecture/, architecture/decisions/, or .agents/architecture/. Do NOT use to debate or review an existing ADR (use adr-review).