architecture

Document architecture decisions using ADRs and arc42 by routing tasks through an orchestration layer that aligns activity with a consistent documentation structure and governance program. It coordinates decision records across initial, retrofitting, and evolving project modes.

Retrofitting arc42 documentation onto an existing codebase is handled through a dedicated retrofitting mode that routes to corresponding sub-skills. This ensures cohesive documentation and governance are applied consistently when evolving architecture for existing projects.

Architecture orchestration coordinates sub-skills for greenfield projects by operating in an initial mode that sequentially invokes the appropriate sub-skills. This anchors strategy, documentation, and governance to establish a cohesive arc42-aligned workflow from the start.

Yes, you can manage architecture risk and governance through a single orchestration workflow that routes tasks across modes and integrates architecture-building blocks with consult outputs. This maintains a consistent output format and unified governance program.

You need separate sub-skills for initial and evolving architecture work because the orchestration layer routes tasks to specific sub-skills based on the selected mode. Invoking the corresponding sub-skill in sequence ensures appropriate documentation and governance for each context.

Use architecture orchestration instead of writing arc42 docs manually when you need to coordinate across multiple project modes, ensure consistent output formats, and integrate architecture-building blocks with consult outputs for cohesive governance and risk management.