extract-adrs

Solid

Extract 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.

Data & Documents 34 stars 1 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
51
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Extract ADRs from Meta Documents !`accelerator config context --skill extract-adrs --fail-safe` !`accelerator config agents --fail-safe` If no "Agent Names" section appears above, use these defaults: accelerator:reviewer, accelerator:codebase-locator, accelerator:codebase-analyser, accelerator:codebase-pattern-finder, accelerator:documents-locator, accelerator:documents-analyser, accelerator:web-search-researcher. **Decisions directory**: !`accelerator config path decisions --fail-safe` **Codebase research directory**: !`accelerator config path research_codebase --fail-safe` **Plans directory**: !`accelerator config path plans --fail-safe` You are tasked with identifying architectural decisions within existing meta documents and helping the user capture them as formal ADRs. ## Initial Setup When this command is invoked: 1. **Check if parameters were provided**: - If one or more file paths were provided, note them as the target documents - If no parameters provided, respond with: ``` I'll help you extract architectural decisions from existing documents. You can: 1. Specify documents to scan: `/accelerator:extract-adrs @{research directory}/2026-03-18-auth-flow.md` 2. Let me scan all documents in the configured directories for decisions (this may take a moment) Which would you prefer? ``` Wait for user input. ## Process Steps ### Step 1: Identify Source Documents 1. If specific files were provided, read them FULLY 2. If scanning all meta documents: - Spawn a...

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

AI & Automation Solid

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.

34 Updated yesterday
atomicinnovation
Data & Documents Listed

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'.

2 Updated 1 weeks ago
pantheon-org
AI & Automation Listed

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).

47 Updated today
rjmurillo