agentleFS
Sign inStart free
sp1esp1e/claude-skills/gsd-manager/SKILL.md

gsd-manager

Skill1 starsChanged 31 days agoMITView on GitHub

Interactive command center for managing multiple phases from one terminal

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 2 are common, 0 are distinctive, and 2 are very specific to this project.

  • 2

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    No files created directly — dispatches to existing GSD commands via Skill() and background Task agents.

    line 23
  2. Common:

    No arguments required. Requires an active milestone with ROADMAP.md and STATE.md.

    line 35
  3. Very specific:

    If --analyze-deps is in $ARGUMENTS: Read and execute $HOME/.claude/get-shit-done/workflows/analyze-dependencies.md end-to-end.

    line 41
  4. Very specific:

    Read and execute $HOME/.claude/get-shit-done/workflows/analyze-dependencies.md end-to-end.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<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-sdk query init.manager. No upfront context loading needed. </context>

<process> If `--analyze-deps` is in $ARGUMENTS: Read and execute `$HOME/.claude/get-shit-done/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>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free