Turn a roadmap phase into executable PLAN.md files through research, planning, and repeated checks. Use requirements documents, verification gaps, or review feedback to shape the plan, then receive a continuation command for phase execution.
Create detailed phase plan (PLAN.md) with verification loop
Review the instructions the agent will receive before you install.
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. </objective>
<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 /rc remote sessions)Normalize phase input in step 2 before any directory lookups. </context>
<process> 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). </process><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:
## ✓ Phase N Planned — M plans, K tasks with brief plan list)## ▶ Next Up heading with /gsd:execute-phase N`/clear` then: before the command/clear is safe — /gsd:resume-work restores position from HANDOFF.json if you change your mind)/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>
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Handle ActiveCampaign contact and marketing tasks through Rube MCP, a connection for agent tools. Find or create contacts, manage tags and subscriptions, enroll contacts in existing automated workflows, and create follow-up tasks.
Research competitors’ live Meta and Google ads to identify opening hooks, offers, calls to action, and landing pages. Receive a sourced creative brief and up to three test ideas adapted to your product.
Add website or app tracking, then use command-line tools to review traffic, signups, drop-off, and returning users across projects. Run A/B tests, which compare alternative headlines or buttons, and inspect results to guide changes.
Establish rules for when an AI agent should recall past context and save lasting decisions, corrections, preferences, and failures. Works with Markdown files or memory services, preserving decision history and surfacing conflicting records.
Audit local AI coding-agent sessions with agenttrace to identify spending, token use, tool failures, and operational problems. Produce readable or structured reports and define pass-or-fail thresholds for automated continuous integration checks.
Audit saved agent sessions for access to private files and evidence that secret values entered an agent's context. Get findings without displaying secrets, identify keys needing rotation, and inspect Claude Code or Codex sessions in a local report.