gsd:plan-phase
GitHub用于创建包含验证循环的详细阶段计划(PLAN.md)。支持自动检测阶段、强制研究、跳过验证及基于PRD规划。通过解析参数、执行规划并迭代验证直至通过,最终输出状态及执行下一步指令。
Trigger Scenarios
Install
npx skills add davepoon/buildwithclaude --skill gsd:plan-phase -g -y
SKILL.md
Frontmatter
{
"name": "gsd:plan-phase",
"agent": "gsd-planner",
"description": "Create detailed phase plan (PLAN.md) with verification loop",
"allowed-tools": [
"Read",
"Write",
"Bash",
"Glob",
"Grep",
"Task",
"AskUserQuestion",
"WebFetch",
"mcp__context7__*"
],
"argument-hint": "[phase] [--auto] [--research] [--skip-research] [--gaps] [--skip-verify] [--prd <file>] [--reviews] [--text] [--tdd]"
}
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.
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/plan-phase.md @${CLAUDE_PLUGIN_ROOT}/references/ui-brand.md </execution_context>
<runtime_note>
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.
</runtime_note>
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/rcremote sessions)
Normalize phase input in step 2 before any directory lookups.
<output_format>
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 taskswith brief plan list) - Emit a
## ▶ Next Upheading with/gsd:execute-phase N - Use
`/clear` then:before the command - Include a parenthetical: (
/clearis safe —/gsd:resume-workrestores position fromHANDOFF.jsonif 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.
</output_format>
Version History
- 502fc01 Current 2026-07-05 15:14


