$ARGUMENTS
The text inside <arguments> is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.
Designed for power users who want to parallelize work across phases from one terminal: discuss a phase while another plans or executes in the background.
Creates/Updates:
- No files created directly — dispatches to existing GSD commands via Skill() and background Task agents.
- Reads
.planning/STATE.md,.planning/ROADMAP.md, phase directories for status.
After: User exits when done managing, or all phases complete and milestone lifecycle is suggested.
<execution_context> @/.claude/gsd-core/workflows/manager.md @/.claude/gsd-core/references/ui-brand.md </execution_context>
Project context, phase list, dependencies, and recommendations are resolved inside the workflow using gsd-tools query init.manager. No upfront context loading needed.
Execute end-to-end. Maintain the dashboard refresh loop until the user exits or all phases complete.