agentleFS
Sign inStart free
ejwhite7ejwhite7/product-release-checklist/skills/launch-retro/SKILL.md

launch-retro

Skill0 starsChanged 35 days agoMITView on GitHub

Run a launch retrospective in the release checklist studio and feed the lessons back into the system (benchmarks, extra checklist items). Use for "Run retro" requests, 1–2 weeks after T-0, or for "launch retro", "post-mortem", or "what did we learn from this launch".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Feed the system: If an export folder is set, append the benchmarks row to <exportDir>/benchmarks.md.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Launch Retro

  1. Gather the evidence:
    • from the checklist: which items slipped (due later than planned), were waived (read the reasons in note), or ended N/A
    • feedback and measure.readouts
    • the user's note (Slack threads, meeting notes)
  2. Write retro:
    • outcome: one line with numbers against the goal
    • worked: the channels or assets that drove activation, with evidence from measure.channels
    • didnt: specific failures. For example: "KB went live at T+1, and 40% of first-day tickets asked how to enable it."
    • gaps: work the checklist was missing, or that sat in the wrong phase
    • benchmarks: the actual exposure %, discovery %, activation %, cost per activation and email CTR
  3. Feed the system. If an export folder is set, append the benchmarks row to <exportDir>/benchmarks.md. Future targets will use it.
  4. Propose checklist changes in chat. Add them to this launch's custom only if the user agrees. For changes to every future launch, suggest editing ITEMS in the plugin's studio/model.mjs.

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.

Check your setup, free