gsd-plan-phase

name	gsd-plan-phase
description	Create detailed phase plan (PLAN.md) with verification loop

<augment_skill_adapter>

A. Skill Invocation

• This skill is invoked when the user mentions gsd-plan-phase or describes a task matching this skill.
• Treat all user text after the skill mention as {{GSD_ARGS}}.
• If no arguments are present, treat {{GSD_ARGS}} as empty.

B. User Prompting

When the workflow needs user input, prompt the user conversationally:

• Present options as a numbered list in your response text
• Ask the user to reply with their choice
• For multi-select, ask for comma-separated numbers

C. Tool Usage

Use these Augment tools when executing GSD workflows:

• launch-process for running commands (terminal operations)
• str-replace-editor for editing existing files
• view for reading files and listing directories
• save-file for creating new files
• grep for searching code (or use MCP servers for advanced search)
• web-search, web-fetch for web queries
• add_tasks, view_tasklist, update_tasks for task management

D. Subagent Spawning

When the workflow needs to spawn a subagent:

• Use the built-in subagent spawning capability
• Define agent prompts in .augment/agents/ directory </augment_skill_adapter>

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.

<execution_context> @/home/delorenj/code/bhappy/.augment/get-shit-done/workflows/plan-phase.md @/home/delorenj/code/bhappy/.augment/get-shit-done/references/ui-brand.md </execution_context>

<runtime_note> Copilot (VS Code): Use vscode_askquestions wherever this workflow calls conversational prompting. They are equivalent — vscode_askquestions is the VS Code Copilot implementation of the same interactive question API. Do not skip questioning steps because conversational prompting appears unavailable; use vscode_askquestions instead. </runtime_note>

Phase number: {{GSD_ARGS}} (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)
• --mvp — Vertical MVP mode. Planner organizes tasks as feature slices (UI→API→DB) instead of horizontal layers. On Phase 1 of a new project, also emits SKELETON.md (Walking Skeleton). Can be persisted on a phase via **Mode:** mvp in ROADMAP.md.

Normalize phase input in step 2 before any directory lookups.

Execute the plan-phase workflow from @/home/delorenj/code/bhappy/.augment/get-shit-done/workflows/plan-phase.md end-to-end. Preserve all workflow gates (validation, research, planning, verification loop, routing).