What problem does it solve?
This Skill reduces PR rework and missed test coverage by validating mid-level design and test strategies before committing a plan to a pull request, catching structural, signature, and testing gaps early.
Core Features & Use Cases
- Dual-persona review loop: Runs 2–3 Haiku cycles with Persona A (The Architect) validating Mid-Level Design and Persona B (The TDD Engineer) validating test scenarios until no significant concerns remain.
- Targeted checks: Verifies TypeScript signatures reference project types, enforces a Call Graph Changes subsection, ensures Calls: lists only project functions, and requires ≥3 test cases per exported function.
- Test hygiene validation: Confirms happy paths, error and edge cases are covered and that tests use project factories and mock helpers rather than inline mocks.
- Use Case: Use this to validate STORY-123 plan.md after plan creation and before creating the PR to ensure the implementation is testable and architecturally sound.
Quick Start
Run a dual-persona haiku review on the plan file for the target story to surface architectural and test coverage issues before creating a PR.