architecture-stress-test

To stress test your software architecture pre-lock, run the adversarial review against your drafted ARCHITECTURE.md and capabilities.yaml to expose architecture-breaking risks. This produces a STRESS-TEST-REPORT.md with GO-FIX-NOW or ARCH-AMEND recommendations.

An adversarial architecture review systematically surfaces design risks by running three parallel lenses: a bottleneck-finder, an edge-case-finder, and a forgotten-concern-finder. These lenses validate your drafted architecture against planned capabilities to expose breaking points.

You need to prepare ARCHITECTURE.md, capabilities.yaml, WEDGE-AND-CAPABILITIES.md, and PRD context files in your project root. These inputs provide the drafted design and product planning context required to generate a structured stress test report.

You can use this architecture stress test on any product context because the workflow is product-agnostic. It validates your drafted ARCHITECTURE.md against capabilities.yaml and planning context regardless of the specific software framework or platform.

You should run a pre-lock architecture stress test during Phase 0.5, after drafting your architecture but before locking in the design. This gating phase ensures architecture-breaking risks are identified and resolved before development proceeds.

The stress test report outputs a STRESS-TEST-REPORT.md containing structured findings and a formal verdict for gating the lock. You use the GO-FIX-NOW, ARCH-AMEND, or DEFERRED recommendations to decide whether to amend the architecture or proceed with locking.