Retro Points

Turn a discussion into retrospective points for a team's daily retro. Called on the current conversation, a pasted thread, a file, or a ticket or PR, it finds what slowed the team down, traces each item from event to pattern to the structure and belief behind it, names the system archetype, runs the systems-thinking iceberg on recurring points, proposes one structural experiment per pattern, scores it for impact, and recommends what the retro should open with. Built on Kerth's Prime Directive, Derby & Larsen's phases, Toyota Kata's daily improvement cycle, a multi-branch 5 Whys repaired with A

5 stars 2 forksGit & Code Review Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add vnovakovits/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add vnovakovits/claude-skills --skill retro-points
Manual install
git clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/retro-points ~/.claude/skills/retro-points

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Retro Points

## When invoked

**Input.** Use what follows the command:
- nothing: the current conversation, from its start;
- pasted text: that discussion (a Slack thread, meeting notes, an incident timeline);
- a file path: read it;
- a ticket or PR link: read it and its comments, using the connected tools.

Read the whole discussion before writing. Gather evidence: ticket and PR numbers, commits, timestamps, error names, quoted decisions.

**Output, in this order:**

1. **Retro points table**, at most eight rows, highest score first:

   | # | What happened | The pattern underneath | Structure or archetype | Candidate experiment | Score |
   |---|---|---|---|---|---|

   - *What happened:* concrete events with a pointer (ticket, PR, time). Several events per row when they share a pattern.
   - *Pattern:* what keeps happening, in one sentence.
   - *Structure or archetype:* the rule, pipeline, ownership or information gap that produces it, the archetype in bold, and the belief that keeps it in place when the discussion shows one.
   - *Candidate experiment:* one structural change, phrased so it can be tested.
   - *Score:* the impact scorecard total, out of 16.
2. **Suggested order:** which point the retro should open with and why (highest score on the binding flow), the cheapest high scorer next, and which points need another team, so they go to the weekly review.
Read the full skill on GitHub

Details

Skill name
retro-points
Path
plugins/engineering-practices/skills/retro-points/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Retro Points skill do?

Turn a discussion into retrospective points for a team's daily retro. Called on the current conversation, a pasted thread, a file, or a ticket or PR, it finds what slowed the team down, traces each item from event to pattern to the structure and belief behind it, names the system archetype, runs the systems-thinking iceberg on recurring points, proposes one structural experiment per pattern, scores it for impact, and recommends what the retro should open with. Built on Kerth's Prime Directive, Derby & Larsen's phases, Toyota Kata's daily improvement cycle, a multi-branch 5 Whys repaired with A

How do I install the Retro Points skill?

Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Retro Points popular?

It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Accidental Cio

5

vnovakovits/claude-skills

Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to

Frontend & Design

Agent Retro

5

vnovakovits/claude-skills

Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee

AI, LLMs & Agents

API Design

5

vnovakovits/claude-skills

Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.

Software Development

Sharing Skills

8

Freddy-CHEN-ux/00_claude_skills

Use when contributing skills back to the community. Follow git workflow: sync upstream → create branch → develop skill → test with writing-skills → commit → push → PR. One skill per PR.

Git & Code Review

Requesting Code Review

8

Freddy-CHEN-ux/00_claude_skills

Use when completing tasks or major features. Know when and how to request reviews. Provides git commit range to code-reviewer agent.

Git & Code Review

Edu Lesson Plan

5

eshmith7/claude-skills-library

Plan a lesson backwards from the check, with misconceptions named, whole-class checks that each carry a branch, and what to cut decided in advance. Use for lesson or unit plans.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.