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

Retrospective Evidence

by oocx in oocx/tfplan2md

Where to find objective evidence about a completed cycle - work protocol, workflow state, git history and CI.

MITAuto-check passedProduct & Project Management

Install Retrospective Evidence

skills CLI
$ npx skills add oocx/tfplan2md --skill retrospective-evidence -a claude-code

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

GitHub CLI
$ gh skill install oocx/tfplan2md retrospective-evidence --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/oocx/tfplan2md.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/retrospective-evidence .claude/skills/retrospective-evidence && 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-evidence
GitHub stars
174
Token cost
~756 tokens
SKILL.md length
404 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

Where to find objective evidence about a completed cycle - work protocol, workflow state, git history and CI.

  • Works in 3 steps: The evidence — which of the above, quoted. → The change location — the file that… → The verification — how you would know it…
  • Tasks that involve Retrospectives
  • SKILL.md covers The highest-signal source is…, The work protocol, Git history and CI, plus 2 more sections
  • Calls git and jq

What it does

Retrospective Evidence is an agent skill from oocx/tfplan2md. Where to find objective evidence about a completed cycle - work protocol, workflow state, git history and CI.

Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering Retrospectives and Git workflow. The repository describes itself as: Convert terraform plans (json) into human readable markdown for easier review of changes in pull requests. The licence is MIT.

When your agent uses it

  • Tasks that involve Retrospectives
  • Tasks that involve Git workflow

Example prompts

  • “/retrospective-evidence”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. The evidence — which of the above, quoted.
  2. The change location — the file that would change.
  3. The verification — how you would know it worked.

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • jq

    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

Retrospective Evidence loads about 756 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 404 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
~756

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 passed

The automated check found no risky patterns in SKILL.md.

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 oocx/tfplan2md at commit aa2fa28, republished under its MIT licence (© oocx). 404 words, ~756 tokens.

Download SKILL.mdSave it as .claude/skills/retrospective-evidence/SKILL.md (or your agent's skills folder).
name
retrospective-evidence
description
Where to find objective evidence about a completed cycle - work protocol, workflow state, git history and CI.

Retrospective Evidence

A retrospective is only as good as what it can point at. This is where the objective record lives.

The highest-signal source is state.json

bash
jq '{attempts, open_questions, gates}' docs/<type>/NNN-<slug>/state.json
  • attempts — a stage that ran three times is a workflow defect, not bad luck. Look at why it repeated: an unclear specification usually shows up as repeated Developer rework, not as a Requirements Engineer problem.
  • open_questions — a question nobody answered means a role proceeded on an assumption. If the assumption turned out wrong, that is a finding about the gate design, not about the role.
  • gates — a gate that was never contested when it should have been, or one that fired on something trivial, is a rule worth adjusting.

The work protocol

work-protocol.md carries each role's own account, including the Problems Encountered field. Read those first: they are the closest thing to a first-hand incident report, and a problem that was logged and then ignored is a worse finding than the problem itself.

Git history

Start with the retained work item's Release Manager entry to identify the merged PR and published release. Use the merged PR's recorded base and head commits to inspect the delivery commit range, and corroborate it with the release and CI history:

bash
git log --oneline <pr-base>..<pr-head>          # how often delivery work was redone
git log --format='%s' <pr-base>..<pr-head> | cut -d: -f1 | sort | uniq -c

Repeated commits touching the same file, or a string of fix: commits after a feat:, tell you where the work actually went.

Do not use origin/main..HEAD for a post-release documentation follow-up. At that point the delivery commits are already on main, so that range contains only the follow-up branch and can hide the cycle being reviewed. If the Release Manager entry, merged PR, release, or CI record does not establish a fact, say the evidence is unavailable rather than reconstructing it from memory.

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

CI

bash
scripts/check-workflow-status.sh list

What failed, and how late it failed. A failure caught in PR Validation that a role could have caught locally is an argument for moving the check earlier.

What this skill replaced

Retrospectives used to be driven by VS Code chat exports, parsed by scripts/analyze-chat.py. Those exports do not exist outside VS Code, and the metrics they produced (model usage, tool invocation counts, approval friction) measured the harness rather than the workflow. The sources above measure the work.

Writing the finding

Every improvement opportunity needs three things or it is a wish:

  1. The evidence — which of the above, quoted.
  2. The change location — the file that would change.
  3. The verification — how you would know it worked.

© oocx, 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 .agents/skills/retrospective-evidence of oocx/tfplan2md.

Open the folder on GitHubat commit aa2fa28

Compare with similar skills

Retrospective Evidence 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.

Retrospective Evidence compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Retrospective Evidence this skilloocx/tfplan2md174—~756Automated safety check: PassMIT
Dough Story Wrap Upterryyin/lizard2.5k—~4.3kAutomated safety check: PassCustom licence
Retrokoolamusic/claudefiles130—~2.8kAutomated safety check: PassMIT
RetrospectiveApocrathia/home-assistant-config179—~1.9kAutomated safety check: PassNone
Agile Workflowjwynia/agent-skills170—~3.5kAutomated safety check: PassMIT
Retrospectingbitwarden/ai-plugins155—~4kAutomated safety check: PassCustom licence

Similar skills

  • Dough Story Wrap Up

    terryyin/lizard

    Closes one completed feature story, bounded retrospective correction, or context-only planless execution using available execution context.

    2.5k GitHub stars~4.3k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Retro

    koolamusic/claudefiles

    A skill your agent uses when a user completes a phase, sprint, milestone, or meaningful unit of work and needs a retrospective.

    130 GitHub stars~2.8k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Retrospective

    Apocrathia/home-assistant-config

    Structured post-work retrospective for Home Assistant Homelab: review outcomes, mine git history for context drift, classify lessons, and route improvements — HA-local vs contribute back to…

    179 GitHub stars~1.9k tokensUpdated 19 days ago
    Product & Project ManagementAuto-check passed

  • Agile Workflow

    jwynia/agent-skills

    Orchestrate agile development workflows by invoking commands in sequence with checkpoint-based flow control.

    170 GitHub stars~3.5k tokensUpdated 7 mo ago
    Product & Project ManagementAuto-check passed

  • Retrospecting

    bitwarden/ai-plugins

    Official

    Performs comprehensive analysis of Claude Code sessions, examining git history, conversation logs, code changes, and gathering user feedback to generate actionable retrospective reports with…

    155 GitHub stars~4k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Change Traceability Review

    QoderAI/better-harness

    A skill your agent uses for change traceability review across specs, commits, PRs, branches, local diffs, and git history, including Spec Preparation, Review Readiness Checks, and Review…

    2.4k GitHub stars~559 tokensUpdated 3 days ago
    DevelopmentAuto-check passed

More from oocx/tfplan2md

All 28 skills in this repo

  • Create Agent Skill

    oocx/tfplan2md

    Create a new Agent Skill following project standards and templates.

    174 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

  • Detect Diagram Crossings

    oocx/tfplan2md

    Detect and analyze edge crossings and overlaps in SVG workflow diagrams using geometric intersection algorithms and visual analysis.

    174 GitHub stars~4.3k tokensUpdated yesterday
    Auto-check passed

  • Generate Release Screenshots

    oocx/tfplan2md

    Generate PNG screenshots for release notes using the repository's HtmlRenderer and ScreenshotGenerator tools.

    174 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed

  • Git Rebase Main

    oocx/tfplan2md

    Safely rebase the current feature branch on top of the latest origin/main.

    174 GitHub stars~456 tokensUpdated yesterday
    Auto-check passed

  • Next Issue Number

    oocx/tfplan2md

    Determine the next available issue number across all change types (feature, fix, workflow, website) by checking both local docs and remote branches, then reserve it by pushing an empty branch.

    174 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

  • Run Uat

    oocx/tfplan2md

    Run User Acceptance Testing by creating a PR with rendered markdown on GitHub or Azure DevOps.

    174 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Retrospective Evidence

What does Retrospective Evidence do?

Where to find objective evidence about a completed cycle - work protocol, workflow state, git history and CI. Retrospective Evidence is an agent skill from oocx/tfplan2md. Where to find objective evidence about a completed cycle - work protocol, workflow state, git history and CI.

When should I use Retrospective Evidence?

Retrospective Evidence fits situations like: tasks that involve Retrospectives; tasks that involve Git workflow.

How do I install Retrospective Evidence in Claude Code?

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

How do I install Retrospective Evidence in Codex?

Run `npx skills add oocx/tfplan2md --skill retrospective-evidence -a codex`. Or copy the skill folder (.agents/skills/retrospective-evidence in oocx/tfplan2md) into .agents/skills/retrospective-evidence in your project. Codex loads it when a task matches its description.

Can I use Retrospective Evidence 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 oocx/tfplan2md --skill retrospective-evidence -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-evidence, .gemini/skills/retrospective-evidence, .github/skills/retrospective-evidence and .opencode/skills/retrospective-evidence in your project.

What does Retrospective Evidence need to run?

Going by SKILL.md and its folder, Retrospective Evidence needs the command-line tools its instructions call (git and jq).

Does Retrospective Evidence 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 Retrospective Evidence safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Retrospective Evidence use?

Retrospective Evidence 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 Retrospective Evidence use?

About 756 tokens (SKILL.md is roughly 3k 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 Retrospective Evidence?

Skills that share tags, products or a category with Retrospective Evidence: Dough Story Wrap Up (terryyin/lizard, 2.5k stars), Retro (koolamusic/claudefiles, 130 stars), Retrospective (Apocrathia/home-assistant-config, 179 stars) and Agile Workflow (jwynia/agent-skills, 170 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Retrospective Evidence?

oocx (a GitHub user) maintains it in oocx/tfplan2md, which has 174 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 9, 2026.

Source: oocx/tfplan2md on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.