plan-rollout
Skill1 starsChanged 2 months agoNo licenceView on GitHub
Delivers a plan or ticket as merged PRs: two coordinator levels and their coding sub-agents falsify it against the repo, partition it into PR units, and run each as a build-review-fix-merge loop that continues until a human is genuinely needed. Use when a ticket or plan needs implementing through coding sub-agents; when partitioning work into PRs or dependency waves, dispatching an agent that edits or commits, choosing agent count/model, or placing a PR's review and fix passes; when a PR draws repeated finding rounds, or a finding needs a ticket versus a direct fix; when a sub-agent's deviation, a shared file, or merge/deploy ordering across PRs could bite; or when the change itself is tests or test infrastructure. Not authoring or reviewing the plan itself (plan-and-review), where a plan doc lives and how it stays true (plan-docs), verifying a single written claim outside a run (claims-and-scope-discipline), git and worktree mechanics (git-worktree-topology), or finding prose (review).
- Commits and pushes
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-styleSkill
- benchmark-code-graphsSkill
- bug-reportSkill
- claims-and-scope-disciplineSkill
- context7-mcpSkill
- dreamSkill
- dual-scoped-review-plansSkill
- git-worktree-topologySkill
- improve-memorySkill
- plan-and-reviewSkill
- plan-docsSkill
- reviewSkill
- root-cause-fixSkill
- send-resultsSkill
- session-analysisSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
3
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.