* Add /vertical-slice skill, prototype overhaul, and workflow integration - Add /vertical-slice skill for pre-production validation (Phase 4 gate) - Overhaul /prototype skill with two-mode design: concept prototype (Phase 1) vs vertical slice (Phase 4), with clearer differentiation and higher standards for VS - Update prototyper agent to own both prototype and vertical-slice workflows - Add prototype-report.md and vertical-slice-report.md output templates - Update WORKFLOW-GUIDE, quick-start, skills-reference, agent-coordination-map, and skill-flow-diagrams to fully integrate both skills into the 7-phase pipeline - Remove orphaned empty quick-prototype/ directory Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * sync v1 counts + polish Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add entity inventory flow, relax vertical-slice gate, improve UX authoring prompts - /asset-spec: new Phase 0b entity & screen inventory when no argument and no existing inventory — reads GDDs/art-bible, proposes categorized list, writes design/assets/entity-inventory.md collaboratively - /asset-spec: entity/character target falls back to inline user description when no source doc exists, rather than failing - /gate-check: vertical slice changed from blocking to CONCERNS-only when absent; built-but-broken slice still fails; adds entity inventory as gate artifact - /ux-design: convert inline approval prompts to AskUserQuestion for structured option capture at key authoring decision points - workflow-catalog.yaml: entity-inventory step added to pre-production; UX spec min_count raised to 3; vertical-slice and prototype marked required: false with updated descriptions - .gitignore: exclude marrow/ eval tooling directory Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Add missing AskUserQuestion widgets to 7 skills Audit found 11 decision points across 7 skills where structured option prompts were missing — using plain text, auto-selection, or no gate at all. Skills patched: - create-epics: per-epic approval + producer CONCERNS verdict - sprint-plan: producer CONCERNS verdict with scope/timeline options - milestone-review: AT RISK / OFF TRACK producer verdicts require acknowledgement - retrospective: existing-retro handling converted from plain text [A]/[B] - quick-design: classification confirmation + draft approve/revise/redirect - tech-debt add mode: category (6 options) + effort (S/M/L/XL) structured capture - regression-suite: no-arg mode selection instead of silent auto-detect - hotfix: severity confirmation gate before workflow begins Also added AskUserQuestion to allowed-tools headers for retrospective, quick-design, tech-debt, regression-suite, and hotfix. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Prep v1 stable: fix WORKFLOW-GUIDE counts, stale agent names, and skill model fields - WORKFLOW-GUIDE.md: correct agent count (48→49), skill count (66/68→73), add 6 missing skills to Appendix B, fix Creative category count (2→4), replace 3 non-existent agent names with correct ue-*/unity-* specialists, add missing godot-csharp/gdextension specialists to hierarchy, fix production/stories/ paths → production/epics/ - coordination-rules.md: replace "not yet used" with opt-in env var note - quick-start.md: rename duplicate "Validate the concept" label → "Prototype the mechanic" - skill-flow-diagrams.md: remove duplicate legacy UX pipeline section - All 62 skills missing model: field now have explicit model: sonnet Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix: comprehensive skill audit — consistency, UX, and flow gaps Two-pass audit fixing ~35 bugs across 41 files. Pre-production flow: - Brainstorm next-steps split into Path A (design-first) and Path B (prototype-first) — eliminates "prototype after architecture" confusion - /architecture-review added to pre-production flow in brainstorm and create-architecture handoffs - gate-check traceability check corrected to requirements-traceability.md - dev-story TR registry error now points to /architecture-review (not /create-epics) - start now writes production/stage.txt on first onboarding AskUserQuestion gaps filled: - balance-check, code-review, hotfix, day-one-patch, consistency-check all gain closing widgets and/or missing allowed-tools declarations - hotfix git branch creation now requires user confirmation - sprint-plan review-mode setup moved to Phase 0 (before gates run) - team-combat gains architecture→implementation approval gate - design-review APPROVED path consolidated from 3 widgets to 1 multiSelect All 9 team-* skills: - Phase 0 review-mode resolution added (solo/lean/full now respected) - team-audio output path fixed (design/gdd/ → design/audio/) - team-level final doc compilation delegated to level-designer subagent - team-narrative localization-lead added to composition list - team-qa sprint path fixed (flat files, not directories) - team-release NO-GO override captures written justification - team-live-ops Cancel verdict now explicitly BLOCKED Other fixes: - Art bible path standardized to design/art/art-bible.md (3 wrong refs) - AD-PHASE-GATE added to lean-mode skip list in director-gates.md - design-system duplicate 5d heading fixed; skeleton decline path added; mandatory agent spawns now respect review mode - story-readiness acceptance criteria thresholds now type-aware - create-stories gains multi-ADR and no-ADR handling guidance - consistency-check creates docs/consistency-failures.md on first run - retrospective frontmatter bash injection replaced with explicit Bash call - smoke-check ls -t gains PowerShell fallback - Conventional Commits format documented in coding-standards.md - gate-check: ADR acceptance gate, QA plan check, chain-of-verification tool-action requirement all added Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix: expose --review flag in argument-hints for all team-* skills All 9 team-* skills already implement Phase 0 review-mode resolution internally (full/lean/solo), but none advertised [--review full|lean|solo] in their argument-hint. Users had no way to discover the per-run override. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * docs: add SECURITY.md with coordinated disclosure policy Defines scope, reporting process (GitHub private vulnerability reporting), contributor security guidelines for hooks/skills/agents, and 90-day coordinated disclosure timeline. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * docs: add CONTRIBUTING.md with framework contribution guidelines Covers what PRs are welcome, skill/hook/agent technical requirements, the collaborative principle, testing expectations, commit format, and platform compatibility requirements. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * docs: add v1.0.0-beta → v1.0 upgrade section to UPGRADING.md Documents the 17 commits since the beta tag: new /vertical-slice gate, entity inventory flow in /map-systems, AskUserQuestion widgets across 7 skills, --review flag exposure on team-* skills, bug fixes (#21, #36, #42, #43, #45), and the new CONTRIBUTING.md and SECURITY.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
4.5 KiB
CCGS Skill Testing Framework — Claude Instructions
This folder is the quality assurance layer for the Claude Code Game Studios skill/agent framework. It is self-contained and separate from any game project.
Key files
| File | Purpose |
|---|---|
catalog.yaml |
Master registry for all 73 skills and 49 agents. Contains category, spec path, and last-test tracking fields. Always read this first when running any test command. |
quality-rubric.md |
Category-specific pass/fail metrics. Read the matching ### section for the skill's category when running /skill-test category. |
skills/[category]/[name].md |
Behavioral spec for a skill — 5 test cases + protocol compliance assertions. |
agents/[tier]/[name].md |
Behavioral spec for an agent — 5 test cases + protocol compliance assertions. |
templates/skill-test-spec.md |
Template for writing new skill spec files. |
templates/agent-test-spec.md |
Template for writing new agent spec files. |
results/ |
Written by /skill-test spec when results are saved. Gitignored. |
Path conventions
- Skill specs:
CCGS Skill Testing Framework/skills/[category]/[name].md - Agent specs:
CCGS Skill Testing Framework/agents/[tier]/[name].md - Catalog:
CCGS Skill Testing Framework/catalog.yaml - Rubric:
CCGS Skill Testing Framework/quality-rubric.md
The spec: field in catalog.yaml is the authoritative path for each skill/agent spec.
Always read it rather than guessing the path.
Skill categories
gate → gate-check
review → design-review, architecture-review, review-all-gdds
authoring → design-system, quick-design, architecture-decision, art-bible,
create-architecture, ux-design, ux-review
readiness → story-readiness, story-done
pipeline → create-epics, create-stories, dev-story, create-control-manifest,
propagate-design-change, map-systems
analysis → consistency-check, balance-check, content-audit, code-review,
tech-debt, scope-check, estimate, perf-profile, asset-audit,
security-audit, test-evidence-review, test-flakiness
team → team-combat, team-narrative, team-audio, team-level, team-ui,
team-qa, team-release, team-polish, team-live-ops
sprint → sprint-plan, sprint-status, milestone-review, retrospective,
changelog, patch-notes
utility → all remaining skills
Agent tiers
directors → creative-director, technical-director, producer, art-director
leads → lead-programmer, narrative-director, audio-director, ux-designer,
qa-lead, release-manager, localization-lead
specialists → gameplay-programmer, engine-programmer, ui-programmer,
tools-programmer, network-programmer, ai-programmer,
level-designer, sound-designer, technical-artist
godot → godot-specialist, godot-gdscript-specialist, godot-csharp-specialist,
godot-shader-specialist, godot-gdextension-specialist
unity → unity-specialist, unity-ui-specialist, unity-shader-specialist,
unity-dots-specialist, unity-addressables-specialist
unreal → unreal-specialist, ue-gas-specialist, ue-replication-specialist,
ue-umg-specialist, ue-blueprint-specialist
operations → devops-engineer, security-engineer, performance-analyst,
analytics-engineer, community-manager
creative → writer, world-builder, game-designer, economy-designer,
systems-designer, prototyper
Workflow for testing a skill
- Read
catalog.yamlto get the skill'sspec:path andcategory: - Read the skill at
.claude/skills/[name]/SKILL.md - Read the spec at the
spec:path - Evaluate assertions case by case
- Offer to write results to
results/and updatecatalog.yaml
Workflow for improving a skill
Use /skill-improve [name]. It handles the full loop:
test → diagnose → propose fix → rewrite → retest → keep or revert.
Spec validity note
Specs in this folder describe current behavior, not ideal behavior. They were written by reading the skills, so they may encode bugs. When a skill misbehaves in practice, correct the skill first, then update the spec to match the fixed behavior. Treat spec failures as "this needs investigation," not "the skill is definitively wrong."
This folder is deletable
Nothing in .claude/ imports from here. Deleting this folder has no effect on the
CCGS skills or agents themselves. /skill-test and /skill-improve will report that
catalog.yaml is missing and guide the user to initialize it.