tobihagemann/turbo / claude/skills/review-plan
review-plan
VerifiedReview a plan with internal and peer reviews in parallel and return combined findings. Use when the user asks to "review my plan", "check my plan", or "critique my plan".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.7 KB |
| references/plan-scope-review.md | markdown | 3.1 KB |
| references/plan-structure-review.md | markdown | 4.8 KB |
references/plan-scope-review.md
View on GitHub# Plan Scope Review Reference
## Review Instructions
Read project context (CLAUDE.md and files mentioned in the plan) to understand what already exists. Review whether the plan builds more than its acceptance criteria and stated bounds justify.
Identify the plan's acceptance criteria and its stated bounds (Context or the original ask) before judging any step. A step is in scope when a criterion or bound calls for it.
## What to Review
- **Scope** — Acceptance criteria addressed without creep
- **YAGNI** — Steps that build something no acceptance criterion asks for: unrequested features, premature abstractions, or scaffolding for anticipated work
- **Design Direction** — Whether the chosen approach is the simplest safe option. Challenge assumptions the plan depends on and flag when a different approach would be safer or simpler
- **Proportionality** — Steps whose machinery (leases, locks, queues, versioning schemes, state machines, new persistent entities) exceeds the failure modes and scale the plan's Context admits
- **Unconsumed Capability** — A capability the plan builds for code outside the change, such as a caller or a consuming project, that nothing there uses and no plan for that code takes up. Read that code, and the plan for it when one exists. Flag it even when an acceptance criterion names the capability, naming deferral as the simpler approach
- **Self-Referential Justification** — Mechanism justified by a failure mode that exists only because that mechanism is present. Trace each justification back to a criterion or bound; when the chain closes on itself, test whether cutting the mechanism removes its dependents rather than judging each link alone
## Determination Criteria
Flag an issue only when ALL of these hold:
1. The plan builds something its acceptance criteria and stated bounds do not justify, or takes an approach a safer or simpler one would replace
2. The issue is discrete and actionable, naming the cut, the merge, or the alternative approach
3. The finding cites the criterion or bound that fails to justify the work, or the concrete advantage the alternative approach holds
A deliberate design choice is in range here: name the choice and the evidence against it rather than treating the author's intent as settling the question.
## Priority Levels
- **P0** — The approach as a whole builds substantially more than the acceptance criteria ask for
- **P1** — A step or abstraction no acceptance criterion stands behind, or an approach a materially safer or simpler one would replace
- **P2** — Machinery disproportionate to the stated bounds, or a step that folds into a neighbor
- **P3** — Minor simplification
## What to Ignore
- Alternative approaches without evidence of concrete advantages over the chosen one
- A step the dependency chain or a stated constraint requires, even when folding it into a neighbor would shorten the plan; a dependency the reviewed mechanism itself creates does not count as such a constraint
- Input validation at trust boundaries, error handling that prevents data loss, security controls, and accessibility affordances; these stay even when the acceptance criteria do not name them
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |