mcpbeat

Gsd Manager

coco-research/gsd-manager

Interactive command center for managing multiple phases from one terminal

391 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
196
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/coco-research/coco --skill gsd-manager

The instruction itself

as written by the author

<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>

@$HOME/.claude/get-shit-done/workflows/manager.md

@$HOME/.claude/get-shit-done/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.cjs init manager. No upfront context loading needed.

</context>

<process>

Execute the manager workflow from @$HOME/.claude/get-shit-done/workflows/manager.md end-to-end.

Maintain the dashboard refresh loop until the user exits or all phases complete.

</process>

How to use it

Copy the folder

Take coco-research/gsd-manager from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.