Add ADR follow-up commands for completing investigations #16
Description
Summary
After /beagle:write-adr generates draft ADRs with [INVESTIGATE: ...] prompts, engineers and LLM agents need tooling to systematically complete that work.
Context
The /write-adr command creates ADRs in draft status with investigation prompts like:
* [INVESTIGATE: Review PR #42 discussion for additional drivers]
* [INVESTIGATE: Benchmark performance of Option A vs Option B]
* [INVESTIGATE: Schedule review with security team]These prompts need follow-up before the ADR can move to accepted status.
Proposed Commands
/beagle:list-adr-investigations
Scan all ADRs and list outstanding investigations:
$ /beagle:list-adr-investigations
## Outstanding Investigations
| ADR | Investigation | Category |
|-----|---------------|----------|
| 0003-use-postgresql.md | Review PR #42 discussion | Research |
| 0003-use-postgresql.md | Benchmark performance | Technical |
| 0004-event-sourcing.md | Schedule security review | Agreement |
Found 3 investigations across 2 ADRs
/beagle:complete-adr
Interactive workflow to complete investigations for a specific ADR:
$ /beagle:complete-adr 0003-use-postgresql.md
## ADR: Use PostgreSQL for User Data
### Outstanding Investigations (2)
1. [INVESTIGATE: Review PR #42 discussion for additional drivers]
2. [INVESTIGATE: Benchmark performance of Option A vs Option B]
Which investigation should I work on? (1, 2, or "all")
For each investigation:
- Gather relevant context (fetch PR, run benchmarks, etc.)
- Present findings to user
- Update the ADR with resolved content
- Remove the
[INVESTIGATE]prompt
/beagle:promote-adr
Validate an ADR against E.C.A.D.R. criteria and promote status:
$ /beagle:promote-adr 0003-use-postgresql.md
## E.C.A.D.R. Validation
✓ Evidence - Design feasibility demonstrated
✓ Criteria - 3 alternatives evaluated
✓ Agreement - Peer review completed
✓ Documentation - All sections complete
✗ Realization - No implementation ticket found
Cannot promote: 1 criterion not met.
Create implementation ticket? (y/n)
Proposed Skills
adr-investigation
Skill for resolving different types of investigations:
| Investigation Type | Resolution Approach |
|---|---|
| Research (PR, issue, doc) | Fetch and summarize content |
| Technical (benchmark, PoC) | Run commands, analyze results |
| Agreement (review, sign-off) | Draft request, track status |
| Documentation (diagram, context) | Generate missing content |
adr-lifecycle
Skill for managing ADR status transitions:
draft → proposed → accepted
↓ ↓
rejected deprecated → superseded
Implementation Considerations
- Commands should work with both human engineers and LLM agents
- Support parallel investigation resolution where possible
- Track investigation history (who resolved, when, how)
- Integration with GitHub issues for Agreement-type investigations
Related
- Depends on: Add ADR (Architectural Decision Records) skills and command #14 (ADR skills and write-adr command)
- PR: feat(adr): add ADR skills and write-adr command #15