project-retrospective
Analyze a project's session history by dispatching parallel historian agents to read each export, then synthesizing their findings into a structured analysis document. The value is in the extraction criteria — domain-specific signals tuned for Claude Code session exports, not generic summarization.
npx skills add majiayu000/claude-skill-registry --skill project-retrospective-belumume-claude-skills --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
--- name: project-retrospective description: Use when a project needs multi-session retrospective analysis — after milestones, before starting a new phase, when vision drift is suspected, or every 3-5 sessions. Triggers: user says "retro", "run a retro", "since-last-retro"; asks to analyze patterns, recurring mistakes, or correction trends across multiple sessions; says "how did we get here" or "project history" in a project-arc context (not single-file diffs or README edits); or notes that MEMORY.md has drifted from what actually happened across sessions. NOT for: single-session review, MEMORY.md cleanup, retro templates, or git-level file diffs. argument-hint: [full | since-last-retro | last-N] --- # Project Retrospective Analyze a project's session history by dispatching parallel historian agents to read each export, then synthesizing their findings into a structured analysis document. The value is in the **extraction criteria** — domain-specific signals tuned for Claude Code session exports, not generic summarization. ## Modes Two modes, differentiated by **output format** (not historian cost): | Mode | Output | When to Use | |------|--------|-------------| | **full** | Standal
- Modes
- Arguments
- Phase 1: Discover & Validate Exports
- Phase 1.5: Detect Prior Retro
- Phase 2: Spawn Historians (Parallel Background Agents)
- Historian Extraction Template
- Phase 3: Synthesize
- Full Synthesis Template
- Incremental Synthesis Template
- Phase 4: Write & Integrate
- Write the analysis
- Update MEMORY.md
- Commit
- Deletion Semantics
What does the project-retrospective skill do?
Analyze a project's session history by dispatching parallel historian agents to read each export, then synthesizing their findings into a structured analysis document. The value is in the extraction criteria — domain-specific signals tuned for Claude Code session exports, not generic summarization.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill project-retrospective-belumume-claude-skills --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.