What problem does it solve? Before implementation starts or a release ships, teams need to know whether their normative documents — SRS requirements, HLD design entries, accepted ADRs, and the implementation plan — tell one consistent story about every frozen contract property. Manually cross-checking namespaces, nullability, enum values, and forbidden requirement IDs across thousands of lines of documentation is error-prone and often misses contradictions or untested acceptance criteria. ## Core Features & Use Cases - Frozen-contract consistency review: Traces each contract property through every document that should state it, citing doc:line evidence, and distinguishes actionable contradictions from harmless omissions. - Spec-compliance implementation mode: Maps every SRS acceptance criterion to a named test, runs focused test suites as execution evidence, and classifies results as PASS, FAIL-untested, or FAIL-deviant. - Negative-claim verification: Greps the whole docs tree and repository for forbidden requirement IDs, removed API names, and scope-exclusion violations, and diffs the frozen API manifest symbol-by-symbol against PublicAPI baselines. - Use Case: Before freezing a Phase-N contract, ask for a final read-only review of the SRS, HLD manifest section, ADRs, and plan; receive a PASS/FAIL verdict with per-item evidence and a separate informational-only list. ## Quick Start Ask the agent to perform a final read-only consistency review of your Phase-N frozen contracts against the SRS, HLD, ADR, and implementation plan, returning a PASS/FAIL verdict with evidence.
