6.6 KiB
Skill Test Spec: /launch-checklist
Skill Summary
/launch-checklist generates and evaluates a complete launch readiness checklist
covering: legal compliance (EULA, privacy policy, ESRB/PEGI ratings), platform
certification status, store page completeness (screenshots, description, metadata),
build validation (version tag, reproducible build), analytics and crash reporting
configuration, and first-run experience verification.
The skill produces a checklist report written to production/launch/launch-checklist-[date].md
after a "May I write" ask. If a previous launch checklist exists, it compares the
new results against the old to highlight newly resolved and newly blocked items. No
director gates apply — /team-release orchestrates the full release pipeline. Verdicts:
LAUNCH READY, LAUNCH BLOCKED, or CONCERNS.
Static Assertions (Structural)
Verified automatically by /skill-test static — no fixture needed.
- Has required frontmatter fields:
name,description,argument-hint,user-invocable,allowed-tools - Has ≥2 phase headings
- Contains verdict keywords: LAUNCH READY, LAUNCH BLOCKED, CONCERNS
- Contains "May I write" collaborative protocol language before writing the checklist
- Has a next-step handoff (e.g.,
/team-releaseor/day-one-patch)
Director Gate Checks
None. /launch-checklist is a readiness audit utility. The full release pipeline
is managed by /team-release.
Test Cases
Case 1: Happy Path — All Checklist Items Verified, LAUNCH READY
Fixture:
- Legal docs present: EULA, privacy policy in
production/legal/ - Platform certification: marked as submitted and approved in production notes
- Store page assets: screenshots, description, metadata all present in
production/store/ - Build: version tag
v1.0.0exists, reproducible build confirmed - Crash reporting: configured in
technical-preferences.md
Input: /launch-checklist
Expected behavior:
- Skill checks all checklist categories
- All items pass their verification checks
- Skill produces checklist report with all items marked PASS
- Skill asks "May I write to
production/launch/launch-checklist-2026-04-06.md?" - Report written on approval; verdict is LAUNCH READY
Assertions:
- All checklist categories are checked (legal, platform, store, build, analytics, UX)
- All items appear in the report with PASS markers
- Verdict is LAUNCH READY
- "May I write" is asked with the correct dated filename
Case 2: Platform Certification Not Submitted — LAUNCH BLOCKED
Fixture:
- All other checklist items pass
- Platform certification section: "not submitted" (no submission record found)
Input: /launch-checklist
Expected behavior:
- Skill checks all items
- Platform certification check fails: no submission record
- Skill reports: "LAUNCH BLOCKED — Platform certification not submitted"
- Specific platform(s) missing certification are named
- Verdict is LAUNCH BLOCKED
Assertions:
- Verdict is LAUNCH BLOCKED (not CONCERNS)
- Platform certification is identified as the blocking item
- Missing platform names are specified
- All other passing items are still shown in the report
Case 3: Manual Check Required — CONCERNS Verdict
Fixture:
- All critical checklist items pass
- First-run experience item: "MANUAL CHECK NEEDED — human must play the first 5 minutes and verify tutorial completion flow"
- Store screenshots item: "MANUAL CHECK NEEDED — art team must verify screenshot quality matches current build"
Input: /launch-checklist
Expected behavior:
- Skill checks all items
- 2 items are flagged as requiring human verification
- Skill reports: "CONCERNS — 2 items require manual verification before launch"
- Both items are listed with instructions for what to manually verify
- Verdict is CONCERNS (not LAUNCH BLOCKED, since these are advisory)
Assertions:
- Verdict is CONCERNS (not LAUNCH READY or LAUNCH BLOCKED)
- Both manual check items are listed with verification instructions
- Skill does not auto-block on MANUAL CHECK items
Case 4: Previous Checklist Exists — Delta Comparison
Fixture:
production/launch/launch-checklist-2026-03-25.mdexists with previous results:- 2 items were BLOCKED (platform cert, crash reporting)
- 1 item had a MANUAL CHECK
- New checklist: platform cert is now PASS, crash reporting is now PASS, manual check still open; 1 new item flagged (EULA last updated date)
Input: /launch-checklist
Expected behavior:
- Skill finds the previous checklist and loads it for comparison
- Skill produces the new checklist and compares:
- Newly resolved: "Platform cert — was BLOCKED, now PASS"
- Newly resolved: "Crash reporting — was BLOCKED, now PASS"
- Still open: manual check (unchanged)
- New issue: EULA last updated date (not in previous checklist)
- Delta is shown prominently in the report
- Verdict is CONCERNS (manual check + new EULA question)
Assertions:
- Delta section shows newly resolved items
- Delta section shows new issues (not present in previous checklist)
- Still-open items from the previous checklist are noted as persistent
- Verdict reflects the current state (not the previous state)
Case 5: Director Gate Check — No gate; launch-checklist is an audit utility
Fixture:
- All checklist dependencies present
Input: /launch-checklist
Expected behavior:
- Skill runs the full checklist and writes the report
- No director agents are spawned
- No gate IDs appear in output
Assertions:
- No director gate is invoked
- No gate skip messages appear
- Verdict is LAUNCH READY, LAUNCH BLOCKED, or CONCERNS — no gate verdict
Protocol Compliance
- Checks all required categories (legal, platform, store, build, analytics, UX)
- LAUNCH BLOCKED for hard failures (uncompleted certifications, missing legal docs)
- CONCERNS for advisory items requiring manual verification
- Compares against previous checklist when one exists
- Asks "May I write" before creating the checklist report
- Verdict is LAUNCH READY, LAUNCH BLOCKED, or CONCERNS
Coverage Notes
- Region-specific compliance (GDPR data handling, COPPA for under-13 audiences) is checked but the specific requirements are not enumerated in test assertions.
- The store page completeness check (screenshots, description) relies on the
presence of files in
production/store/; it cannot verify visual quality. - Build reproducibility check validates the presence of a version tag and build configuration but does not execute the build process.