architect-first

To enforce architecture before code, you map the current state, present A/B/C options, validate them with stakeholders, document the chosen architecture, and only then implement with tests. This process ensures structural decisions are validated before development begins.

Zero coupling module design ensures modules operate independently without hidden dependencies. Validation requires multiple perspectives, such as Product Owner, Architect, and stakeholders, to confirm the direction and preserve existing capabilities during structural refactors.

You need an architecture decision record when making structural decisions or refactors that impact system design. It captures the chosen architecture, rationale from multi-agent validation, and ensures capability preservation before implementation begins.

Yes, YAML-based configuration externalization supports test-backed execution by externalizing settings. This allows quality gates and safety checks to verify capability preservation while providing a test-backed escape hatch for pragmatism when quality is confirmed.

The best way to prevent capability loss is enforcing quality gates and multi-agent validation before implementation. By mapping current state, presenting options, and requiring complete documentation with explicit stop rules, capabilities are preserved during refactoring.

Architecture-first development requires upfront time investment in documentation and multi-agent validation before coding begins. It may slow rapid prototyping, but includes a test-backed escape hatch for pragmatism when quality can be verified through tests.