Steam Launch Readiness

Use this skill to turn a Steam release into a coordinated product, store, community, and live-ops launch.

Workflow

1. Identify game genre, audience, launch stage, monetization model, languages, and release strategy.
2. Read references/steam-launch-systems.md.
3. Audit store page promise, wishlist funnel, demo/playtest plan, build quality, community readiness, pricing, and support.
4. Separate pre-launch, launch-day, first-week, and post-launch operations.
5. Convert vague launch advice into decision gates: technical release gates, commercial policy gates, community response gates, and first-week learning gates with numeric or pre-agreed thresholds.
6. Verify store promise details against build proof: capsule, short description, tags, trailer, screenshots, achievements, cloud saves, controller support, settings, localization, system requirements, demo scope, and DLC wording.
7. Make player communication operational: bug-report format, known-issue state, ETA policy, support macro, public update cadence, and whether the fix is hotfix, rollback, copy change, or roadmap item.
8. Do not assert Steam discount/refund/review policy from memory. Use a policy-verification matrix and label numeric tripwires as internal starter thresholds unless the studio supplied approved targets.
9. Produce a readiness matrix with blockers, assets, telemetry, and review-risk mitigations.

When not to use

• Do not use for generic advice the base model already handles without this skill's specific artifact contract.