review-plan

Solid

Review an implementation plan: launches an internal plan review and `/peer-review` in parallel and returns combined findings. Use when the user asks to "review my plan", "review this plan", "check my plan", "critique my plan", or wants plan feedback before implementation.

Code & Development 312 stars 24 forks Updated today MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
83
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Review Plan Run two AI plan reviews in parallel and return combined findings. ## Step 1: Identify the Plan Determine the plan to review: - If **plan text** is in conversation context, use it - If a **plan file path** was provided, read the file ## Step 2: Run Two Reviews in Parallel Launch two Agent tool calls in a single message so they run concurrently (`model: "opus"`, do not set `run_in_background`): ### Internal Plan Review Spawn a subagent with the full plan text and instruct it to: 1. Read project context (CLAUDE.md and files mentioned in the plan) to understand the codebase 2. Apply the plan determination criteria below 3. Return findings in the output format below ### Run `/peer-review` Skill Spawn a subagent whose prompt includes the full plan text and the following review prompt, and instructs it to invoke `/peer-review` via the Skill tool: ``` <task> Review the following implementation plan for issues that would cause an implementer to build the wrong thing or get stuck. Challenge the design direction: question whether the chosen approach is the simplest safe option and identify assumptions it depends on. </task> <dig_deeper_nudge> After surface-level issues, check for failure modes under stress: partial failure, race conditions, rollback safety, stale state, and data loss. </dig_deeper_nudge> <structured_output_contract> For each issue, state: (1) the problem, (2) where in the plan it occurs, (3) impact on implementation, (4) a suggested fix, and ...

Details

Author
tobihagemann
Repository
tobihagemann/turbo
Created
2 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

review-plan

Review implementation plans for parallelization, TDD, types, libraries, and security before execution

60 Updated today
existential-birds
AI & Automation Solid

review-prompt-plan

Review a prompt plan against its source spec: launches an internal prompt plan review and `/peer-review` in parallel and returns combined findings. Use when the user asks to "review my prompt plan", "review my prompts", "check my prompt plan", "critique my prompts", or wants prompt plan feedback before implementation.

312 Updated today
tobihagemann
Web & Frontend Listed

plan-review

Multi-perspective plan review with VP Product, VP Engineering, and VP Design. Use when reviewing implementation plans, design docs, architecture proposals, or wave plans for blockers, anti-patterns, conflicts, and regressions.

0 Updated today
Miyamura-sudo
Code & Development Solid

iterative-plan-review

Sharpens and stress-tests an existing plan file through multiple codebase-grounded review passes, editing it in place and recording every finding and iteration in cross-referenced companion files. Use this skill whenever the user wants to iterate on, refine, tighten, or improve a plan — including terse commands like "iterate", "refine it", or "iterate for correctness" where a plan is present in context. Also use it when the user asks to verify, validate, or confirm feasibility of an approach (e.g., "can you verify this will work", "check this for correctness", "is this sound") — the defining signal is that the user wants critical evaluation of a proposed approach, not execution of it. Produces two companion files in an artifacts/ subfolder next to the plan: review-findings.md (every finding raised and how it was resolved) and review-iteration-history.md (round-by-round record of specialists engaged and plan changes applied). Do NOT use for implementing plan steps, generating new plans from scratch, writing te

66 Updated today
testdouble
Code & Development Listed

plan-review

Run a multi-LLM review on `plan.md` and `tasks.md` before implementation starts, capturing each reviewer's output as a file and synthesizing a Korean summary the user reads. Use this whenever a plan is non-trivial (size M with external dependencies, or any size L). Different models catch different gaps; the cost of an extra reviewer pass is tiny compared to discovering a missing requirement halfway through develop. Also use whenever the user asks for a "second opinion" on a plan or wants to validate an approach before committing to it.

1 Updated 3 days ago
gitgitWi