Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed before release.
SkillScore87Maintained
Automatic
◆Product Management pack
Last verified 8/19/2026
What it changes
Passed 20 of 23 test cases with the skill, and 13 of 23 without it.
Without skill57%
With skill87%
Checks it passed that the model alone missed
Output includes a dedicated section for Design & UX.
Output includes a dedicated section for Open Issues.
Output includes a dedicated section for Launch Overview.
and 8 more in the full report
7 fixed13 passed either way3 still failing0 broke
Pass-rate lift
+30 pp
Tokens
+45%
Agent turns
0%
Response time
+15%
Model gemini-3.6-flashMeasured 8/19/2026v120 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
Our backend developer is fixing a minor typo in a log message for the internal auth microservice. There are no external dependencies or cross-functional impacts. How should we track and prepare this for deployment?
What was checked, without and with the skill
Checked
Without skill
With skill
Response advises against creating a multi-functional launch checklist for a single-team minor fix.
Missed
Passed
Response recommends tracking the fix within standard sprint workflows.
Passed
Passed
case-06 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md63 lines3 files
Launch Checklist
A launch checklist is a comprehensive verification document that ensures all functions are ready before releasing a feature or product. It coordinates across engineering, QA, design, marketing, support, legal, and operations to prevent launch-day surprises. Good launch checklists surface blockers early and create shared accountability for launch readiness.
When to Use
1-2 weeks before any significant launch
During launch planning kickoff meetings
When coordinating cross-functional releases
Before major version releases or feature rollouts
After incidents to improve launch processes
When NOT to Use
You are validating whether to ship at all via an experiment -> use measure-experiment-design
You need the customer-facing announcement of what shipped -> use deliver-release-notes
The launch already happened and you want results or reflection -> use measure-experiment-results or iterate-retrospective
The change is small and single-team with no cross-functional surface: a launch checklist adds ceremony without value; track it in the sprint instead
Instructions
When asked to create a launch checklist, follow these steps:
Define Launch Context
Document what is launching, when, and who the key stakeholders are. Establish the launch tier (major release, minor feature, experiment) as this affects checklist scope.
Gather Functional Requirements
For each function (engineering, QA, marketing, etc.), identify what must be complete, verified, or in place before launch. Distinguish between blockers (must-have) and nice-to-haves.
Assign Owners and Dates
Every checklist item needs an owner and a target completion date. Ownership creates accountability; dates enable tracking.
Identify Dependencies and Blockers
Flag items that block other work or are blocked by external factors. Surface these early so teams can unblock.
Define Go/No-Go Criteria
Establish clear criteria for making the launch decision. What conditions must be met? Who makes the final call?