write-adr

# Write ADR Generate Architecture Decision Records (ADRs) from decisions made during the current session. ## Workflow Overview 1. **Context** - Gather repository context and existing ADRs 2. **Extract** - Analyze conversation for decisions using a subagent 3. **Confirm** - Present decisions to user for selection 4. **Write** - Generate ADRs in parallel using subagents 5. **Report** - Summarize created files and status 6. **Verify** - Validate generated ADRs against Definition of Done ### Gates (objective pass conditions) Advance only when the **pass condition** holds. These are checkable without “I verified internally.” | After | Pass condition | |-------|----------------| | Step 2 (extract) | The subagent response is **valid JSON** with a top-level `decisions` **array** (empty is OK). Each non-empty item has `id`, `title`, and at least one of `context`, `decision`, `alternatives`, or `rationale` present as a non-empty string or non-empty array. If parsing fails or the shape is wrong, **re-run extraction or fix the payload** before Step 3. | | Step 4 (pre-allocate) | From repo root, `python plugins/beagle-analysis/skills/adr-writing/scripts/next_adr_number.py --count N` prints **exactly `N` lines** (one number per line). You have a **written mapping** (in the reply draft or notes) from each selected decision to one of those lines **before** launching any `run_in_background` ADR writer Task. | | Step 5 (report) | Every file path in the summary table is copied from a suba...