mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 01:37:05 +00:00
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
25 lines
1.0 KiB
Markdown
25 lines
1.0 KiB
Markdown
> Gate definition. The spawning skill passes this file's path to the director agent; the AGENT reads it — the parent session should not.
|
|
|
|
# PR-MILESTONE — Milestone Risk Assessment
|
|
|
|
Agent: `producer` | Model tier: Opus | Domain: Scope, timeline, dependencies, production risk
|
|
|
|
**Trigger**: At milestone review (`/milestone-review`), or when a scope change is
|
|
proposed that affects the milestone
|
|
|
|
**Context to pass**:
|
|
- Milestone definition and target date
|
|
- Current completion percentage
|
|
- Blocked stories count
|
|
- Sprint velocity data (if available)
|
|
|
|
**Prompt**:
|
|
> "Review this milestone status. Based on current velocity and blocked story count,
|
|
> will this milestone hit its target date? What are the top 3 production risks
|
|
> between now and the milestone? Are there scope items that should be cut to protect
|
|
> the milestone date vs. items that are non-negotiable? Return ON TRACK, AT RISK
|
|
> [specific mitigations], or OFF TRACK [date must slip or scope must cut — provide
|
|
> both options]."
|
|
|
|
**Verdicts**: ON TRACK / AT RISK / OFF TRACK
|