skill CX Codex

sprint-retrospective — Claude Code skill: run sprint retros

Q: How do I install sprint-retrospective in Claude?

Run `npx skills add akillness/jeo-skills --skill sprint-retrospective -a claude-code`. The skill lands at `~/.claude/skills/sprint-retrospective/SKILL.md`.

Q: What does this skill not cover?

Backlog planning routes to `task-planning`, sizing to `task-estimation`, daily coordination to `standup-meeting`, and incident analysis to dedicated skills.

Runs a sprint or milestone retrospective and turns it into a few owned actions instead of another template ritual.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓

npx skills add akillness/jeo-skills --skill sprint-retrospective -a claude-code

Open on GitHub

What sprint-retrospective does

The skill walks a retrospective from intake to brief. It first classifies the request: cadence (sprint, release, milestone, project phase), team shape, current pain, and what evidence is on hand. Then it picks exactly one primary mode — live-facilitated-retro, async-first-retro, hybrid-retro, milestone-postmortem, or action-review-reset. It will not blend modes in one answer.

Next comes a review of prior actions: done, stale, blocked, or worth dropping. Observations are collected through one prompt family — start / stop / continue, 4Ls, mad / sad / glad, or custom prompts tied to quality and handoffs. Themes get merged down to three to five, and actions are capped at three, each with an owner, a due date, and a success signal.

When a team keeps generating actions and closing none, the skill switches to action-review-reset. Backlog planning goes to task-planning, sizing to task-estimation, daily sync to standup-meeting, and incident forensics to dedicated skills. That last handoff matters: a retro is not the place for a deep outage investigation.

What it helps with

run a retrospective after a finished sprint
pick a retro format instead of reusing a stale template
sort prior actions into done, stale, blocked and dropped
collect team observations without turning it into blame
turn recurring complaints into a couple of process experiments

Example prompts for the agent

Run a sprint retrospective for a distributed team and give me themes plus owned actions
Our old retro actions never closed — do an action-review-reset and tell me what to keep or drop
I need a milestone postmortem for the release: what broke in the workflow and what we change next

How to install sprint-retrospective

1Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill sprint-retrospective -a claude-code

2Manually: put the files in place

~/.claude/skills/sprint-retrospective/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/sprint-retrospective/

1Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill sprint-retrospective -a codex

2Manually: put the files in place

.agents/skills/sprint-retrospective/SKILL.md

For all projects use ~/.agents/skills/

1Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill sprint-retrospective -a cursor

2Manually: put the files in place

.cursor/skills/sprint-retrospective/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

1GitHub CLI

gh skill install akillness/jeo-skills sprint-retrospective

2Manually: put the files in place

.github/skills/sprint-retrospective/SKILL.md

1Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill sprint-retrospective -a gemini-cli

2Platform CLI

gemini skills install https://github.com/akillness/jeo-skills --path .agent-skills/sprint-retrospective

Manually: put the files in place

.devin/skills/sprint-retrospective/SKILL.md

The legacy .windsurf/skills/ path still works

Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill sprint-retrospective -a opencode

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about sprint-retrospective

How do I install sprint-retrospective in Claude?

Run npx skills add akillness/jeo-skills --skill sprint-retrospective -a claude-code. The skill lands at ~/.claude/skills/sprint-retrospective/SKILL.md.

What does sprint-retrospective do?

It facilitates a sprint, release, or milestone retrospective: picks a facilitation mode, reviews previous actions, clusters themes, and leaves a few actions with owners and due dates.

What does this skill not cover?

Backlog planning routes to task-planning, sizing to task-estimation, daily coordination to standup-meeting, and incident analysis to dedicated skills.

iterate-retrospective product-on-purpose Facilitates and documents team retrospectives after sprints or milestones, capturing what worked, what failed, and who owns each follow-up action. CX Codex +1 741installs retrospective Donchitos Generates sprint and milestone retrospectives from task plans, git commits, and blockers. Helps capture action items for upcoming iterations. CX Codex +1 433installs sprint-status Donchitos Reads the sprint plan and story files, then reports what is done and what is left. Useful when you need a fast read on how the sprint is going. CX Codex +1 411installs retro phuryn Facilitates structured sprint retrospectives, analyzes team performance, and turns feedback into prioritized action items with assigned owners and deadlines. CX Codex +1 2,700installs Jira Automation Claude Office Skills Automates Jira issue tracking and sprint planning. Helps configure transition workflows and calculate team capacity through chat. CX Codex +1 4,700installs agile-sprint-planning aj-geddes Helps teams organize sprints by setting clear sprint goals, estimating story points, managing backlogs against team velocity, and running standups. CX Codex +1 669installs

From the same set22

plannotator The skill opens a browser approval loop: a human reads a plan, diff or spec and leaves notes before any code gets written. CX Codex +1 379installs marketing-automation The skill turns a vague marketing request into one operating mode, one discipline and one operator packet with an owner and proof. CX Codex +1 377installs monitoring-observability Turns service, data-pipeline, or live-ops context into a monitoring brief with a primary mode, useful signals, and a small first implementation slice. CX Codex +1 369installs authentication-setup Walks you through choosing an auth lane for a web app or API and drawing the line between what the provider owns and what stays in your app. CX Codex +1 368installs state-management A skill that classifies React state into packets and picks the narrowest owner, so you stop arguing about libraries before you know what the state is. CX Codex +1 365installs debugging A skill that walks the agent through a reproduce → isolate → verify loop for concrete bugs, regressions and flaky failures. Useful once you already have a failing test or request. CX Codex +1 361installs system-environment-setup A skill that makes a repo runnable on any machine: pinned runtimes, local services, containers, bootstrap scripts and setup diagnosis. CX Codex +1 351installs bmad Reads your current project state and names the next BMAD artifact or gate. Useful when you are stuck after idea notes, a PRD or an architecture draft. CX Codex +1 334installs