gap-analysislisted

# Gap Analysis Domain expertise for detecting gaps in design documents, specifications, and plans before implementation begins. ## Iron Law > **GAPS IN DESIGN BECOME BUGS IN PRODUCTION** > > Every undefined error state, vague requirement, and missing integration point is a bug > waiting to be written. Catch gaps in the plan so the implementation reflects reality, > not assumption. Evidence-required: every gap must cite specific text from the artifact. --- ## Focus Areas ### 1. Completeness Detect missing pieces that will block or break implementation. **Detection patterns:** - Missing acceptance criteria — requirements without testable success conditions - Undefined error states — happy path described, failure paths absent - Vague requirements — "fast", "secure", "user-friendly" without measurable thresholds - Ambiguous user journeys — "user submits form" without specifying what happens next - Missing rollback specification — no recovery path if operation partially fails - Unspecified data constraints — fields mentioned without type, size, or validation rules **Evidence trigger:** Any requirement phrase that cannot be directly translated into a test case. ### 2. Architecture Detect design decisions that conflict with existing patterns or create structural problems. **Detection patterns:** - Implied patterns violating existing conventions — new module structure that contradicts codebase layout - Missing integration points — feature touches shared state but integrat