New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Sprint Retrospective

by Donchitos in Donchitos/Claude-Code-Game-Studios

Builds a sprint or milestone retrospective from completed work, velocity and blockers, checking first for an existing retrospective file.

MITAuto-check: notesProduct & Project Management

Install Sprint Retrospective

skills CLI
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill retrospective -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Donchitos/Claude-Code-Game-Studios retrospective --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/retrospective .claude/skills/retrospective && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
retrospective
GitHub stars
26k
Token cost
~3.1k tokens
SKILL.md length
1,261 words
Files
1
Skills in repo
73
Repo updated
First seen
Licence
MIT

At a glance

Builds a sprint or milestone retrospective from completed work, velocity and blockers, checking first for an existing retrospective file.

  • Works in 6 steps: Parse Arguments → Load Sprint or Milestone Data → Analyze Completion and Trends → …
  • Closing a sprint with a written look at what went well and what blocked the team
  • SKILL.md covers Insufficient input — check…, Phase 1: Parse Arguments, Phase 1b: Check for Existing… and Phase 2: Load Sprint or…, plus 4 more sections
  • Calls git and bash

What it does

You name a sprint (as `sprint-N`) or a milestone, and the skill produces a retrospective from the work that was completed, the velocity and the blockers, ending in actionable points for the next iteration. Before loading any data it looks for an existing retrospective under `production/retrospectives/`, or in the sprint folder for sprints, and asks what to do if it finds one.

Like other report skills in this framework, it first records which required inputs are found or absent. Sections without data are marked NOT ASSESSED instead of being estimated, and a run with no data at all stops with that verdict and names the missing inputs. A config helper supplies the automation mode, which governs how often it asks before writing.

When your agent uses it

  • Closing a sprint with a written look at what went well and what blocked the team
  • Reviewing a whole milestone for lessons to carry into the next one
  • Avoiding a duplicate retrospective when one already exists for the sprint

Example prompts

  • “Run a retrospective for sprint-4.”
  • “Write the retrospective for the vertical slice milestone from our completed stories.”
  • “Summarize velocity and blockers for the last sprint and suggest changes for the next one.”

Requirements

  • Sprint and story records under `production/`
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Bash, AskUserQuestion, Bash(bash "*/.claude/skills/retrospective/../../hooks/yaml-helper.sh" resolve_config *)

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Parse Arguments
  2. Load Sprint or Milestone Data
  3. Analyze Completion and Trends
  4. Generate the Retrospective
  5. Save Retrospective
  6. Next Steps

What it can do on your machine

Read from SKILL.md and the folder at commit be8993b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Write
    • Bash
    • AskUserQuestion
    • Bash(bash "*/.claude/skills/retrospective/../../hooks/yaml-helper.sh" resolve_config *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sprint Retrospective loads about 3.1k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 1,261 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Glob, Grep, Write, Bash, AskUserQuestion, Bash(bash "*/.claude/skills/retrospective/../../hook

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Donchitos/Claude-Code-Game-Studios at commit be8993b, republished under its MIT licence (© Donchitos). 1,261 words, ~3,086 tokens.

Download SKILL.mdSave it as .claude/skills/retrospective/SKILL.md (or your agent's skills folder).
name
retrospective
description
Sprint or milestone retrospective from completed work, velocity, blockers. Actionable insights for the next iteration.
allowed-tools
Read, Glob, Grep, Write, Bash, AskUserQuestion, Bash(bash "*/.claude/skills/retrospective/../../hooks/yaml-helper.sh" resolve_config *)
argument-hint
[sprint-N|milestone-name]
user-invocable
true
model
sonnet

!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow,qa.level

Retrospective

Every AskUserQuestion call follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and proceeds; automation_always_ask categories always prompt).

Insufficient input — check this before producing any report

If the inputs this skill needs do not exist, the answer is "could not run" — not a filled-in report. Check first, and stop if the check fails.

  1. List the inputs this skill reads (data files, prior reports, profiler output, test results, registries, source code).
  2. For each, record FOUND or ABSENT — not "assumed present".
  3. If any input required for a section is ABSENT, that section is NOT ASSESSED — NO DATA. Do not estimate it, do not infer it from an adjacent artifact, and do not leave a mandated cell to be filled by whoever reads the template next.
  4. If every required input is ABSENT, stop and report NOT ASSESSED — NO DATA as the whole verdict, naming what was missing and which skill produces it.

A verdict of NOT ASSESSED is a success. It is the correct, useful answer to "what does the data say?" when there is no data. The failure mode this prevents is specific: a report whose verdict enum has no "could not run" state produces false clean passes — an asset audit returning COMPLIANT on a project with no assets and no standards, or a performance profile reporting ">99% headroom against a 16.67ms budget" with zero profiler data and no budget ever set.

Absence of evidence is never evidence of absence. A scan that finds no matches because there are no files to scan has not verified anything. Say which of the two happened — a reader cannot tell from a green result.

Phase 1: Parse Arguments

Determine whether this is a sprint retrospective (sprint-N) or a milestone retrospective (milestone-name).

Phase 1b: Check for Existing Retrospective

Before loading any data, glob for an existing retrospective file:

  • For sprint retrospectives: production/retrospectives/retro-[sprint-slug]-*.md (also check production/sprints/sprint-[N]-retrospective.md as an alternate location)
  • For milestone retrospectives: production/retrospectives/retro-[milestone-name]-*.md

If a matching file is found, use AskUserQuestion:

  • Prompt: "An existing retrospective was found: [filename]. How do you want to proceed?"
  • Options:
    • [A] Update existing — load it and add/revise sections with new data
    • [B] Start fresh — generate a new retrospective (archive the old one)

If [A]: read the existing file and carry its content forward, revising sections with new data. If [B]: continue to Phase 2 with a blank slate. Before writing the new file, rename the existing one with a -archived-[date] suffix. That rename is a write too: it happens in Phase 5, only once the ask there — which names it — is approved.

Phase 2: Load Sprint or Milestone Data

Read the sprint or milestone plan from the appropriate location:

  • Sprint plans: production/sprints/
  • Milestone definitions: production/milestones/

Also check for production/sprint-status.yaml: if it exists, read it alongside the sprint plan. It is the authoritative source for actual story completion status (status: done, completed dates, blockers). Use it as the primary source for completion metrics in Phase 3. Fall back to markdown scanning only if the yaml does not exist. Note discrepancies between the yaml and the sprint plan (e.g., stories in yaml not in plan, or vice versa).

If the file does not exist or is empty, output:

"No sprint data found for [sprint/milestone]. Run /sprint-plan new to create a sprint (/sprint-status only reads one), or provide the sprint details manually."

At workflow: minimal (resolved above) there are no sprints: offer to look back over the stories closed so far instead (production/epics/*/story-*.md with Status: Complete). At qa.level: minimal (resolved above) tests are waived, so a story closed without one is not a finding; a Visual/Feel or UI story closed without its retained screenshot still is.

Then use AskUserQuestion to present these options ([C] only at workflow: minimal):

  • [A] Provide data manually — ask the user to paste or describe the sprint tasks, dates, and outcomes; use that as the source of truth for the retrospective.
  • [B] Stop — abort the skill. Verdict: BLOCKED — no sprint data available.
  • [C] Look back over the closed stories — use the stories with Status: Complete as the record of what was done.

If the user chooses [A], collect the data and continue to Phase 3 using what they provide. If the user chooses [B], stop here. If the user chooses [C], read those stories and continue to Phase 3. Sections that need sprint data (planned vs actual, velocity, carryover, estimation accuracy) are NOT ASSESSED — NO DATA.

Extract: planned tasks, estimated effort, owners, and goals.

Run git log for the sprint period to understand what was actually committed and when. Use the Bash tool (which uses Git Bash on Windows — the 2>/dev/null is bash syntax, not PowerShell):

Bash: git log --oneline --since="4 weeks ago" 2>/dev/null || git log --oneline -20

Adjust the --since date to match the sprint duration if known from the sprint plan.

Show full SKILL.md (470 more words)Show less

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

Every story with status: blocked in production/sprint-status.yaml goes under Blockers Encountered, with its blocker field as the Blocker, and gets an action item in Action Items for Next Iteration.

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/retrospectives/ to check:

  • Were previous action items addressed?
  • Are the same problems recurring?
  • How has velocity trended?

With no earlier sprint or retrospective, Velocity Trend keeps only the current sprint's row and reads NOT ASSESSED — NO DATA, and Previous Action Items Follow-Up is that one line — no invented earlier rows, no empty table.

Phase 4: Generate the Retrospective

markdown
## Retrospective: [Sprint N / Milestone Name]
Period: [Start Date] -- [End Date]
Generated: [Date]

### Metrics

| Metric | Planned | Actual | Delta |
|--------|---------|--------|-------|
| Tasks | [X] | [Y] | [+/- Z] |
| Completion Rate | -- | [Z%] | -- |
| Story Points / Effort Days | [X] | [Y] | [+/- Z] |
| Bugs Found | -- | [N] | -- |
| Bugs Fixed | -- | [N] | -- |
| Unplanned Tasks Added | -- | [N] | -- |
| Commits | -- | [N] | -- |

### Velocity Trend

| Sprint | Planned | Completed | Rate |
|--------|---------|-----------|------|
| [N-2] | [X] | [Y] | [Z%] |
| [N-1] | [X] | [Y] | [Z%] |
| [N] (current) | [X] | [Y] | [Z%] |

**Trend**: [Increasing / Stable / Decreasing — or `NOT ASSESSED — NO DATA` with no earlier sprint to compare]
[One sentence explaining the trend]

### What Went Well
- [Observation backed by specific data or examples]
- [Another positive observation]
- [Recognize specific contributions or decisions that paid off]

### What Went Poorly
- [Specific issue with measurable impact -- e.g., "Feature X took 5 days
  instead of estimated 2, blocking tasks Y and Z"]
- [Another issue with impact]
- [Do not assign blame -- focus on systemic causes]

### Blockers Encountered

| Blocker | Duration | Resolution | Prevention |
|---------|----------|------------|------------|
| [What blocked progress] | [How long] | [How it was resolved] | [How to prevent recurrence] |

### Estimation Accuracy

| Task | Estimated | Actual | Variance | Likely Cause |
|------|-----------|--------|----------|--------------|
| [Most overestimated task] | [X] | [Y] | [+Z] | [Why] |
| [Most underestimated task] | [X] | [Y] | [-Z] | [Why] |

**Overall estimation accuracy**: [X%] of tasks within +/- 20% of estimate

[Analysis: Are we consistently over- or under-estimating? For which types of
tasks? What adjustment should we apply?]

### Carryover Analysis

| Task | Original Sprint | Times Carried | Reason | Action |
|------|----------------|---------------|--------|--------|
| [Task that was not completed] | [Sprint N-X] | [N] | [Why] | [Complete / Descope / Redesign] |

### Technical Debt Status
- Current TODO count: [N] (previous: [N])
- Current FIXME count: [N] (previous: [N])
- Current HACK count: [N] (previous: [N])
- Trend: [Growing / Stable / Shrinking]
- [Note any areas of concern]

### Previous Action Items Follow-Up

| Action Item (from Sprint N-1) | Status | Notes |
|-------------------------------|--------|-------|
| [Previous action] | [Done / In Progress / Not Started] | [Context] |

### Action Items for Next Iteration

| # | Action | Owner | Priority | Deadline |
|---|--------|-------|----------|----------|
| 1 | [Specific, measurable action] | [Who] | [High/Med/Low] | [When] |
| 2 | [Another action] | [Who] | [Priority] | [When] |

### Process Improvements
- [Specific change to how we work, with expected benefit]
- [Another improvement -- keep it to 2-3 actionable items, not a wish list]

### Summary
[2-3 sentence overall assessment: Was this a good sprint/milestone? What is
the single most important thing to change going forward?]

Phase 5: Save Retrospective

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/retrospectives/retro-sprint-[N]-[date].md?" (or production/retrospectives/retro-[milestone-name]-[date].md for milestone retrospectives)

After Start fresh in Phase 1b, the same ask also names the rename: "…and rename [old file] to [old file name]-archived-[date].md?" On yes, rename first, then write; on no, neither happens.

If yes, write the file, creating the production/retrospectives/ directory if needed. Verdict: COMPLETE — retrospective saved.

If no, stop here. Verdict: BLOCKED — user declined write.

Phase 6: Next Steps

At workflow: minimal (resolved above), which has no sprints, skip this question: point to the retrospective file and say its action items go into the brief's build order.

Otherwise, use AskUserQuestion:

  • Prompt: "Retrospective complete. The action items and velocity data are ready. Would you like to start sprint planning now with this data pre-loaded?"
  • Options:
    • [A] Yes — open sprint planning with retro action items and velocity delta pre-populated
    • [B] No — I'll reference the retrospective file manually when I'm ready

If the user selects [A]: Proceed to invoke /sprint-plan new, passing the retrospective file path and a summary of the action items and velocity change so the sprint planner can reference them.

  • 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.
  • 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.

© Donchitos, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/retrospective of Donchitos/Claude-Code-Game-Studios.

Open the folder on GitHubat commit be8993b

Compare with similar skills

Sprint Retrospective next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sprint Retrospective compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sprint Retrospective this skillDonchitos/Claude-Code-Game-Studios26k—~3.1kAutomated safety check: NotesMIT
Scrum Masteralirezarezvani/claude-skills28k1 repos~2.4kAutomated safety check: PassMIT
Scrum Master Agentalirezarezvani/claude-code-skill-factory880—~3.3kAutomated safety check: PassMIT
Omh Operating Rhythmrlaope/oh-my-hermes3.2k—~1.5kAutomated safety check: PassMIT
Scrum Masterborghei/Claude-Skills886—~2.5kAutomated safety check: PassMIT
Agile Coachborghei/Claude-Skills886—~1.2kAutomated safety check: PassMIT

Similar skills

  • Scrum Master

    alirezarezvani/claude-skills

    Advanced Scrum Master skill for data-driven agile team analysis and coaching.

    28k GitHub starsUsed in 1 repo~2.4k tokens
    Product & Project ManagementAuto-check passed

  • Scrum Master Agent

    alirezarezvani/claude-code-skill-factory

    Comprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting

    880 GitHub stars~3.3k tokensUpdated 11 mo ago
    Product & Project ManagementAuto-check passed

  • Omh Operating Rhythm

    rlaope/oh-my-hermes

    [omh] Team minutes, retros, and decision history to keep: meeting minutes, scrum/sprint records, retros, decisions, and follow-up history.

    3.2k GitHub stars~1.5k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Scrum Master

    borghei/Claude-Skills

    Data-driven Scrum Master for sprint health scoring, Monte Carlo velocity forecasting, retrospective analysis, capacity planning, and Tuckman team coaching.

    886 GitHub stars~2.5k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

  • Agile Coach

    borghei/Claude-Skills

    Expert agile coaching: framework selection, maturity assessment, retrospective facilitation, transformation roadmaps.

    886 GitHub stars~1.2k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

  • Scrum Master

    aAAaqwq/AGI-Super-Team

    Advanced Scrum Master with data-driven team health analysis, velocity forecasting, retrospective insights, and team development expertise.

    105 GitHub starsUsed in 1 repo~5.7k tokens
    Product & Project ManagementAuto-check passed

More from Donchitos/Claude-Code-Game-Studios

All 73 skills in this repo

  • Architecture Decision

    Donchitos/Claude-Code-Game-Studios

    Create an ADR documenting a technical decision: context, alternatives considered, consequences.

    26k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

  • Dev Story

    Donchitos/Claude-Code-Game-Studios

    Implement a story: ADR guidelines, right programmer agent, code plus test.

    26k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check: notes

  • Game Asset Audit

    Donchitos/Claude-Code-Game-Studios

    Audits game assets against naming conventions, file size budgets and format standards, and finds orphaned assets and missing references.

    26k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Game Asset Spec Writer

    Donchitos/Claude-Code-Game-Studios

    Writes per-asset visual specs and AI image-generation prompts for a game's characters, enemies and screens, driven by the GDD, art bible and an entity inventory.

    26k GitHub stars~5k tokensUpdated yesterday
    Auto-check passed

  • Game Balance Check

    Donchitos/Claude-Code-Game-Studios

    Checks game data and formulas for balance outliers, broken progression, degenerate strategies and economy problems, and answers 'could not run' when the data is missing.

    26k GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

  • Structured Bug Reports

    Donchitos/Claude-Code-Game-Studios

    Turns a description into a structured bug report, or scans code for likely bugs, then verifies and closes reports through four modes.

    26k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check: notes

Categories

Questions about Sprint Retrospective

What does Sprint Retrospective do?

Builds a sprint or milestone retrospective from completed work, velocity and blockers, checking first for an existing retrospective file. You name a sprint (as `sprint-N`) or a milestone, and the skill produces a retrospective from the work that was completed, the velocity and the blockers, ending in actionable points for the next iteration. Before loading any data it looks for an existing retrospective under `production/retrospectives/`, or in the sprint folder for sprints, and asks what to do if it finds one.

When should I use Sprint Retrospective?

Sprint Retrospective fits situations like: closing a sprint with a written look at what went well and what blocked the team; reviewing a whole milestone for lessons to carry into the next one; avoiding a duplicate retrospective when one already exists for the sprint.

How do I install Sprint Retrospective in Claude Code?

Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill retrospective -a claude-code`. Or copy the skill folder (.claude/skills/retrospective in Donchitos/Claude-Code-Game-Studios) into .claude/skills/retrospective in your project. Claude Code loads it when a task matches its description.

How do I install Sprint Retrospective in Codex?

Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill retrospective -a codex`. Or copy the skill folder (.claude/skills/retrospective in Donchitos/Claude-Code-Game-Studios) into .agents/skills/retrospective in your project. Codex loads it when a task matches its description.

Can I use Sprint Retrospective in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Donchitos/Claude-Code-Game-Studios --skill retrospective -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/retrospective, .gemini/skills/retrospective, .github/skills/retrospective and .opencode/skills/retrospective in your project.

What does Sprint Retrospective need to run?

Going by SKILL.md and its folder, Sprint Retrospective needs the command-line tools its instructions call (git and bash). Our summary lists: Sprint and story records under `production/`. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Bash, AskUserQuestion, Bash(bash "*/.claude/skills/retrospective/../../hooks/yaml-helper.sh" resolve_config *).

Does Sprint Retrospective access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Sprint Retrospective safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Sprint Retrospective use?

Sprint Retrospective is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sprint Retrospective use?

About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Sprint Retrospective?

Skills that share tags, products or a category with Sprint Retrospective: Scrum Master (alirezarezvani/claude-skills, 28k stars), Scrum Master Agent (alirezarezvani/claude-code-skill-factory, 880 stars), Omh Operating Rhythm (rlaope/oh-my-hermes, 3.2k stars) and Scrum Master (borghei/Claude-Skills, 886 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sprint Retrospective?

Donchitos (a GitHub user) maintains it in Donchitos/Claude-Code-Game-Studios, which has 25,951 GitHub stars. The repository holds 73 skills in this directory. The repository was last updated on October 8, 2026.

Source: Donchitos/Claude-Code-Game-Studios on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.