architect-first

Use the architecture flow: map the current system, present A/B/C design options with trade-offs, get validation from Product Owner, Architect, and User, then complete the architecture template. The architecture_validator.py script checks that required sections, diagrams, and configuration schemas exist before implementation begins.

Run the check_coupling.py script against your project path. It scans Python, JavaScript, TypeScript, and YAML files for hardcoded cross-module imports, hardcoded file paths to other modules, and shared global state, then reports violations with remediation steps.

Imperfect code is acceptable only when backed by comprehensive tests, strategic logging points, and a working core use case. Code without tests, hardcoded mutable values, or deployments missing the core workflow are explicitly rejected by the stop rules.

Six conditions halt work immediately: capability loss versus baseline, structural decisions without multi-agent validation, coupling between modules, missing architectural documentation, quick code without a test plan, and hardcoded mutable configuration values. Each rule has a remediation guide.

It includes a fast mode activated only after architectural validation completes, enabling binary decisions and rapid delegation. Risk mitigations like time-boxed planning, proof-of-concept requirements, and the rule of three prevent excessive planning and perfectionism cascades.