adr-backfill

ADR Drafting helps teams document significant architectural decisions by creating new Architecture Decision Record files with a standard structure. It inspects your repository for existing ADR conventions, then drafts a new record with Title, Status, Context, Decision, and Consequences sections—defaulting to `docs/architecture/adr` when no convention exists.

adr-critique systematically reviews existing or inherited ADRs to identify violations of shared rules, gaps in business-to-architecture reasoning, and conflicts with neighboring decisions or LikeC4 models. Each issue surfaces as a single flag requiring architect sign-off before moving to the next, ensuring quality without bulk rewrites.

Guides you through seven-phase ADR drafting via focused dialogue, asking one question per turn and pressure-testing your reasoning before self-critique. Enforces specificity on components, deciders, and architectural characteristics, then routes to discovery if foundations are shallow.

ADR Discovery walks you through pre-flight context gathering before drafting an architecture decision record. It scans your repo for signals, confirms your domain and components one at a time, maps relationships, and classifies existing ADRs—outputting a human-verified discovery brief and an open-questions register. Hand off to adr-drafting once five required confirmations are locked.

c4-model produces LikeC4 specifications that enforce Simon Brown's canonical C4 model, generating context and container views alongside architecture decisions. It scaffolds the necessary DSL files and validates against a strict checklist, refusing component views, dynamic diagrams, custom element kinds, and nested systems that fall outside canonical C4 scope.

migrate helps you add govctl governance to an established project by examining existing evidence—documentation, code structure, VCS history, and configuration—to recover consequential decisions and specifications. It guides you through a discovery phase, presents candidates for backfill as Architecture Decision Records, RFCs, or Work Items, and executes only authorized changes in small coherent batches. The workflow preserves traceability, respects existing artifact state, and stops when evidence conflicts or authorization is unclear.