extract-adrs

# Extract ADRs from Meta Documents !`${CLAUDE_PLUGIN_ROOT}/bin/accelerator config context --skill extract-adrs --fail-safe` !`${CLAUDE_PLUGIN_ROOT}/bin/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**: !`${CLAUDE_PLUGIN_ROOT}/bin/accelerator config path decisions --fail-safe` **Research directory**: !`${CLAUDE_PLUGIN_ROOT}/bin/accelerator config path research_codebase --fail-safe` **Plans directory**: !`${CLAUDE_PLUGIN_ROOT}/bin/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: Ident...