mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-06-27 13:01:50 +00:00
e289ce906f
* Add context resilience: file-backed state, incremental writing, auto-recovery Prevents "prompt too long" crashes from killing sessions by persisting work to disk incrementally instead of relying on conversation memory. Changes: - pre-compact.sh: dumps session state before context compression - session-start.sh: detects active.md for crash recovery - session-stop.sh: archives and clears active.md on clean shutdown - context-management.md: file-backed state as primary strategy - 9 agents updated with incremental section writing protocol (game-designer, systems-designer, economy-designer, narrative-director, level-designer, world-builder, writer, art-director, audio-director) - CLAUDE.md: trimmed redundant imports (10 → 5) to reduce token overhead - design-docs.md rule: enforces incremental writing pattern - .gitignore: excludes ephemeral session state files - directory-structure.md: documents session-state/ and session-logs/ - COLLABORATIVE-DESIGN-PRINCIPLE.md: documents incremental writing pattern Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add AskUserQuestion integration across collaborative protocols Explicitly reference the AskUserQuestion tool in all collaborative agent definitions, protocol templates, team orchestrator skills, and the master principle doc. Introduces the Explain-then-Capture pattern: agents write full expert analysis in conversation, then call AskUserQuestion with concise labels to capture decisions via structured UI. 26 files updated: - 3 protocol templates (design, leadership, implementation) - 14 agent definitions (10 design + 3 leadership + writer) - 8 orchestrator skills (brainstorm + 7 team-*) - 1 master principle doc (COLLABORATIVE-DESIGN-PRINCIPLE.md) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add /design-systems skill: concept-to-GDD decomposition workflow Bridges the gap between game concept and per-system design documents. Professional studios use systems enumeration + dependency sorting between concept and feature docs — skipping this step is one of the most expensive mistakes (systems discovered during production cost 5-10x more to add). New files: - .claude/skills/design-systems/SKILL.md — 7-phase orchestration skill (enumerate systems, map dependencies, assign priorities, write GDDs) - .claude/docs/templates/systems-index.md — master tracking template Flow integration (7 existing skills updated): - brainstorm, start, setup-engine, design-review, gate-check, project-stage-detect, game-concept template all reference /design-systems at the appropriate workflow touchpoints Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix cross-platform bugs, add missing tool permissions, and update docs for v0.2.0 Hooks: fix \s → [[:space:]] in grep -E fallbacks (3 files), fix detect-gaps.sh empty-variable bug, fix log-agent.sh field name (agent_name → agent_type), harden validate-push.sh with explicit $MATCHED_BRANCH, convert for-in loops to while-read for space-safe iteration, add POSIX head -n syntax, increase PreCompact timeout, widen session-stop log window. Skills: add AskUserQuestion to 10 skills and TodoWrite to 8 multi-phase skills. Fix project-stage-detect template/output paths, tech-artist → technical-artist. Docs: add /design-systems to all references (README, quick-start, workflow guide, skills-reference), update skill count 35 → 36, remove stale AI artifacts from COLLABORATIVE-DESIGN-PRINCIPLE.md, add AskUserQuestion note to examples README. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
82 lines
3.8 KiB
Markdown
82 lines
3.8 KiB
Markdown
---
|
|
name: team-release
|
|
description: "Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment."
|
|
argument-hint: "[version number or 'next']"
|
|
user-invocable: true
|
|
allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite
|
|
---
|
|
When this skill is invoked, orchestrate the release team through a structured pipeline.
|
|
|
|
**Decision Points:** At each phase transition, use `AskUserQuestion` to present
|
|
the user with the subagent's proposals as selectable options. Write the agent's
|
|
full analysis in conversation, then capture the decision with concise labels.
|
|
The user must approve before moving to the next phase.
|
|
|
|
## Team Composition
|
|
- **release-manager** — Release branch, versioning, changelog, deployment
|
|
- **qa-lead** — Test sign-off, regression suite, release quality gate
|
|
- **devops-engineer** — Build pipeline, artifacts, deployment automation
|
|
- **producer** — Go/no-go decision, stakeholder communication, scheduling
|
|
|
|
## How to Delegate
|
|
|
|
Use the Task tool to spawn each team member as a subagent:
|
|
- `subagent_type: release-manager` — Release branch, versioning, changelog, deployment
|
|
- `subagent_type: qa-lead` — Test sign-off, regression suite, release quality gate
|
|
- `subagent_type: devops-engineer` — Build pipeline, artifacts, deployment automation
|
|
- `subagent_type: producer` — Go/no-go decision, stakeholder communication
|
|
|
|
Always provide full context in each agent's prompt (version number, milestone status, known issues). Launch independent agents in parallel where the pipeline allows it (e.g., Phase 3 agents can run simultaneously).
|
|
|
|
## Pipeline
|
|
|
|
### Phase 1: Release Planning
|
|
Delegate to **producer**:
|
|
- Confirm all milestone acceptance criteria are met
|
|
- Identify any scope items deferred from this release
|
|
- Set the target release date and communicate to team
|
|
- Output: release authorization with scope confirmation
|
|
|
|
### Phase 2: Release Candidate
|
|
Delegate to **release-manager**:
|
|
- Cut release branch from the agreed commit
|
|
- Bump version numbers in all relevant files
|
|
- Generate the release checklist using `/release-checklist`
|
|
- Freeze the branch — no feature changes, bug fixes only
|
|
- Output: release branch name and checklist
|
|
|
|
### Phase 3: Quality Gate (parallel)
|
|
Delegate in parallel:
|
|
- **qa-lead**: Execute full regression test suite. Test all critical paths. Verify no S1/S2 bugs. Sign off on quality.
|
|
- **devops-engineer**: Build release artifacts for all target platforms. Verify builds are clean and reproducible. Run automated tests in CI.
|
|
|
|
### Phase 4: Localization and Performance
|
|
Delegate (can run in parallel with Phase 3 if resources available):
|
|
- Verify all strings are translated (delegate to localization-lead if available)
|
|
- Run performance benchmarks against targets (delegate to performance-analyst if available)
|
|
- Output: localization and performance sign-off
|
|
|
|
### Phase 5: Go/No-Go
|
|
Delegate to **producer**:
|
|
- Collect sign-off from: qa-lead, release-manager, devops-engineer, technical-director
|
|
- Evaluate any open issues — are they blocking or can they ship?
|
|
- Make the go/no-go call
|
|
- Output: release decision with rationale
|
|
|
|
### Phase 6: Deployment (if GO)
|
|
Delegate to **release-manager** + **devops-engineer**:
|
|
- Tag the release in version control
|
|
- Generate changelog using `/changelog`
|
|
- Deploy to staging for final smoke test
|
|
- Deploy to production
|
|
- Monitor for 48 hours post-release
|
|
|
|
### Phase 7: Post-Release
|
|
- **release-manager**: Generate release report (what shipped, what was deferred, metrics)
|
|
- **producer**: Update milestone tracking, communicate to stakeholders
|
|
- **qa-lead**: Monitor incoming bug reports for regressions
|
|
- Schedule post-release retrospective if issues occurred
|
|
|
|
## Output
|
|
A summary report covering: release version, scope, quality gate results, go/no-go decision, deployment status, and monitoring plan.
|