launch-checklist
Explicit invocation only: This skill should only run when the user explicitly requests it with
/launch-checklist. Do not auto-invoke based on context matching.
Phase 1: Parse Arguments
Read the argument for the launch date or dry-run mode. Dry-run mode generates the checklist without creating sign-off entries or writing files.
Phase 2: Gather Project Context
- Read
CLAUDE.mdfor tech stack, target platforms, and team structure - Read the latest milestone in
production/milestones/ - Read any existing release checklist in
production/releases/ - Read the content calendar in
design/live-ops/content-calendar.mdif it exists
Phase 3: Scan Codebase Health
More from donchitos/claude-code-game-studios
balance-check
Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.
125brainstorm
Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative exploration.
95playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
94team-narrative
Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.
92estimate
Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.
81asset-audit
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
78