Skip to content

tobihagemann/turbo / claude/skills/review-plan

review-plan

Verified

Review 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".

FileKindSize
SKILL.mdskill md7.7 KB
references/plan-scope-review.mdmarkdown3.1 KB
references/plan-structure-review.mdmarkdown4.8 KB

references/plan-structure-review.md

View on GitHub
# Plan Structure Review Reference

## Review Instructions

Read project context (CLAUDE.md and files mentioned in the plan) to understand the codebase. Review whether the plan holds together and can be executed.

## What to Review

- **Structural completeness** — Context states the deployment's bounds, and the plan carries acceptance criteria (or Verification records that the change has no observable behavior). Every acceptance criterion with observable behavior is exercised by the Verification section
- **Completeness** — Missing steps, undefined behavior, unaddressed acceptance criteria or edge cases
- **Feasibility** — Technically unsound approaches, ignored constraints, missing dependencies
- **Ordering** — Step dependency issues, missing prerequisites, circular dependencies
- **Buildability** — Steps specific enough to execute without getting stuck. No logical gaps between steps
- **Concreteness** — Every step references a concrete anchor (file/line, function, symbol, or file to create), and named symbols/types are verifiable in the codebase. Flag vague directives or placeholder language
- **Codebase accuracy** — Concrete claims the plan makes about current code (named functions, file paths, type shapes, module boundaries, existing API surfaces) must match what is in the repo. Spot-check by opening the cited files. Flag wrong citations, misdescribed seams, and nonexistent-but-assumed APIs — these mislead implementation the most
- **Consistency** — Internal contradictions between sections (e.g., Implementation Steps disagree with Verification, two steps describe the same call differently)
- **Verification** — The plan has a verification section that describes how to confirm the change works. Flag if missing, or if it is vague ("run tests" without naming which tests or what to look for)
- **Execution-wrapper content** — Flag Implementation Steps or Verification that instruct committing, pushing, or opening a PR when the workflow that produced the plan forbids that content in plan files. An item that only observes the result of a push passes
- **Test efficacy** — When the plan proposes, keeps, or reshapes a test as a regression net, check that the test can fail when the behavior it guards breaks. Flag an assertion that reads a surface the code under test does not write, a case where a mechanism other than the one under test produces the same observable, or an outcome asserted in a suite that replaces the code producing it with a test double
- **Specified algorithms** — When the plan specifies an algorithm or rule with stated postconditions, trace it by hand on concrete inputs it can receive, including degenerate ones (empty, equal values, a value just beside a boundary). Flag any input where a postcondition fails or the rule is ambiguous
- **Pattern Alignment** — Proposed approach follows existing codebase patterns where applicable. Deviations from established patterns are justified
- **Side effects** — Other consumers, callers, or co-firing components affected by changes to shared surfaces (helpers, lifecycle hooks, globals)
- **Failure Modes** — How the design handles partial failure, race conditions, stale state, rollback, data loss, and degraded dependencies. Limit this to scenarios reachable in the deployment the plan's Context describes: when it bounds the system (a single operator, no concurrent writers, a handful of invited users), a scenario that bound rules out is not a gap

## Determination Criteria

Flag an issue only when ALL of these hold:

1. It would cause an implementer to build the wrong thing or get stuck
2. The issue is discrete and actionable (not a vague concern or general suggestion)
3. The author would likely fix the issue if made aware of it
4. The issue is clearly not an intentional design choice, OR it challenges a design choice with evidence of concrete failure modes or a simpler alternative

## Priority Levels

- **P0** — Plan is fundamentally flawed. Wrong approach or missing core acceptance criterion
- **P1** — Significant gap that will likely cause implementation problems
- **P2** — Moderate issue that should be addressed before implementation
- **P3** — Minor improvement

## What to Ignore

- Wording, stylistic, or cosmetic preferences that don't affect buildability
- Alternative approaches without evidence of concrete advantages over the chosen one
- Suggestions that add complexity without clear implementation value
- Missing execution-wrapper content (skill invocations, task tracking, or finalize/commit steps) when the workflow that produced the plan forbids that content in plan files, the execution wrapper already discovers the required capability from the plan's substantive work, and the plan carries concrete acceptance criteria for that outcome. Still flag when the wrapper cannot discover the capability, or when the plan lacks substantive behavior or verification for the intended outcome.
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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall