extract-adrs

To extract architectural decisions, agent-based document analysis scans meta research and plan documents to identify implicit choices, context, drivers, and tradeoffs, then converts them into draft Architecture Decision Records for review.

Creating Architecture Decision Records from scattered notes involves scanning research and planning documents to surface option comparisons and rationale, then populating a canonical ADR template with context, considered options, and consequences.

You need to formalize implicit architectural decisions into ADRs when significant choices are buried across multiple research notes and plans, ensuring decisions are recorded consistently for long-term documentation and review.

Generating and numbering ADR drafts requires populating templates with placeholder numbers, coordinating approvals for the proposed drafts, and then assigning sequential ADR numbers to write approved files into the configured decisions directory.

Yes, you need repository access to read meta documents from research, plans, and decisions directories for analysis, and to write the approved Architecture Decision Record files into the configured repository structure.