Skip to main content
Generaldavepoon

gsd:plan-phase

Create detailed phase plan (PLAN.md) with verification loop

Stars
2,987
Source
davepoon/buildwithclaude
Updated
2026-05-26
Slug
davepoon--buildwithclaude--plan-phase
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/davepoon/buildwithclaude/HEAD/plugins/gsd/skills/plan-phase/SKILL.md -o .claude/skills/plan-phase.md

Drops the SKILL.md into .claude/skills/plan-phase.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Create executable phase prompts (PLAN.md files) for a roadmap phase with integrated research and verification.

Default flow: Research (if needed) → Plan → Verify → Done

Orchestrator role: Parse arguments, validate phase, research domain (unless skipped), spawn gsd-planner, verify with gsd-plan-checker, iterate until pass or max iterations, present results.

@${CLAUDE_PLUGIN_ROOT}/workflows/plan-phase.md @${CLAUDE_PLUGIN_ROOT}/references/ui-brand.md **Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`. They are equivalent — `vscode_askquestions` is the VS Code Copilot implementation of the same interactive question API. Do not skip questioning steps because `AskUserQuestion` appears unavailable; use `vscode_askquestions` instead. Phase number: $ARGUMENTS (optional — auto-detects next unplanned phase if omitted)

Flags:

  • --research — Force re-research even if RESEARCH.md exists
  • --skip-research — Skip research, go straight to planning
  • --gaps — Gap closure mode (reads VERIFICATION.md, skips research)
  • --skip-verify — Skip verification loop
  • --prd <file> — Use a PRD/acceptance criteria file instead of discuss-phase. Parses requirements into CONTEXT.md automatically. Skips discuss-phase entirely.
  • --reviews — Replan incorporating cross-AI review feedback from REVIEWS.md (produced by /gsd:review)
  • --text — Use plain-text numbered lists instead of TUI menus (required for /rc remote sessions)

Normalize phase input in step 2 before any directory lookups.

Execute the plan-phase workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/plan-phase.md end-to-end. Preserve all workflow gates (validation, research, planning, verification loop, routing). When planning concludes (PLAN.md files written, plan-checker passed, STATE.md updated), emit a Next Up continuation block following the pattern in `references/continuation-format.md`:
  • Show planning status (e.g., ## ✓ Phase N Planned — M plans, K tasks with brief plan list)
  • Emit a ## ▶ Next Up heading with /gsd:execute-phase N
  • Use `/clear` then: before the command
  • Include a parenthetical: (/clear is safe — /gsd:resume-work restores position from HANDOFF.json if you change your mind)
  • Add an "Also available:" section: review the plan files, run /gsd:list-phase-assumptions N, etc.

Plan-to-execute is a clean boundary — the discuss/research/plan conversation rarely informs execution. Suggesting /clear here keeps execution starting with a tight, plan-focused context.