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
26 lines
1.1 KiB
Markdown
26 lines
1.1 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-SCOPE — Scope and Timeline Validation
|
|
|
|
Agent: `producer` | Model tier: Opus | Domain: Scope, timeline, dependencies, production risk
|
|
|
|
**Trigger**: After scope tiers are defined (brainstorm Phase 6, map-systems Phase
|
|
4, or any workflow that produces an MVP definition and timeline estimate)
|
|
|
|
**Context to pass**:
|
|
- Full vision scope description
|
|
- MVP definition
|
|
- Timeline estimate
|
|
- Team size (solo / small team / etc.)
|
|
- Scope tiers (what ships if time runs out)
|
|
|
|
**Prompt**:
|
|
> "Review this scope estimate. Is the MVP achievable in the stated timeline for
|
|
> the stated team size? Are the scope tiers correctly ordered by risk — does each
|
|
> tier deliver a shippable product if work stops there? What is the most likely
|
|
> cut point under time pressure, and is it a graceful fallback or a broken product?
|
|
> Return REALISTIC (scope matches capacity), OPTIMISTIC [specific adjustments
|
|
> recommended], or UNREALISTIC [blockers — timeline or MVP must be revised]."
|
|
|
|
**Verdicts**: REALISTIC / OPTIMISTIC / UNREALISTIC
|