ksh999000/Claude-Code-Game-Studios
1
0
Fork 0
mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-06-27 04:51:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

Release v0.4.0: /consistency-check, skill fixes, genre-agnostic agents

Browse Source 
New skill: /consistency-check — cross-GDD entity registry scanner
New registries: design/registry/entities.yaml, docs/registry/architecture.yaml
Skill fixes: no-arg guards, verdict keywords, AskUserQuestion gates on all team-* skills
Agent fixes: genre-agnostic language in game-designer, systems-designer, economy-designer, live-ops-designer
Docs: skill/template counts corrected, stale references cleaned up

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Donchitos
2026-03-27 20:06:33 +11:00
parent 04ed5d5c36
commit 6c041ac1be
108 changed files with 2745 additions and 1005 deletions
Download Patch File Download Diff File Expand all files Collapse all files

94
.claude/skills/retrospective/SKILL.md
View File

@@ -8,41 +8,50 @@ context: |
!git log --oneline --since="2 weeks ago" 2>/dev/null
---
When this skill is invoked:
## Phase 1: Parse Arguments
1. **Read the argument** to determine whether this is a sprint retrospective
(`sprint-N`) or a milestone retrospective (`milestone-name`).
Determine whether this is a sprint retrospective (`sprint-N`) or a milestone retrospective (`milestone-name`).
2. **Read the sprint or milestone plan** from the appropriate location:
- Sprint plans: `production/sprints/`
- Milestone definitions: `production/milestones/`
---
Extract: planned tasks, estimated effort, owners, and goals.
## Phase 2: Load Sprint or Milestone Data
3. **Read the git log** for the period covered by the sprint or milestone to
understand what was actually committed and when.
Read the sprint or milestone plan from the appropriate location:
4. **Scan for completed and incomplete tasks** by comparing the plan against
actual deliverables. Check for:
- Tasks completed as planned
- Tasks completed but modified from the plan
- Tasks carried over (not completed)
- Tasks added mid-sprint (unplanned work)
- Tasks removed or descoped
- Sprint plans: `production/sprints/`
- Milestone definitions: `production/milestones/`
5. **Scan the codebase for TODO/FIXME trends**:
- Count current TODO/FIXME/HACK comments
- Compare to previous sprint counts if available (check previous
retrospectives)
- Note whether technical debt is growing or shrinking
Extract: planned tasks, estimated effort, owners, and goals.
6. **Read previous retrospectives** (if any) from `production/sprints/` or
`production/milestones/` to check:
- Were previous action items addressed?
- Are the same problems recurring?
- How has velocity trended?
Read the git log for the period covered by the sprint or milestone to understand what was actually committed and when.
7. **Generate the retrospective**:
---
## Phase 3: Analyze Completion and Trends
Scan for completed and incomplete tasks by comparing the plan against actual deliverables. Check for:
- Tasks completed as planned
- Tasks completed but modified from the plan
- Tasks carried over (not completed)
- Tasks added mid-sprint (unplanned work)
- Tasks removed or descoped
Scan the codebase for TODO/FIXME trends:
- Count current TODO/FIXME/HACK comments
- Compare to previous sprint counts if available (check previous retrospectives)
- Note whether technical debt is growing or shrinking
Read previous retrospectives (if any) from `production/sprints/` or `production/milestones/` to check:
- Were previous action items addressed?
- Are the same problems recurring?
- How has velocity trended?
---
## Phase 4: Generate the Retrospective
```markdown
## Retrospective: [Sprint N / Milestone Name]
@@ -136,23 +145,30 @@ tasks? What adjustment should we apply?]
the single most important thing to change going forward?]
```
8. **Save the retrospective** to the appropriate location:
- Sprint: `production/sprints/sprint-[N]-retrospective.md`
- Milestone: `production/milestones/[milestone-name]-retrospective.md`
---
Create the directory if it does not exist.
## Phase 5: Save Retrospective
9. **Output a summary** to the user with: completion rate, velocity trend
direction, top blocker, and the most important action item.
Present the retrospective and top findings to the user (completion rate, velocity trend, top blocker, most important action item).
Ask: "May I write this to `production/sprints/sprint-[N]-retrospective.md`?" (or the milestone path if applicable)
If yes, write the file, creating the directory if needed. Verdict: **COMPLETE** — retrospective saved.
If no, stop here. Verdict: **BLOCKED** — user declined write.
---
## Phase 6: Next Steps
- Run `/sprint-plan` to incorporate the action items and velocity data into the next sprint.
- If this was a milestone retrospective, run `/gate-check` to formally assess readiness for the next phase.
### Guidelines
- Be honest and specific. Vague retrospectives ("communication could be
better") produce vague improvements. Use data and examples.
- Be honest and specific. Vague retrospectives ("communication could be better") produce vague improvements. Use data and examples.
- Focus on systemic issues, not individual blame.
- Limit action items to 3-5. More than that dilutes focus.
- Every action item must have an owner and a deadline.
- Check whether previous action items were completed. Recurring unaddressed
items are a process smell.
- If this is a milestone retrospective, also evaluate whether the milestone
goals were achieved and what that means for the overall project timeline.
- Check whether previous action items were completed. Recurring unaddressed items are a process smell.
- If this is a milestone retrospective, also evaluate whether the milestone goals were achieved and what that means for the overall project timeline.