manager
Skill102 starsChanged 8 days agoMITView on GitHub
Interactive command center for managing multiple phases from one terminal
7 other projects use a version of this.
Adopted by
Most recently taken up by
- serejaris/ris-claude-codetheir own version, first seen Oct 9, 2026
- RichieHakim/agent_skillstheir own version, first seen Oct 5, 2026
- Digital-Process-Tools/claude-osstheir own version, first seen Sep 30, 2026
- orrgal1/manager-skilltheir own version, first seen Sep 6, 2026
- serejaris/personal-corp-ostheir own version, first seen Aug 6, 2026
- rishbjain1/claude-stacktheir own version, first seen Jul 30, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- serejaris/personal-corp-os★ 243same name
- serejaris/ris-claude-code★ 243same name
- Digital-Process-Tools/claude-oss★ 5same name
- RichieHakim/agent_skills★ 5same name
- alexgrebeshok-coder/dirigent-skills★ 0same name
- orrgal1/manager-skill★ 0same name
- rishbjain1/claude-stack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository88 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- templates/copilot-instructions.mdCopilot instructions
- add-backlogSkill
- add-phaseSkill
- add-testsSkill
- add-todoSkill
- ai-integration-phaseSkill
- analyze-dependenciesSkill
- audit-fixSkill
- audit-milestoneSkill
- audit-uatSkill
- autonomousSkill
- check-todosSkill
- cleanupSkill
- code-review-fixSkill
- code-reviewSkill
- complete-milestoneSkill
- debugSkill
- discuss-phaseSkill
- docs-updateSkill
- doSkill
- eval-reviewSkill
- execute-phaseSkill
- exploreSkill
- extract-learningsSkill
- fastSkill
- forensicsSkill
- from-gsd2Skill
- graphifySkill
- healthSkill
- helpSkill
- importSkill
- inboxSkill
- ingest-docsSkill
- insert-phaseSkill
- intelSkill
- join-discordSkill
- list-phase-assumptionsSkill
- list-workspacesSkill
- map-codebaseSkill
- milestone-summarySkill
- mvp-phaseSkill
- new-dddSkill
- new-milestoneSkill
- new-projectSkill
- new-workspaceSkill
- nextSkill
- noteSkill
- pause-workSkill
- plan-milestone-gapsSkill
- plan-phaseSkill
- plant-seedSkill
- pr-branchSkill
- profile-userSkill
- progressSkill
- quickSkill
- reapply-patchesSkill
- reconcileSkill
- remember-accessSkill
- remove-phaseSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
No files created directly — dispatches to existing GSD commands via Skill() and background Task agents.
- Distinctive: line 32
No arguments required. Requires an active milestone with ROADMAP.md and STATE.md.
“Common” is measured: kept by at least 6 in 10 of the 5 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.
Files
<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_PLUGIN_ROOT}/workflows/manager.md @${CLAUDE_PLUGIN_ROOT}/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 bm-sdk query init.manager. No upfront context loading needed.
</context>
<process>
Execute the manager workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/manager.md end-to-end.
Maintain the dashboard refresh loop until the user exits or all phases complete.
</process>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
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.