DonchitosandClaude Opus 5.5
b21fa0f7f2
Fix release for 1.1.1: the minimal path end to end, engine commands that run on Godot, Unity and Unreal, hook warnings you can see, and verdicts that say when they could not check. Details in CHANGELOG.md; upgrade steps in UPGRADING.md (v1.1.1 → v1.1.2). Fixes #67 Fixes #131 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WuJn2FdynEybfL5KC697nJ
1.9 KiB
Gate definition. The spawning skill passes this file's path to the director agent; the AGENT reads it — the parent session should not.
PR-PHASE-GATE — Production Readiness at Phase Transition
Agent: producer | Model tier: Opus | Domain: Scope, timeline, dependencies, production risk
Trigger: At every /gate-check director panel — producer is on the panel at every modes.workflow; spawn in parallel with the rest of it (alone at minimal, with TD-PHASE-GATE at standard, with TD-PHASE-GATE, CD-PHASE-GATE and AD-PHASE-GATE at full)
Context to pass:
- Target phase name and the resolved
workflowtier - The target gate's required and recommended artifacts at the resolved tier (from
/gate-check's loaded gate file) - Sprint and milestone artifacts present — at
minimal, the Build order indesign/game-brief.mdis the plan (that tier has no sprint plan) - Team size (
team.size) and sprint capacity (from the current sprint plan, if one exists) - Current blocked story count
Prompt:
"Review the current project state for [target phase] gate readiness from a production perspective, judged against what this gate requires at this tier (the required-artifacts list you were given). Is the scope realistic for the stated timeline and team size? Is the work of [target phase] planned to the depth this gate requires — from the Production gate on, a sprint plan at
standard/fulland the brief's Build order atminimal; before it, no sprint plan is expected — and are its dependencies ordered so the team can execute it in sequence? What milestone or schedule risks could derail the start of [target phase] (its first two sprints, where the tier plans in sprints)? A required artifact passed as "none" is a finding; one passed as "not expected before [phase]" or "not required atworkflow: [tier]" is not a finding. Return READY, CONCERNS [list], or NOT READY [blockers]."
Verdicts: READY / CONCERNS / NOT READY