agentleFS
tatashbartatashbar/Economic-Modeling-Studio/.agents/skills/retrospective/SKILL.md

retrospective

Skill4 starsChanged 6 days agoMITView on GitHub

Runs a retrospective on a forecast round, model build or project: what worked, what failed, what to change.

73 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dev-story, team-level and 9 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.
  • lilangMaxSkill

    dev-story

    Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before /code-review and /story-done.

    Also in 12 projects that use this

  • CoralGameSkill

    team-level

    Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.

    Also in 12 projects that use this

  • CoralGameSkill

    team-narrative

    Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.

    Also in 12 projects that use this

  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • +7 more from lilangMax

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 62 edited versions we read keep these.

  • 3

    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. Distinctive:

    Run a retrospective on a forecast round, model build or project: gather the facts, decompose forecast errors into data, model, judgment and …

    line 16
  2. Very specific:

    If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.

    line 26
  3. Very specific:

    Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …

    line 28
  4. Distinctive:

    Use data revisions, model reruns with final data and the overlay log

    line 40
  5. Distinctive:

    After the error decomposition: agree the main lessons

    line 45

“Common” is measured: kept by at least 6 in 10 of the 62 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
<!-- Generated from .claude/skills/retrospective/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->

/retrospective — Retrospective

Category: Governance · Primary agent: project-planning-specialist

Runs a retrospective on a forecast round, model build or project: what worked, what failed, what to change.

Arguments: whatever the user wrote after the command name.

Purpose

Run a retrospective on a forecast round, model build or project: gather the facts, decompose forecast errors into data, model, judgment and unforeseen shocks, and turn lessons into actions with owners. The output improves the next round rather than assigning blame.

Use it when a forecast round or project ends, or after a large forecast miss.

Do not use it when the aim is to re-plan an ongoing project (/milestone-review).

Before you start

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • Project artifacts
    • Forecast errors if relevant If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
  2. Check confidentiality. Identify the data classification level of the inputs (.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow.
  3. Collaboration. Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and update production/session-state/active.md after each approved section.

Agents

  • project-planning-specialist — primary agent; coordinates the work and integrates results
  • economic-reasoning-specialist — Frames the economic question and tests whether results make economic sense
  • forecast-evaluation-specialist — Evaluates forecasts

Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.

Workflow

  1. Gather facts: plan vs. actual, forecast errors, issues, rework
  2. Decompose errors by data, model, judgment and shocks where relevant
    • Use data revisions, model reruns with final data and the overlay log
  3. Identify process and methodology changes
  4. Record actions with owners

Checkpoints with the user

  • After the error decomposition: agree the main lessons

Common pitfalls

  • Attributing every miss to unforeseeable shocks
  • Lessons without actions
  • Ignoring what went well

Output

production/retrospectives/<name>-<date>.md

The record documents facts, error decomposition, lessons, and actions with owners and dates.

Gate / verdict

  • Each lesson has an action and an owner
  • Error decomposition uses the overlay log where judgment was applied

Suggested next steps

  • /milestone-review

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.