architect-first

Document software architecture before writing code by mapping current structures and writing complete designs, including an ADR and YAML configuration schema, to enforce zero-coupling checks and prevent capability loss.

Architect-first development is the practice of enforcing complete design and documentation before implementation. Apply it to structural decisions, refactors, feature launches, and configuration-driven system changes requiring multi-perspective review.

Validate a system refactor against previous capabilities by applying multi-agent validation across Product Owner, Architect, and User perspectives, then verify with tests and zero-coupling checks before implementation.

Yes, this approach requires writing an Architecture Decision Record (ADR) and a YAML configuration schema to document complete designs before requesting any code changes for structural decisions or refactors.

Enforce stop-rule remediation during test-backed execution by requiring explicit approval across multiple perspectives and verifying with tests and coupling checks, ensuring no implementation proceeds without validated architecture.

Implementing structural changes without design causes capability loss because incomplete or missing documentation leads to tight coupling and quality regressions that bypass multi-perspective validation and zero-coupling checks.