architect-implement

To generate architecture documentation from ADRs, a multi-agent DAG orchestration processes decision records through plan, execute, and summarize phases. This produces a unified AD.md file at the repository root alongside per-view artifacts with full traceability.

ADR traceability in architecture description generation ensures every architectural decision record is explicitly linked to its corresponding section in the generated AD.md. The DAG orchestration enforces this by mapping each ADR to specific per-view artifacts and perspectives.

Organize ADRs by sub-systems to enable sub-system DAG customization during AD.md generation. This structure allows the orchestration workflow to execute topologically across sub-systems, resolve cross-subsystem conflicts, and integrate perspectives into the final architecture description.

Yes, the architecture documentation generation workflow supports stateful resumability. If the DAG execution is interrupted, you can resume the plan, execute, and summarize phases without losing prior state or ADR traceability mappings.

Automated AD generation works specifically with projects that have existing ADRs organized by sub-systems. It applies a multi-agent DAG orchestration to these records to produce a unified AD.md and per-view artifacts with integrated perspectives.

The best way to resolve cross-subsystem conflicts during Architecture Description generation is through topological DAG execution. The orchestration workflow automatically identifies and resolves conflicting decisions across sub-systems before integrating them into the final AD.md.