gsd-plan-phaselisted

<purpose> Create executable phase prompts (PLAN.md files) for a roadmap phase with integrated research and verification. Default flow: Research (if needed) -> Plan -> Verify -> Done. Orchestrates gsd-phase-researcher, gsd-planner, and gsd-plan-checker agents with a revision loop (max 3 iterations). </purpose> <required_reading> Read all files referenced by the invoking prompt's execution_context before starting. @~/.claude/gsd-core/references/ui-brand.md @~/.claude/gsd-core/references/revision-loop.md @~/.claude/gsd-core/references/gate-prompts.md @~/.claude/gsd-core/references/agent-contracts.md @~/.claude/gsd-core/references/gates.md </required_reading> <available_agent_types> Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'): - gsd-phase-researcher — Researches technical approaches for a phase - gsd-pattern-mapper — Analyzes codebase for existing patterns, produces PATTERNS.md - gsd-planner — Creates detailed plans from phase scope - gsd-plan-checker — Reviews plan quality before execution </available_agent_types> <process> ## 0. Git Branch Invariant **Do not create, rename, or switch git branches during plan-phase.** Branch identity is established at discuss-phase and is owned by the user's git workflow. A phase rename in ROADMAP.md is a plan-level change only — it does not mutate git branch names. If `phase_slug` in the init JSON differs from the current branch name, that is expected and correct; leave the branch unchanged. ## 1. I