launch-check

Verifies acceptance criteria evidence and rollback readiness before releasing a task slice.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/rombel00/game-processes --skill launch-check-rombel00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: launch-check
Source: https://github.com/rombel00/game-processes/tree/main/plugins/delivery/skills/launch-check
Command: npx skills add https://github.com/rombel00/game-processes --skill launch-check-rombel00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Green tests on mocks do not prove that the live verification promised in a task specification actually happened. This Skill performs the final pre-release check: it confirms each acceptance criterion in task_spec section 9 has real evidence, that rollback is possible, and that nothing promised in the lean canvas Channels was silently forgotten. ## Core Features & Use Cases - Evidence audit: Walks task_spec section 9 line by line, matching each acceptance criterion against the test_report to distinguish proven criteria from mock-only coverage or missing live checks. - Rollback readiness check: Verifies the release can be reverted without data loss, including feature flags that disable new behavior without a full rollback. - Playtest outcome handling: Distinguishes a disproven design hypothesis (recorded as done and routed to retro) from a check that never happened (blocked). - Use Case: After code review passes on a game feature slice, run this check to confirm the owner actually performed the manual real-environment verification before tagging the release. ## Quick Start Run the launch check on the current task slice using its task_spec and test_report to confirm it is ready for release.

Frequently Asked Questions about launch-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a release is ready after code review?▼

Run a launch check that walks the task specification acceptance criteria line by line and confirms each one has actual evidence in the test report. It also verifies rollback readiness and flags any criteria proven only by mock-based tests.

What is the difference between launch check and code review?▼

Code review evaluates code quality and tests, while launch check confirms the live verification promised in the task specification actually happened. Code reviewers are not required to manually test in a real environment, so a separate step confirms that honest fact.

When should a release be blocked instead of approved?▼

Block a release when an acceptance criterion lacks evidence, such as a required manual real-environment check that never occurred. A blocked result lists exactly which criterion is unproven and what evidence is missing.

What happens when a playtest disproves a design hypothesis?▼

A disproven hypothesis is recorded as done, not blocked, because the check was honestly performed. The finding is routed to the retro step to revisit the game loop design decision rather than treated as an implementation defect.

Can the product owner self-verify onboarding or readability criteria?▼

No, criteria about first impressions, onboarding, or rule readability cannot be closed by the author's own check since they know the game too well. These require testers seeing the game for the first time, as specified by the handoff or game loop design.