Arch Skill — Architecture + System Test Design

Feature architecture with requirements traceability is designed by mapping every REQ-NNN directly to BDD-style system tests and architecture patterns. This enforces user approval gates to prevent late-stage rework and ensure complete coverage.

Generating BDD system tests from feature requirements is best handled by producing SPipe constructs with built-in matchers. This approach enforces strict per-requirement test coverage and calls out performance risks before design iteration.

The MDSOC pattern applies to system test design by evaluating architecture patterns and producing a feature-scoped architecture artifact. It aligns feature requirements directly with SPipe BDD system tests and explicit observability considerations.

Performance budgets and observability checks can be enforced during architecture planning through an explicit quality check loop. This loop requires user approval for architecture changes and calls out invalidation risks before moving to design iteration.

User approval gates are required before finalizing a feature architecture document. These gates ensure architecture patterns, BDD-style tests, and requirement coverage meet quality standards before proceeding to design iteration.