architect-first

To enforce design before code, an architect-first approach requires complete documentation and multi-agent validation before implementation. This reduces rework by ensuring system design is mapped and approved prior to writing any code.

The best way to document architecture decisions is by creating an Architecture Decision Record (ADR). This captures the rationale and design choices before implementation, ensuring alignment across teams during feature inception or refactoring.

Multi-agent validation assesses architecture design from Product Owner, Architect, and User perspectives. This process checks zero-coupling and risk mitigation before coding, ensuring the design meets diverse stakeholder requirements.

Yes, you can use architecture templates for refactoring efforts and major system changes. The process applies architecture diagrams, risk assessment, and ADRs to guide the safe evolution of systems and externalize configuration.

YAML is required as a dependency to support the externalization of configuration. This ensures system configuration is separated from the codebase, aligning with the zero-coupling checks needed for safe architectural evolution.