launch-readiness-gate
Skill0 starsChanged 4 months agoMITView on GitHub
Ensure a feature or change is truly ready to launch before declaring release readiness. Use for launches, cutovers, and go-live checks.
In this repository32 other files it gives its agents.
- architect-modeSkill
- architecture-bundleSkill
- code-like-a-localSkill
- decision-making-guardrailsSkill
- decision-recordsSkill
- delivery-bundleSkill
- fable-modeSkill
- finish-the-turnSkill
- incident-response-playbookSkill
- lead-developer-modeSkill
- lead-with-outcomeSkill
- lean-tool-useSkill
- migration-refactor-safetySkill
- plan-before-implementationSkill
- pr-and-commit-hygieneSkill
- product-delivery-bundleSkill
- product-minded-engineer-modeSkill
- reliability-bundleSkill
- reliability-incident-modeSkill
- review-quality-gateSkill
- run-guardrails-on-code-changesSkill
- security-bundleSkill
- security-minded-engineer-modeSkill
- senior-operating-systemSkill
- staff-engineering-bundleSkill
- staff-engineer-modeSkill
- stakeholder-communicationSkill
- surgical-questionsSkill
- systematic-debuggingSkill
- test-disciplineSkill
- truthful-reportingSkill
- verify-by-exercisingSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
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 8
Do not call a launch ready until the change is verified, the support path is clear, and the rollout plan is credible.
- Distinctive: line 13
Verify that monitoring, alerts, and rollback procedures are in place.
- Distinctive: line 14
Check that support and ownership are clear.
- Distinctive: line 19
Do not claim readiness based on local success alone.
- Distinctive: line 20
Do not skip support, rollback, or incident handling plans.
- Distinctive: line 21
Do not declare a launch ready when key risks are still unresolved.
- Distinctive: line 22
Do not treat launch as a single event when it is really a staged rollout.
- Distinctive: line 24
Use this skill to keep launches disciplined and less fragile.
≈ “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.
Files
Launch readiness gate
Do not call a launch ready until the change is verified, the support path is clear, and the rollout plan is credible.
Required readiness checks
- Confirm the intended behavior is verified in the target environment.
- Verify that monitoring, alerts, and rollback procedures are in place.
- Check that support and ownership are clear.
- Confirm that the launch plan accounts for dependencies, traffic patterns, and known risks.
Non-negotiables
- Do not claim readiness based on local success alone.
- Do not skip support, rollback, or incident handling plans.
- Do not declare a launch ready when key risks are still unresolved.
- Do not treat launch as a single event when it is really a staged rollout.
Use this skill to keep launches disciplined and less fragile.
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.