What problem does it solve? Game development plans often degrade into task lists that cannot be verified or lose their status history when rebuilt. This Skill structures plans so every task can be checked with a single playtest and every rebuild preserves existing statuses and IDs. ## Core Features & Use Cases - Playtest-driven task slicing: Splits work into vertical slices where each task is verified by one playtest, with a mandatory "How to verify" section describing what to press and what should happen. - Milestone and version management: Orders tasks so playability arrives early, keeps exactly one version as current, and parks deferred work in a backlog milestone. - Merge-based plan rebuilds: Rebuilds plans without resetting statuses, reusing IDs, or reopening closed versions, using board.js for ID allocation and validation. - Use Case: When running /plan on an RTS engine project, generate a first version covering scene setup, player control, combat, defeat/restart, and scoring, each task verifiable in one playtest. ## Quick Start Ask the assistant to run /plan and build or rebuild the development plan for the current game version.
