agentleFS
nshopiknshopik/dream-team/skills/milestone-close/SKILL.md

milestone-close

Skill2 starsChanged 19 days agoMITView on GitHub

Closes a tracker milestone: checks its exit criterion, triages its open issues, checks docs against code and offers a release. Use when the user asks to close, wrap up or review a milestone — "close milestone 4", "is M4 done", "wrap up the dogfood milestone".

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read-only until step 5, except step 2's approved gap issues.

    line 12
  2. Very specific:

    Ask only for what leaves the docs MR or changes agent rules: issues, closes, moves, milestones, CLAUDE.md and CLAUDE.local.md lines, and a …

    line 17
  3. Very specific:

    Run or read the measurement it names: gate floors, a recorded run, a deployed host.

    line 36
  4. Very specific:

    Not met → report the gap, and propose the gap issues per scope-issue, light-tier ones bundled, in this milestone.

    line 39
  5. Very specific:

    Every close, M<n> and version milestone alike, whose version no project rule sets → load ship-it.

    line 102
  6. Distinctive:

    Before any other step 5 action:

    line 111
  7. Distinctive:

    No such proposal → do not wait for answers.

    line 115

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

milestone-close

Read-only until step 5, except step 2's approved gap issues. The user decides every close, move and filed issue.

  • An edit that lands in the docs MR needs no approval: the user reviews it there, once step 5 opens the MR.
  • Ask only for what leaves the docs MR or changes agent rules: issues, closes, moves, milestones, CLAUDE.md and CLAUDE.local.md lines, and a release the project rules do not settle.

1. Read the milestone

  • The milestone is not numbered M<n>, YY.MM or v<major>.<minor> (SemVer past 1.0) → stop and tell the user the repo may not be set up for dream-team, naming setup-dream-team; check, propose or preview no later step.

Milestone description, and its roadmap row if it has one. No measurable exit criterion → stop and ask for one; a milestone without one cannot close.

The ROADMAP and specs folder are at the paths <base directory>/../../references/repo-conventions.md resolves.

A version milestone's Gate: bullet holds its release criteria; check each item there too.

2. Check the criterion

Run or read the measurement it names: gate floors, a recorded run, a deployed host. A field-evidence gate reads its Evidence: issue for the deploy, the start date and how to collect.

Not met → report the gap, and propose the gap issues per scope-issue, light-tier ones bundled, in this milestone. The user approves or rejects each; file the approved ones and stop. The milestone stays open.

A failed kill-gate (the criterion names a redesign) gets no gap issues: report it and stop. The redesign goes back to the spec.

Outside flow mode, an open headline issue in a version milestone is its own gap; file nothing for it. Past the ship-by date, or a YY.MM milestone's due date, the user picks between moving the headline to the next version and a new date. A new date for a YY.MM milestone renames it to the new month and moves its due date to that month's last day.

The project CLAUDE.md says Version milestones release in flow mode. → a version milestone's criterion is met at its due date, and an open headline is no gap.

3. Triage open issues

One table: issue, title, proposed action — close (done or obsolete; cite the commit or reason), move (target from the tracker's open milestones and the roadmap's planned rows; a planned row target → no milestone and workflow::future), or blocks-close. The user answers in one reply. In a version milestone, an open backlog issue defaults to move, to the next version; in flow mode, so does an open headline.

Meta: issues stay out of the table. List each meta issue with a child in this milestone; tick the boxes of closed children in its description.

  • A Meta: issue set to this milestone with an open child → it moves with that child.

4. Docs check

Collect the docs-MR edits and the proposals; fix nothing yet.

Docs-MR edits, applied in step 5 without asking:

  • Architecture doc and diagram against the workspace's component list.
  • Specs in the specs folder whose decision the code no longer follows, recorded on a closed issue or merged MR → a Superseded by status line. No such record → propose it.
  • README, docs/ pages, help text and comments: dispatch dream-team:docs-reviewer, told to read the milestone's merged diff with git diff <base>..<head>, <base> the first-merged MR's merge base and <head> the last-merged MR's merge commit.
  • Each 🔴/🟡 docs-reviewer finding, as a fix; leave its 🔵 findings out. A finding you judge wrong → drop it and name it in the report.
  • Roadmap, when the milestone has a row: status of the milestone's merged work, and the row against the criterion result. Feature MRs leave roadmap status to this step.
  • Root-cause and behaviour sections of the milestone's merged MRs → each fact a future change must respect that the contributor doc lacks, as one line.
  • The release, when the project's CLAUDE.md or AGENTS.md sets the version each close takes: ship-it's Bump step. The tag is still offered after the merge.

Proposals, each approved or rejected by the user:

  • Each planned roadmap row with no tracker milestone of its title, whose every Depends on: entry is a closed milestone or this one → propose it as a tracker milestone, numbered with the next free M<n>, with a <due date> and the parked issues that belong to it, in ROADMAP order until 3 M<n> milestones would be open, this one not counted; it is approved only once the user sets its <due date>.
  • Each project CLAUDE.md and CLAUDE.local.md line, proposed as a cut when the path or tool it names is gone, its only content is one closed issue's artifacts rather than a gotcha, a hook or CI enforces it now, a global rule already says it, or a change outside the repo could fix the gotcha it works around (a lab host's config, a missing tool, a plugin bug), recommending that change.
  • Each other CLAUDE.local.md line: proposed as a promotion to CLAUDE.md when it holds no hostname, IP, internal URL or lab access, otherwise left alone.
  • Every close, M<n> and version milestone alike, whose version no project rule sets → load ship-it; propose a release per its Propose step.
  • A milestone with MVP in its title, in a repo whose last release is 0.x or none → propose this month's <YY.MM>.0, the first CalVer release, in place of the next 0.x minor.
  • In a SemVer repo, a v<x.y> milestone whose major is above the version file's → warn in the release proposal that its name says a major release, naming both versions.

5. Apply

Before any other step 5 action:

  • At least one numbered proposal changes CLAUDE.md (a cut from it or a promotion) → send the held report per Report back, and wait for the user's one reply.
  • No such proposal → do not wait for answers; carry on with the rest of step 5 and open the docs MR once its edits are committed.
  • A proposal the user rejects changes nothing; the docs-MR edits still land in the MR.

The approved closes and moves, through the host's tooling skill; an obsolete close is not planned and adds wontfix, and the Evidence: issue closes with the milestone. Step 4's docs-MR edits, the approved Superseded by lines, the approved CLAUDE.md cuts and promotions as one MR; approved promotions and cuts leave CLAUDE.local.md directly, since it is untracked. Then close the milestone and set its roadmap status, if it has a row. Create each approved planned row's milestone per cut-milestones step 5, move its parked issues into it without workflow::future, then set the row's # and its status not started in the docs MR. Every milestone whose Depends on: is now all closed is ready: drop workflow::future from its open issues.

  • docs-reviewer fixes → dispatch dream-team:docs-editor in drift mode with git diff <base>..<head> from step 4 and only the pages they name; its edits go in the docs MR.
  • Release set by a project rule, or approved → ship-it Bump and Tag steps, its bump in the docs MR and its tag message naming the milestone; with nothing else in it, the release alone opens the MR.

Report back

Criterion result, issues closed, moved and filed, milestones created, the docs MR link, each docs fix docs-editor reported as skipped: or under gaps:, the release version and its tag, or the tag pending the docs MR's merge, or the declined release.

A numbered proposal that changes CLAUDE.md is unanswered → send only the held report: criterion result, step 4's docs-MR edits and the proposals below, with no docs MR link. After step 5 applies the user's reply, send the full report above, with the link.

Step 4's docs-MR edits: one bullet in the report, each edit named in the docs MR description, or in the bullet in a held report; never numbered as proposals.

Proposals from step 2 or 4:

  • Number them; ask the user to approve them by number.
  • A cut that waits on a fix outside the repo → one unnumbered Outside the repo: line naming the fix; propose the cut once the user reports the fix made.
  • Under each, name what approving it does: an issue filed, a milestone created, a line added, removed or moved to CLAUDE.md, a Superseded by line in the docs MR, or a version bump and CHANGELOG move in the docs MR.

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.