implementation-handoff

To turn a slice plan into a build-ready handoff, provide the slice plan to generate a structured artifact defining Build Target, Scope, Gameplay Requirements, and Acceptance Criteria. This ensures developers know exactly what to build and how the player should experience it.

A slice plan handoff is a comprehensive implementation artifact that translates design intent into concrete build targets, gameplay requirements, and acceptance criteria. It bridges the gap between design and execution by providing developers with a structured template ready for review.

Prioritize gameplay requirements and mechanics for a prototype build by tagging each item with MUST, SHOULD, or COULD priorities. This explicitly identifies the core 'soul' of the mechanic to guide development and QA efforts effectively.

An implementation handoff artifact for early build targets should include Build Target, Scope, Gameplay Requirements, System Requirements, Asset and Test Hooks, Acceptance Criteria, Known Risks, and Review Logs. This templated layout ensures all execution details are preserved.

Yes, this handoff template applies directly to prototypes and early build targets where a coder needs a concrete artifact. It describes the intended experience, interactions, and acceptance criteria to ensure the design intent is fully preserved for build execution.

Handle known risks and test hooks by utilizing the generated handoff artifact layout, which explicitly includes sections for Asset and Test Hooks alongside Known Risks. This provides clear decision context and supports rapid iteration from slice plan to implementation.