agentleFS
alvin-reyesalvin-reyes/better-agentic-ide/.claude/skills/bmad-retrospective/SKILL.md

bmad-retrospective

Skill43 starsChanged 32 days agoMITView on GitHub

Review a finished epic folder in the ticket tree against the evidence it left behind — the epic file, each ticket plan, diffs, commits — and produce a retrospective with sourced findings, action items, and an acceptance decision. Use when the user says "run a retrospective" or "lets retro the epic [epic]". Supports -H/--headless

23 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use bmad-dev-auto, bmad-editorial-review and 2 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.
  • areesh-aliSkill

    bmad-dev-auto

    One iteration of an unattended development loop. Use when invoked by name.

    Also in 8 projects that use this

  • 2233adminSkill

    bmad-editorial-review

    Deprecated — forwards to bmad-review.

    Also in 6 projects that use this

  • 2233adminSkill

    bmad-review-verification-gap

    Deprecated — forwards to bmad-review.

    Also in 6 projects that use this

  • GauravRatnawatSkill

    bmad-checkpoint-preview

    LLM-assisted human-in-the-loop review. Make sense of a change, focus attention where it matters, test. Use when the user says "checkpoint", "human review", or "walk me through this change".

    Also in 15 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the following command exactly once without changing the current working directory.

    line 6
  2. Very specific:

    If the script does not exist, BMad is not set up in this project yet.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 23 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run the following command exactly once without changing the current working directory. Replace {project-root} with the absolute path to the project root and {skill-root} with the absolute path to this skill's directory:

node {project-root}/_bmad/ade-runtime.mjs render_skill --project-root "{project-root}" --skill "{skill-root}"
  • The command should print one line to stdout. read and follow <rendered workflow.md>: read that file and follow it. HALT: <reason>: report the reason and stop.
  • If the script does not exist, BMad is not set up in this project yet. Offer to set it up using bmad skill, then run the command again. If you do not have the bmad skill, offer to install it first.
  • On any other output or failure, including uv being unavailable, report the command output and stop. Do not run any workflow source directly.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.