mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 01:37:05 +00:00
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
25 lines
1.1 KiB
Markdown
25 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.
|
|
|
|
# TD-FEASIBILITY — Technical Feasibility Assessment
|
|
|
|
Agent: `technical-director` | Model tier: Opus | Domain: Architecture, engine risk, performance
|
|
|
|
**Trigger**: After biggest technical risks are identified during scope/feasibility
|
|
(brainstorm Phase 6, or any early-stage concept with technical unknowns)
|
|
|
|
**Context to pass**:
|
|
- Concept's core loop description
|
|
- Platform target
|
|
- Engine choice (or "undecided")
|
|
- List of identified technical risks
|
|
|
|
**Prompt**:
|
|
> "Review these technical risks for a [genre] game targeting [platform] using
|
|
> [engine or 'undecided engine']. Flag any HIGH risk items that could invalidate
|
|
> the concept as described, any risks that are engine-specific and should influence
|
|
> the engine choice, and any risks that are commonly underestimated by solo
|
|
> developers. Return VIABLE (risks are manageable), CONCERNS [list with mitigation
|
|
> suggestions], or HIGH RISK [blockers that require concept or scope revision]."
|
|
|
|
**Verdicts**: VIABLE / CONCERNS / HIGH RISK
|