What problem does it solve? Teams starting a new top-level objective often jump straight into issue creation and task dispatch, ending up with layer-based work splits (backend, frontend, database) that never assemble into a usable app. This Skill turns a brief into a concrete product plan before any sub-issues are created or agents are dispatched. ## Core Features & Use Cases - User journey mapping: Defines 3-7 end-to-end flows with entry points, action sequences, and exit states so every primary entity has a reachable creation path. - App shell specification: Documents global navigation, exact labels and URLs, empty-state CTAs, and where every "Create <Entity>" affordance lives. - Vertical chunk decomposition: Splits work into capability-oriented chunks of 2-5 features that one lead can own end-to-end, explicitly forbidding layer-based splits. - Slot-aware dispatch planning: Chooses between leads mode (4+ concurrent slots) and direct-builder mode (3 or fewer slots) based on maxConcurrent in .overstory/config.yaml. - Use Case: A coordinator receives a brief for a team management app. Before running sd create or ov sling, it invokes this Skill to produce .overstory/specs/<issue-id>.md containing journeys, nav spec, chunks like "Team management" and "Project kanban", and runtime acceptance criteria. ## Quick Start Ask the coordinator to run the product-plan skill on the new top-level objective brief before creating any sub-issues or dispatching leads.
