rollout-plan
Skill6 starsChanged 25 days agoNo licenceView on GitHub
How to order a change that alters data, schema or a cross-repo contract so each step is safe to deploy alone — expand → migrate → contract, one PR per step that is deployable and reversible on its own, compatibility shims and the rule for retiring them, why a feature flag does not protect a migration, the data-safety rules (export before a destructive step, dry-run, batches, verify counts; read-only queries, production only with explicit confirmation), and a plan template (step | PR | what changes | how to revert | verify). Use when a ticket carries the `rollout-plan` label, or before removing or renaming an endpoint, column, table, queue or config key that something else may use, or before a migration that alters or drops data. Invoke as /rollout-plan [TICKET-KEY].
In this repository18 other files it gives its agents.
- acceptance-criteriaSkill
- app-designSkill
- ci-cdSkill
- credentialsSkill
- definition-of-readySkill
- feature-flagsSkill
- gate-policiesSkill
- gitflowSkill
- grafana-dashboardsSkill
- kubectlSkill
- observabilitySkill
- pull-requestSkill
- refinement-contextSkill
- secret-or-settingSkill
- skill-designSkill
- task-trackerSkill
- test-appsSkill
- ticket-lifecycleSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
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.