Narrative Quest Content Contract
Overview
Provide an evidence-first contract for quest state, objectives, dialogue, conditions, rewards, failure, localization, telemetry, and implementation authority.
When to use
Use only for the trigger conditions in the description and when the requested artifact needs explicit owners, evidence, limitations, and verification.
When NOT to use
Do not use for general story ideation, packet protocols, or live content publication.
Required inputs and context discovery
Collect exact project and build identity, requested scope, owners, dependencies, constraints, existing evidence, commands, artifact paths, risks, approvals, rollback or recovery, and unavailable information.
Safety and risk level
Risk level is low. Read-only review never authorizes mutation. Any load, rollout, publication, service, database, credential, or external-system action requires explicit human approval and bounded stop conditions.
Workflow
- Define player intent, narrative purpose, entry conditions, and authority.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Model states, objectives, branches, failure, recovery, rewards, and completion.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Bind dialogue, cinematic, localization, audio, UI, data, and telemetry contracts.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Identify save compatibility, replay, sequencing, and content dependency risks.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Produce implementation acceptance criteria and unresolved decisions.
Completion criterion: evidence is recorded and unresolved items are explicit.
Evidence and output contract
Produce narrative-quest-contract.json with scope, snapshot, findings, owners, commands and exit codes, artifacts, acceptance criteria, Verified facts, Snapshot assumptions, Unverified hypotheses, BLOCKED items, and next actions.
Handoff contract
Record repository and path, goal, owned scope, do-not-touch scope, decisions, files changed, commands, exit codes, artifacts, restore information, blockers, next owner, and reactivation prompt.
Pitfalls and anti-rationalization
- Missing evidence is
BLOCKED, never PASS.
- A plan or review does not authorize production execution.
- Compile success, screenshots, or anecdotes do not prove broader coverage.
- Preserve unrelated work and generated-source ownership.
Verification checklist
References and scripts
No bundled runtime helper is required. Use project-owned plans, evidence, runbooks, schemas, and validation commands; repository governance tools remain full-clone-only.
1---2name: narrative-quest-content-contract3description: Use when narrative, quest, dialogue, objective, state, reward, localization, cinematic, and implementation teams need one explicit content contract; not for general story brainstorming or protocol review.4license: MIT5---6# Narrative Quest Content Contract78## Overview9Provide an evidence-first contract for quest state, objectives, dialogue, conditions, rewards, failure, localization, telemetry, and implementation authority.1011## When to use12Use only for the trigger conditions in the description and when the requested artifact needs explicit owners, evidence, limitations, and verification.1314## When NOT to use15Do not use for general story ideation, packet protocols, or live content publication.1617## Required inputs and context discovery18Collect exact project and build identity, requested scope, owners, dependencies, constraints, existing evidence, commands, artifact paths, risks, approvals, rollback or recovery, and unavailable information.1920## Safety and risk level21Risk level is `low`. Read-only review never authorizes mutation. Any load, rollout, publication, service, database, credential, or external-system action requires explicit human approval and bounded stop conditions.2223## Workflow241. Define player intent, narrative purpose, entry conditions, and authority.25 Completion criterion: evidence is recorded and unresolved items are explicit.262. Model states, objectives, branches, failure, recovery, rewards, and completion.27 Completion criterion: evidence is recorded and unresolved items are explicit.283. Bind dialogue, cinematic, localization, audio, UI, data, and telemetry contracts.29 Completion criterion: evidence is recorded and unresolved items are explicit.304. Identify save compatibility, replay, sequencing, and content dependency risks.31 Completion criterion: evidence is recorded and unresolved items are explicit.325. Produce implementation acceptance criteria and unresolved decisions.33 Completion criterion: evidence is recorded and unresolved items are explicit.3435## Evidence and output contract36Produce `narrative-quest-contract.json` with scope, snapshot, findings, owners, commands and exit codes, artifacts, acceptance criteria, Verified facts, Snapshot assumptions, Unverified hypotheses, BLOCKED items, and next actions.3738## Handoff contract39Record repository and path, goal, owned scope, do-not-touch scope, decisions, files changed, commands, exit codes, artifacts, restore information, blockers, next owner, and reactivation prompt.4041## Pitfalls and anti-rationalization42- Missing evidence is `BLOCKED`, never PASS.43- A plan or review does not authorize production execution.44- Compile success, screenshots, or anecdotes do not prove broader coverage.45- Preserve unrelated work and generated-source ownership.4647## Verification checklist48- [ ] Scope, identity, owners, and exclusions are explicit.49- [ ] Every verdict cites observed evidence or is labeled Unverified/BLOCKED.50- [ ] Risks have mitigations, triggers, owners, and dates.51- [ ] No unauthorized mutation, publication, deployment, or destructive action occurred.52- [ ] Handoff names the next bounded action.5354## References and scripts55No bundled runtime helper is required. Use project-owned plans, evidence, runbooks, schemas, and validation commands; repository governance tools remain full-clone-only.
hoatv2211