ksh999000/Claude-Code-Game-Studios
1
0
Fork 0
mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-10-16 01:37:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Release 1.1.2 — the default path works end to end

Browse Source 
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
This commit is contained in:
Donchitos
2026-09-29 21:32:19 +10:00
co-authored by Claude Opus 5.5
parent 7ed2c3e9c4
commit b21fa0f7f2
383 changed files with 22888 additions and 10618 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/docs/templates/vertical-slice-report.md
Vendored
+19 -5
View File
@@ -90,12 +90,14 @@ encounter, 0.5 days per UI screen"]
---
## Recommendation: [PROCEED / PIVOT / KILL]
## Recommendation: [PROCEED / PIVOT / KILL / NOT ASSESSED — the slice was built but nobody has played it]
[One paragraph with evidence — reference the validation question directly. Did a
player experience the core fantasy within the target time, without developer guidance?
Can the team build at this quality on the projected schedule?]
**Creative Director review (CD-PLAYTEST):** [APPROVE / CONCERNS / REJECT / NOT ASSESSED — the director's reason; or "not run — [review mode]"]
---
## If Proceeding
@@ -116,13 +118,25 @@ Can the team build at this quality on the projected schedule?]
**Performance targets:** [Confirmed / Revised — list changes if revised]
**Playtest note:** Run `/playtest-report` to structure additional session data
before running `/gate-check pre-production`.
before running `/gate-check production`.
**Next steps:**
1. `/gate-check pre-production` — formally advance to Production
2. `/create-epics layer:foundation` — plan Foundation layer epics
3. `/create-epics layer:core` — plan Core layer epics
1. `/create-epics layer:foundation` — plan Foundation layer epics
2. `/create-epics layer:core` — plan Core layer epics
3. `/create-stories [epic-slug]` — break each epic into stories
4. `/sprint-plan` — use velocity data from this report in the estimate
5. `/gate-check production` — formally advance to Production
---
## If Not Assessed
[The slice was built but nobody has played it through, so there is no evidence
for PROCEED, PIVOT or KILL yet.]
**Next step:** play the slice unguided (at least one documented session), then
re-run `/vertical-slice` — it resumes from the checkpoint in
`production/session-state/active.md`.
---