Studio Production Planning
Overview
Provide an evidence-first contract for milestone scope, staffing, schedule, dependencies, critical path, confidence, and delivery forecast.
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 one feature breakdown, detailed task assignment, or release go/no-go.
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
- Bind the plan to a milestone goal, scope, constraints, and target date.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Map workstreams, owners, capacity, dependencies, and integration points.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Build a critical path with confidence ranges and explicit schedule assumptions.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Define milestone gates, change control, escalation thresholds, and reporting cadence.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Publish a forecast with blockers, decisions, and next review date.
Completion criterion: evidence is recorded and unresolved items are explicit.
Evidence and output contract
Produce production-plan.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: studio-production-planning3description: Use when a game milestone needs production planning across schedule, staffing, workstreams, dependencies, delivery forecast, scope, and milestone acceptance; not for decomposing one approved feature into work packets.4license: MIT5---6# Studio Production Planning78## Overview9Provide an evidence-first contract for milestone scope, staffing, schedule, dependencies, critical path, confidence, and delivery forecast.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 one feature breakdown, detailed task assignment, or release go/no-go.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. Bind the plan to a milestone goal, scope, constraints, and target date.25 Completion criterion: evidence is recorded and unresolved items are explicit.262. Map workstreams, owners, capacity, dependencies, and integration points.27 Completion criterion: evidence is recorded and unresolved items are explicit.283. Build a critical path with confidence ranges and explicit schedule assumptions.29 Completion criterion: evidence is recorded and unresolved items are explicit.304. Define milestone gates, change control, escalation thresholds, and reporting cadence.31 Completion criterion: evidence is recorded and unresolved items are explicit.325. Publish a forecast with blockers, decisions, and next review date.33 Completion criterion: evidence is recorded and unresolved items are explicit.3435## Evidence and output contract36Produce `production-plan.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