architect-first

Prevent architectural drift by mandating architectural documentation and running multi-agent validation before code implementation. This process maps the current state, presents A/B/C options, and verifies new designs maintain previous capabilities before development starts.

The architect-first development philosophy is a process enforcing zero-coupling validation, configuration externalization, and test-driven safety nets. It requires design validation and automated scripts to ensure expansion packs remain independent and modular before structural changes begin.

Validate zero-coupling and modularity by running automated architecture validator scripts against your design document. This ensures expansion packs remain independent and externalizes configuration before any new feature code implementation begins.

This architecture validation approach requires the pyyaml dependency to function. You need to prepare your architectural design documents and configuration files to satisfy the externalization requirements before running the validation scripts.

You should not use multi-agent validation for simple, non-structural code changes that do not impact system modularity. The process is designed for structural system changes, complex refactoring, and new feature development where architectural drift is a risk.