architect-first

Architecture-first design requires completing architecture templates, ADRs, and pre-implementation checklists before any code is written, preventing rushed implementation chaos by enforcing multi-agent validation and zero-coupling validation upfront.

The best way to document architecture decisions for refactoring is creating ADRs alongside architecture templates. This governance approach validates decisions with multiple stakeholders before implementation, ensuring externalized YAML configuration and zero-coupling validation are applied safely.

YAML-driven configuration externalizes mutable options to avoid hardcoding during design reviews. By shifting configuration to YAML, the architecture design process maintains governance standards and ensures implementation follows the validated design documentation accurately.

Yes, multi-agent validation is required when starting new features to ensure complete architecture and documentation precede implementation. This governance step validates that design decisions meet zero-coupling requirements and pass pre-implementation checklists before coding begins.

Architecture templates are explicitly designed for major architectural changes, feature starts, and system refactors. They enforce design reviews and ADR creation as non-negotiables, ensuring documentation is validated by stakeholders before any implementation effort.

Zero-coupling validation matters because it prevents misaligned goals and code-first chaos by verifying the architecture design has no hidden dependencies. It acts as a safety net alongside tests, ensuring the documented architecture remains structurally sound during implementation.