Use when identifying launch risks, mitigation plans, and escalation owners.
SkillScore91Maintained
Automatic
◆Product Management pack
Last verified 8/23/2026
What it changes
Passed 21 of 23 test cases with the skill, and 16 of 23 without it.
Without skill70%
With skill91%
Checks it passed that the model alone missed
Includes an action tree
Assigns rollback path readiness to the Product & Reliability category
Categorizes messaging accuracy and asset approvals under Go-to-Market
and 3 more in the full report
6 fixed15 passed either way1 still failing1 broke
Pass-rate lift
+22 pp
Tokens
-14%
Agent turns
0%
Response time
-37%
Model gemini-3.6-flashMeasured 8/23/2026v121 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
Ahead of the StreamFlow 2.0 release, tier-2 support agents lack training on the new API endpoints, risking long queue times. The launch lead proposes putting this under External Factors due to user adoption. Which risk category explicitly covers support staffing and enablement coverage?
What was checked, without and with the skill
Checked
Without skill
With skill
Places support staffing levels and enablement coverage in Support & Success
Missed
Passed
case-04 · gemini-3.6-flash · 8/23/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md34 linessingle file
Launch Risk Playbooks Skill
When to Use
Pre-launch risk assessments and go/no-go criteria.
During launch week to monitor escalations and coordinate mitigations.
Post-launch retros to capture lessons and update future playbooks.
Framework
Launch risk governance combines categorical coverage with a repeatable execution cadence. Use the following building blocks to keep Tier 1+ launches on track.