Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Source from repo
Generate detailed, bite-sized implementation plans from specs before writing any code
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
plan-document-reviewer-prompt.md
1# Plan Document Reviewer Prompt Template23Use this template when dispatching a plan document reviewer subagent.45**Purpose:** Verify the plan is complete, matches the spec, and has proper task decomposition.67**Dispatch after:** The complete plan is written.89```10Task tool (general-purpose):11description: "Review plan document"12prompt: |13You are a plan document reviewer. Verify this plan is complete and ready for implementation.1415**Plan to review:** [PLAN_FILE_PATH]16**Spec for reference:** [SPEC_FILE_PATH]1718## What to Check1920| Category | What to Look For |21|----------|------------------|22| Completeness | TODOs, placeholders, incomplete tasks, missing steps |23| Spec Alignment | Plan covers spec requirements, no major scope creep |24| Task Decomposition | Tasks have clear boundaries, steps are actionable |25| Buildability | Could an engineer follow this plan without getting stuck? |2627## Calibration2829**Only flag issues that would cause real problems during implementation.**30An implementer building the wrong thing or getting stuck is an issue.31Minor wording, stylistic preferences, and "nice to have" suggestions are not.3233Approve unless there are serious gaps — missing requirements from the spec,34contradictory steps, placeholder content, or tasks so vague they can't be acted on.3536## Output Format3738## Plan Review3940**Status:** Approved | Issues Found4142**Issues (if any):**43- [Task X, Step Y]: [specific issue] - [why it matters for implementation]4445**Recommendations (advisory, do not block approval):**46- [suggestions for improvement]47```4849**Reviewer returns:** Status, Issues (if any), Recommendations50