narrative-gameplay-handoff

name	narrative-gameplay-handoff
description	Produce an implementation-ready narrative design packet with state variables, triggers, conditions, IDs, quest graph, dialogue/lore dependencies, telemetry hooks, and test scenarios.

Narrative Gameplay Handoff

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using quest/state designs, game architecture, dialogue/lore assets, UI needs, localization, and QA constraints. Do not fill material gaps with assumptions when they can change the result.
3. Freeze narrative logic at handoff scope, define machine-readable identifiers and state transitions, list content dependencies, provide edge/recovery cases, and align with engineering/game design.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

Engineering and content specialists can implement/test the narrative without inventing missing logic.