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

milestone-review

Skill4 starsChanged 6 days agoMITView on GitHub

Reviews progress against milestones: scope, schedule, risk, quality, dependencies and re-planning.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use soak-test, team-live-ops and 10 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

    soak-test

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

    Also in 9 projects that use this

  • lilangMaxSkill

    team-live-ops

    Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

    Also in 9 projects that use this

  • +10 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 18 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. Very specific:

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

    line 26
  2. Very specific:

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

    line 28
  3. Distinctive:

    Update the plan after approval

    line 43
  4. Distinctive:

    Before recommending changes: agree the causes

    line 46
  5. Distinctive:

    Before updating the plan: approve the option

    line 47

“Common” is measured: kept by at least 6 in 10 of the 18 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/milestone-review/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->

/milestone-review — Milestone Review

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

Reviews progress against milestones: scope, schedule, risk, quality, dependencies and re-planning.

Arguments: whatever the user wrote after the command name.

Purpose

Review a modeling project against its milestones: what was delivered, what slipped and why, how risks and open validation issues have evolved, and whether scope or schedule must change. The output is an honest status with re-planning options and their trade-offs, and an updated plan once the user approves.

Use it when a milestone date arrives, a project slips, or scope pressure builds.

Do not use it when the question is whether a stage's exit criteria are met (/gate-check).

Before you start

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • Project plan
    • Production notes 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
  • modeling-methodology-specialist — Chooses methods and architecture across model families, sets code and data standards, and resolves technical trade-offs between traditional, structural and AI approaches
  • economic-reasoning-specialist — Frames the economic question and tests whether results make economic sense

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. Compare plan and actuals; list slippage and causes
    • Distinguish data delays, model problems, validation findings and scope changes
  2. Review risk register and open validation issues
  3. Recommend scope or schedule changes with trade-offs
    • Protect validation and documentation time rather than cutting it
  4. Update the plan after approval

Checkpoints with the user

  • Before recommending changes: agree the causes
  • Before updating the plan: approve the option

Common pitfalls

  • Cutting validation to recover schedule
  • Causes listed without owners
  • Re-planning that ignores dependencies

Output

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

The review records plan versus actual, causes of slippage, risks, open issues, options with trade-offs and the approved plan change.

Gate / verdict

  • Slippage has causes and owners
  • Validation and documentation time are not silently removed

Suggested next steps

  • /retrospective
  • /gate-check

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.