What problem does it solve? When a product slice is ready to move into development, teams often rewrite requirements from scratch, creating a second source of truth and losing acceptance criteria along the way. This Skill translates an existing story_map (or brief) into a task_spec by referencing what exists and adding only what the product track cannot provide: non-functional requirements, integration points, and constraints. ## Core Features & Use Cases - Slice Translation: References core loop, meta-loop, and progression units from story_map instead of rewriting them, copying acceptance criteria verbatim. - Gap Filling: Adds non-functional requirements (frame rate, target platforms, store certification), integration points, and constraints that product documents do not cover. - Verification Planning: Defines how each acceptance criterion will be proven (autotest, playtest, metric event) before development starts. - Use Case: A game team finishes its first playable slice definition and needs to hand it to developers. The Skill produces a task_spec with branch/base commit info, acceptance criteria, out-of-scope lists, and live verification methods, then routes it through a handoff review gate. ## Quick Start Use the handoff-spec skill to convert the approved story_map slice for Release 1 into a task_spec for the delivery track.
