test-plan-reviewlisted

# Test Plan Review Skill Review a test SUITE or a test PLAN at the suite level — not line by line. The question this skill answers: **what behavior isn't being tested, and which tests will pass even when the code is broken?** A green suite that doesn't exercise the failure paths is worse than no suite, because it manufactures false confidence. ## Step 1: Locate the Inputs If the user provided a path as an argument, use it. Otherwise discover the target: **Test-plan document** — glob: `**/test-plan*.md`, `**/TEST-PLAN*.md`, `**/TESTING.md`, `**/test_plan*.md` **Test directory / files** — glob: `**/tests/`, `**/__tests__/`, `**/*_test.*`, `**/*.test.*`, `**/test_*.*`, `**/*_spec.*`, `**/*.spec.*` If both a plan doc and a test tree exist, review both (the plan states intent; the tree shows reality — gaps between them are findings). If multiple unrelated candidates exist, use AskUserQuestion to disambiguate. ## Step 2: Inventory the Tests Run the scanner to build a picture of what exists before judging what's missing: ```bash ~/.claude/skills/test-plan-review/scripts/scan-tests.sh <repo-or-tests-dir> ``` This counts test functions per file, identifies the test framework(s), and — most importantly — reports which source directories have **no corresponding tests**. Those are your first coverage suspects. ## Step 3: Load Checklists Read ALL of the following checklist files from this skill's directory (`~/.claude/skills/test-plan-review/`). They contain the full review crit