/manager
Interactive command center for managing multiple phases from one terminal
> /plugin marketplace add open-gsd/gsd-core > /plugin install gsd-core@gsd-core
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/manager
Context preview
What this command does when you run it.
Interactive command center for managing multiple phases from one terminal
Command definition
manager.mdname: gsd:manager
description: Interactive command center for managing multiple phases from one terminal
argument-hint: "[--analyze-deps]"
allowed-tools:
- Read
- Write
- Bash
- Glob
- Grep
- AskUserQuestion
- Skill
- Agent
requires: [phase]
<objective> Single-terminal command center for managing a milestone. Shows a dashboard of all phases with visual status indicators, recommends optimal next actions, and dispatches work — discuss runs inline, plan/execute run as background agents.
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. </objective>
<execution_context> @~/.claude/gsd-core/workflows/manager.md @~/.claude/gsd-core/references/ui-brand.md </execution_context>
<context> No arguments required. Requires an active milestone with ROADMAP.md and STATE.md.
Project context, phase list, dependencies, and recommendations are resolved inside the workflow using `gsd-tools query init.manager`. No upfront context loading needed. </context>
<process> If `--analyze-deps` is in $ARGUMENTS: Read and execute `~/.claude/gsd-core/workflows/analyze-dependencies.md` end-to-end.
Execute end-to-end. Maintain the dashboard refresh loop until the user exits or all phases complete. </process>
Read more
name: gsd:manager description: Interactive command center for managing multiple phases from one terminal argument-hint: "[--analyze-deps]" allowed-tools: - Read - Write - Bash - Glob - Grep - AskUserQuestion - Skill - Agent requires: [phase]
<objective> Single-terminal command center for managing a milestone. Shows a dashboard of all phases with visual status indicators, recommends optimal next actions, and dispatches work — discuss runs inline, plan/execute run as background agents.
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. </objective>
<execution_context> @~/.claude/gsd-core/workflows/manager.md @~/.claude/gsd-core/references/ui-brand.md </execution_context>
<context> No arguments required. Requires an active milestone with ROADMAP.md and STATE.md.
Project context, phase list, dependencies, and recommendations are resolved inside the workflow using `gsd-tools query init.manager`. No upfront context loading needed. </context>
<process> If `--analyze-deps` is in $ARGUMENTS: Read and execute `~/.claude/gsd-core/workflows/analyze-dependencies.md` end-to-end.
Execute end-to-end. Maintain the dashboard refresh loop until the user exits or all phases complete. </process>
Git. Ship. Done. A light-weight meta-prompting, context engineering, and spec-driven development system for Claude Code, OpenCode, Antigravity CLI, Kimi CLI, Kilo, Codex, Copilot, Cursor, Windsurf, and more.
Repo: open-gsd/gsd-core
Other commands on gsd-core.
- /add-tests
Generate tests for a completed phase based on UAT criteria and implementation
Open command - /ai-integration-phase
Generate an AI-SPEC.md design contract for phases that involve building AI systems.
Open command - /audit-fix
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit
Open command - /audit-milestone
Audit milestone completion against original intent before archiving
Open command - /audit-uat
Cross-phase audit of all outstanding UAT and verification items
Open command - /autonomous
Run all remaining phases autonomously — discuss→plan→execute per phase
Open command

