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.
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.
- 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.
Source: davepoon/buildwithclaude → plugins/gsd/skills/plan-phase/SKILL.md
1---2name: gsdplan-phase3description: Create detailed phase plan (PLAN.md) with verification loop4---5
6<objective>
7Create executable phase prompts (PLAN.md files) for a roadmap phase with integrated research and verification.
8
9**Default flow:** Research (if needed) → Plan → Verify → Done
10
11**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.
12</objective>
13
14<execution_context>
15@${CLAUDE_PLUGIN_ROOT}/workflows/plan-phase.md
16@${CLAUDE_PLUGIN_ROOT}/references/ui-brand.md
17</execution_context>
18
19<runtime_note>
20**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.
21</runtime_note>
22
23<context>
24Phase number: $ARGUMENTS (optional — auto-detects next unplanned phase if omitted)
25
26**Flags:**
27- `--research` — Force re-research even if RESEARCH.md exists
28- `--skip-research` — Skip research, go straight to planning
29- `--gaps` — Gap closure mode (reads VERIFICATION.md, skips research)
30- `--skip-verify` — Skip verification loop
31- `--prd <file>` — Use a PRD/acceptance criteria file instead of discuss-phase. Parses requirements into CONTEXT.md automatically. Skips discuss-phase entirely.
32- `--reviews` — Replan incorporating cross-AI review feedback from REVIEWS.md (produced by `/gsd:review`)
33- `--text` — Use plain-text numbered lists instead of TUI menus (required for `/rc` remote sessions)
34
35Normalize phase input in step 2 before any directory lookups.
36</context>
37
38<process>
39Execute the plan-phase workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/plan-phase.md end-to-end.
40Preserve all workflow gates (validation, research, planning, verification loop, routing).
41</process>
42
43<output_format>
44When 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`:
45
46- Show planning status (e.g., `## ✓ Phase N Planned — M plans, K tasks` with brief plan list)
47- Emit a `## ▶ Next Up` heading with `/gsd:execute-phase N`
48- Use **`` `/clear` then: ``** before the command
49- Include a parenthetical: *(`/clear` is safe — `/gsd:resume-work` restores position from `HANDOFF.json` if you change your mind)*
50- Add an "Also available:" section: review the plan files, run `/gsd:list-phase-assumptions N`, etc.
51
52Plan-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.
53</output_format>
54
55---
56
57**Source:** [`davepoon/buildwithclaude`](https://github.com/davepoon/buildwithclaude) → `plugins/gsd/skills/plan-phase/SKILL.md`
thedixitjain