retrospective
Skill9 starsChanged 3 months agoMITView on GitHub
Sprint retrospective — consumes progress.md Metrics table, adds leading-lagging analysis, anti-pattern detection, and 4Ls framework.
73 other projects use a version of this.
Adopted by
Most recently taken up by
- tatashbar/Economic-Modeling-Studiotheir own version, first seen Nov 16, 2026
- andymai/claude-agent-teamtheir own version, first seen Nov 16, 2026
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- teodstr/workbenchtheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- andymai/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use dev-story, team-level and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
lilangMaxSkilldev-story
Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before /code-review and /story-done.
Also in 12 projects that use this
CoralGameSkillteam-level
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Also in 12 projects that use this
CoralGameSkillteam-narrative
Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.
Also in 12 projects that use this
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 11 projects that use this
- +7 more from lilangMax
- +1 more from CoralGame
Other versions73 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 73
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- alibaba/MNN★ 17ksame name
- glebis/claude-skills★ 414same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 124same name
- PAIR-code/deliberate-lab★ 102same name
- The01Geek/prflow★ 100same name
- AsiaOstrich/universal-dev-standards★ 84same name
- tranhieutt/software_development_department★ 71same name
- cenconq25/claude-code-app-studio★ 40same name
63 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository56 other files it gives its agents.
- .claude/agents/CLAUDE.mdCLAUDE.md
- .claude/hooks/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .claude/prompts/CLAUDE.mdCLAUDE.md
- .claude/rules/CLAUDE.mdCLAUDE.md
- .claude/skills/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- vision/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- scaffold/llms.txtllms.txt
- architecture-checkSkill
- backlog-reviewSkill
- bootstrapSkill
- brainstormSkill
- buildSkill
- claude-sense-checkSkill
- code-qualitySkill
- commitSkill
- continueSkill
- custom-hooksSkill
- dashboardSkill
- debug-sessionSkill
- deploySkill
- discoverSkill
- doctorSkill
- fix-issueSkill
- framework-upgradeSkill
- handoffSkill
- help-meSkill
- ideateSkill
- lanesSkill
- manual-testSkill
- merge-downSkill
- merge-upSkill
- optimizeSkill
- parallel-workSkill
- performance-checkSkill
- phase-reviewSkill
- pr-statusSkill
- quality-checkSkill
- quickstartSkill
- refine-loopSkill
- researchSkill
- security-auditSkill
- skill-createSkill
- skill-evalSkill
- sprint-endSkill
- sprint-startSkill
- story-cycleSkill
- testing-cycleSkill
- test-validatorSkill
- UAT-cycleSkill
- undo-workSkill
- uninstallSkill
- weekly-maintenanceSkill
- wrap-upSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
25 rules. 0 are common, 15 are distinctive, and 10 are very specific to this project.
0
Common
Most of the 62 edited versions we read keep these.
15
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Run a sprint or weekly retrospective:
- Distinctive: line 20
Read sprint specs and progress to build a complete picture:
- Very specific: line 22
Read docs/progress.md → ## Sprint History table for trend data
- Very specific: line 23
Read the sprint spec(s) being reviewed: docs/sprints/sprint-N.md — especially the ## Outcome and ## Decisions sections
- Very specific: line 31
Read docs/progress.md → ## Metrics table and display it directly — sprint-end already computed these values.
- Very specific: line 41
Read docs/progress.md → ## Sprint History table.
- Very specific: line 60
Read references/metrics-analysis.md for the leading/lagging classification.
- Very specific: line 70
Read references/metrics-analysis.md for the four anti-pattern definitions.
- Distinctive: line 91
If feature stories are <50% of total, flag: "Less than half of sprint work on features — investigate maintenance burden." </IF>
- Very specific: line 97
Run scripts/pm/metrics.sh --churn and display the high-churn files.
- Distinctive: line 102
Run the metrics script for framework-specific data not captured in progress.md:
- Very specific: line 113
Read sprint spec ## Outcome → Ground rules field across recent sprints:
- Very specific: line 122
Read docs/technical-debt.md and recent sprint spec(s) ## Outcome → Debt delta fields:
- Distinctive: line 144
Use the 4Ls format:
- Distinctive: line 148
Consider: smooth processes, good decisions, effective patterns
- Distinctive: line 152
Consider: technical discoveries, process improvements, gotchas found
- Distinctive: line 156
Consider: tools, information, clarity, time
- Distinctive: line 160
Consider: automation, better docs, different approach
- Distinctive: line 169
Should the goal format change for next sprint?
- Distinctive: line 174
Should the session capacity estimate change for next sprint?
- Very specific: line 204
Rule updates needed: Should any patterns be added to CLAUDE.md, GROUND_RULES.md, or .claude/rules/ based on this sprint's experience?
- Distinctive: line 219
If patterns or gotchas were discovered:
- Distinctive: line 221
Add to CLAUDE.md for future sessions
- Distinctive: line 222
Update any incorrect conventions
- Distinctive: line 223
Add new commands if needed
“Common” is measured: kept by at least 6 in 10 of the 62 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
retrospective
Run a sprint or weekly retrospective:
1. Gather Data
Read sprint specs and progress to build a complete picture:
- Read
docs/progress.md→## Sprint Historytable for trend data - Read the sprint spec(s) being reviewed:
docs/sprints/sprint-N.md— especially the## Outcomeand## Decisionssections - Git log for commits and their messages
- Any blockers or issues encountered (from sprint spec
## Notesand## Decisions)
2. Metrics Dashboard
2.1. Progress Metrics (single source of truth)
Read docs/progress.md → ## Metrics table and display it directly — sprint-end already computed these values.
| Metric | Current | Target | Trend | Status |
| [Copy all rows from progress.md Metrics table] |
Sprint note: [Copy from progress.md if present]
2.2. Sprint-over-Sprint Comparison
Read docs/progress.md → ## Sprint History table. Extract the last 2 rows (current and previous sprint):
| Metric | This Sprint | Previous | Δ | Direction |
| Goal achieved | [✅/❌] | [✅/❌] | — | [streak] |
| Tasks completed | [X] | [Y] | [+/-] | [↑/↓/→] |
| Cycle time | [X.Xd] | [Y.Yd] | [+/-] | [↑/↓/→] |
| Change failure rate | [X%] | [Y%] | [+/-] | [↑/↓/→] |
| Test coverage Δ | [+X%] | [+Y%] | [+/-] | [↑/↓/→] |
| Code churn ratio | [0.XX] | [0.YY] | [+/-] | [↑/↓/→] |
| AI effectiveness | [0.XX] | [0.YY] | [+/-] | [↑/↓/→] |
| Sprint satisfaction | [X/5] | [Y/5] | [+/-] | [↑/↓/→] |
Also extract from sprint spec (docs/sprints/sprint-N.md → ## Outcome):
- Sprint churn: % stories added/removed mid-sprint (target <20%, >40% = broken planning)
- Done-to-commit ratio: completed/planned (80% healthy, >95% = under-committing, <65% = over-committing)
2.3. Leading vs Lagging Analysis
Read references/metrics-analysis.md for the leading/lagging classification.
From the Sprint History's last 3 rows, assess the trend direction for each group:
- Leading indicators (churn, coverage Δ, satisfaction): [improving / stable / degrading]
- Lagging indicators (CFR, tasks): [improving / stable / degrading]
Flag any divergence — see the reference file for interpretation guidance. This is the most actionable analysis: leading indicators predict what lagging will show in 1-2 sprints.
2.4. Anti-pattern Detection
Read references/metrics-analysis.md for the four anti-pattern definitions. Check each against Sprint History data:
- Perception gap: satisfaction ≥4 AND (CFR or churn rising 2+ sprints)?
- Task fragmentation: tasks rising AND cycle time shrinking 2+ sprints?
- Weak tests: coverage Δ positive AND CFR rising 2+ sprints?
- Maintenance spiral: <50% feature stories AND churn rising?
Flag any detected patterns with specific metric evidence.
2.5. Feature Time Ratio
<IF condition="docs/sessions/.activity-log.jsonl exists">
Parse `docs/sessions/.activity-log.jsonl` for story `status-change` events with `story_type` field. Count completed stories by type:| Type | Count | % |
| feature | [X] | [X%] |
| bugfix | [Y] | [Y%] |
| refactor | [Z] | [Z%] |
| other | [W] | [W%] |
If feature stories are <50% of total, flag: "Less than half of sprint work on features — investigate maintenance burden."
</IF>
2.6. Hotspot Investigation (conditional)
<IF condition="Code churn ratio in Metrics table is 🟡 or 🔴">
Run `scripts/pm/metrics.sh --churn` and display the high-churn files. Cross-reference with sprint stories — are these files being actively developed, or are they unrelated files being destabilized?
</IF>2.7. Framework Metrics
Run the metrics script for framework-specific data not captured in progress.md:
bash scripts/pm/metrics.shReports: skill success/failure rates, per-skill breakdown, tool usage, rule triggers. Identify: bottleneck skills (high failure), rework patterns (high Bash ratio), underutilized gates.
<IF condition="docs/reference/GROUND_RULES.md exists">
### 2.8. Ground Rule ComplianceRead sprint spec ## Outcome → Ground rules field across recent sprints:
- Violation trend — increasing violations signals architectural drift
- Repeat violations — same rule violated multiple sprints: rule may be unrealistic or enforcement insufficient
- Coverage gaps — rules never checked suggest enforcement isn't working
</IF>
<IF condition="docs/technical-debt.md exists and has active or resolved items">
### 2.9. Technical Debt HealthRead docs/technical-debt.md and recent sprint spec(s) ## Outcome → Debt delta fields:
- Active inventory: [N] total — [N] critical / [N] high / [N] medium / [N] low
- AI-origin ratio: [N] of [total] active items ([X%]) have
origin: ai-generated - Growth trend: Sum debt deltas from sprint outcomes in the review period. Net debt growing, stable, or shrinking?
- Resolution velocity: Items resolved since last retro. Average time from
Sincedate toResolveddate. - Stale items: Any active items older than 90 days with no linked story? Flag as neglected.
- Interest escalation: Any items whose interest changed from Stable → Growing since last review? These are compounding.
- Estimate accuracy: For resolved items, compare
Effort actualvsEffortestimate. Systematic bias?
<IF condition="Section 2.6 (Hotspot Investigation) produced results">
Cross-reference high-churn files from 2.6 with debt item Locations. Overlap means debt in actively changing code — it's compounding through every edit.
</IF>Flag actionable patterns:
- Net debt growing 2+ sprints → "Debt accumulating faster than resolution — increase debt allocation in next sprint"
- AI-origin >50% → "AI is primary debt source — review quality gates, coding standards enforcement, and AI-specific review depth"
- Stale items >3 → "Debt register going stale — items not converting to sprint stories. Check sprint-start debt health check."
</IF>
3. Retrospective Framework
Use the 4Ls format:
Liked (What went well?)
- Consider: smooth processes, good decisions, effective patterns
Learned (What did we discover?)
- Consider: technical discoveries, process improvements, gotchas found
Lacked (What was missing?)
- Consider: tools, information, clarity, time
Longed For (What do we wish we had?)
- Consider: automation, better docs, different approach
4. AI-Assisted Sprint Reflection
Sprint-goal-anchored questions (answer each with evidence, not impressions):
Sprint Goal Effectiveness
- Did the sprint goal help scope decisions during story execution? Was it specific enough for AI to use as decision context?
- Were there moments where the sprint goal was ignored or forgotten? What caused that?
- Should the goal format change for next sprint? (e.g., too vague, too compound, too narrow)
Session & Capacity Accuracy
- How many sessions were actually used vs estimated? Were S/M/L sizes accurate?
- Which stories took more sessions than sized? Why? (complexity surprise, external dependency, scope change)
- Should the session capacity estimate change for next sprint?
AI Execution Quality
- Where did AI-generated code create review bottleneck? (time spent reviewing vs writing)
- Were any tests weakened or deleted? Were quality gates effective at catching this?
- Context management: Did we hit limits? Was the plan-then-execute pattern followed?
- TDD discipline: Was test-first maintained, or did time pressure cause shortcuts?
Carry-Over & Churn Analysis
- Were carried-over stories goal-critical or non-critical? (Non-critical carry-over = correct prioritization)
- What was the sprint churn rate? If >20%, what caused mid-sprint additions?
- Were any stories added mid-sprint that should have waited for backlog?
4.5. Architecture Decision Audit
Review whether architectural decisions made during this sprint are properly documented:
- Scan commit messages and story plans for technology choices, pattern decisions, or trade-off discussions that aren't captured in
docs/adr/ - Check for "decisions in chat" — if the team discussed architectural choices during the sprint but didn't create ADRs, flag specific candidates (e.g., "Chose Redis over Memcached for caching — warrants an ADR")
- Ground rule candidates — if a pattern was enforced informally during the sprint ("we always do X"), suggest formalizing it as a ground rule backed by an ADR
This prevents the "decisions in Slack" anti-pattern where architectural choices are made but never formalized.
4.6. AI Learnings
Review how AI tools performed during this sprint — what worked, what didn't, and what to update:
- Effective patterns: Which prompting strategies, decomposition approaches, or AI workflows produced good results? Document for future sessions and teammates.
- Anti-patterns observed: Did AI-generated code introduce specific defect types this sprint? (Check: phantom packages, code duplication, abstraction bypass, tautological tests, over-engineering — see
docs/reference/TEAM_WORKFLOW.md→ AI-Specific Review Checklist) - Comprehension check: Can every developer explain the AI-generated code they merged? If not, flag specific areas for code walkthroughs. (59% of developers ship AI code they don't fully understand — this is how comprehension debt accumulates.)
- Rule updates needed: Should any patterns be added to CLAUDE.md, GROUND_RULES.md, or
.claude/rules/based on this sprint's experience? - Review effectiveness: Did the review layers (pre-commit → CI → AI review → human review) catch issues? Where did defects slip through?
Capture findings in the retrospective summary. Update CLAUDE.md with any new rules or anti-patterns discovered.
5. Action Items
Convert insights into specific actions:
| Item | Type | Priority | Owner | Due |
| [Action] | Process/Tool/Doc | High/Med/Low | Self | [Date] |
6. Update CLAUDE.md
If patterns or gotchas were discovered:
- Add to CLAUDE.md for future sessions
- Update any incorrect conventions
- Add new commands if needed
7. Retrospective Summary
## Retrospective - [Date]
### Period Covered
[Sprint X / Week of Y]
### Metrics Summary
[Copy the Metrics table from docs/progress.md — single source of truth]
### Key Signals
- Leading indicators: [improving/stable/degrading]
- Lagging indicators: [improving/stable/degrading]
- Anti-patterns detected: [list or "none"]
- Feature time ratio: [X]%
### Top 3 Positives
1. [Most impactful positive]
2.
3.
### Top 3 Improvements Needed
1. [Most important improvement]
2.
3.
### Action Items
[List from above]
### Process Adjustments
[Any changes to workflow]Output the retrospective summary with action items.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

