What problem does it solve? Plans and design docs often hide architecture flaws, missing edge cases, and untested codepaths that only surface after implementation begins. This Skill performs an engineering-manager-style review of a plan before any code is written, catching scope creep, over-engineering, and coverage gaps early. ## Core Features & Use Cases - Scope Challenge (Step 0): Challenges whether existing code already solves sub-problems, flags plans touching 8+ files or 2+ new services, and verifies chosen patterns against current best practices via web search. - Four-Section Interactive Review: Walks through Architecture, Code Quality, Tests, and Performance one section at a time, presenting each issue individually with an opinionated recommendation and confidence score. - Test Coverage Diagrams: Traces every planned codepath and user flow into an ASCII coverage diagram, marking branches that need unit tests, E2E tests, or evals, with a mandatory regression-test rule. - Use Case: Before implementing a new feature, run the review on your plan doc to get findings like "[P1] (confidence: 9/10) auth.ts:47 — token check returns undefined when session expires" and decide each fix interactively. ## Quick Start Ask the assistant to run an engineering review of your current plan or design doc before you start coding.
