What problem does it solve? After the first playable slice of a game is defined, teams often either over-plan future releases in task-level detail that will inevitably change, or have no plan at all. This Skill produces a lightweight roadmap that sequences releases 2 and beyond as themes and hypotheses, ordered by which release yields the most decision-changing facts first. ## Core Features & Use Cases - Theme-based release sequencing: Groups leftover scope (below-the-line loop elements, unverified lean canvas hypotheses, unused market differentiation opportunities) into release themes with explicit hypotheses and dependencies. - Fact-driven ordering: Ranks releases by which one earliest produces a fact that could reshape the rest of the plan, rather than by convenience or effort. - Repeat-run support: Reads an existing roadmap artifact before rewriting it, preserving unaffected themes and dependencies after each release. - Use Case: After finishing a walking-skeleton slice of a mobile game, use this Skill to decide whether the next release should validate monetization or expand to a second player segment, and record the trigger that would force a replan. ## Quick Start Use the release-planning skill to build a roadmap of releases 2 and beyond based on my story_map and lean_canvas artifacts.
