create-orchestration-project
Skill1 starsChanged 5 months agoNo licenceView on GitHub
Bootstrap a brand-new orchestrated Claude Code project — interview the sponsor for vision + V1 scope, propose a project-tailored persona roster, then generate the full `.claude/` scaffolding (CLAUDE.md, agents, docs, hooks, maintain-docs skill, settings, decisions/away logs), initialize the GitHub repo, create the tracker board (ClickUp / Azure DevOps / etc.), and create per-role git worktrees. Use when the user says "create orchestration project", "/create-orchestration-project", "bootstrap a new orchestrated project", "set up a new team project like ClaudeTeam", or wants to start a multi-agent orchestrated project from scratch. Also supports sub-modes `register <path>` (record an existing orchestrated project in the registry without scaffolding), `port-improvements <project>` (diff a registered project's `.claude/` against this skill's `template/` and propose upgrades), `retrofit <path>` (add orchestration scaffolding to an EXISTING non-orchestrated git repo without destroying sponsor's prior work — trigger phrases: "retrofit", "orchestration-ify this existing repo"), and `unretrofit <path>` (surgically remove orchestration from a registered project — trigger phrases: "unretrofit", "remove orchestration from project"). The skill is tracker-agnostic: ClickUp and Azure DevOps are fully wired; Linear / Jira / GitHub Issues are placeholder-only. Each phase is a hard gate — the sponsor approves before the skill advances. The final scaffold step ALWAYS presents a confirmation block listing every external action (repo push, tracker setup, file writes, worktree creates) and refuses to act without an explicit Y from the sponsor.
In this repository22 other files it gives its agents.
- auto-pixellabSkill
- auto-statusSkill
- clone-sessionSkill
- codereviewSkill
- drain-and-save-sessionSkill
- drain-sessionSkill
- grill-meSkill
- investigateSkill
- keep-screens-aliveSkill
- mentor-modeSkill
- pbiSkill
- post-prSkill
- post-releaseSkill
- project-alignment-analysisSkill
- save-sessionSkill
- skill-creatorSkill
- skill-zip-shareSkill
- sponsor-questions-walkthroughSkill
- start-branchSkill
- start-flowSkill
- start-pbiSkill
- start-prSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 12 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.