agentleFS
tcrosslandtcrossland/claude-code-methodology/.claude/skills/close-plan/SKILL.md

close-plan

Skill0 starsChanged 5 months agoApache-2.0View on GitHub

Close out a completed plan in docs/plans/ — set the done status, tick stage markers, clear the active-plan pointer, and archive the file. Use when a plan's work is finished and verified.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. anthropics/knowledge-work-plugins★ 36ksame name
    2. khairold/claude-skills★ 0same name
    3. koruworks/skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

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

    Only close a plan whose work is actually finished and verified (Definition of Done met).

    line 13
  2. Very specific:

    Use British DD/MM/YYYY (today, from the environment's current date).

    line 22

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

Close out a completed plan

Closing a plan is four mechanical steps that are easy to half-do by hand — the failure mode is a plan marked done but with [current] markers left in place, the file still in docs/plans/, and the backlog still pointing at it. Do all four, in order, every time.

Only close a plan whose work is actually finished and verified (Definition of Done met). If a stage was dropped or deviated, record that in the plan rather than ticking it clean.

Steps

  1. Set the done status. Edit the plan's **Status:** line to:
    **Status:** done (DD/MM/YYYY) — <one-line summary: stages complete + the headline outcome>.
    Use British DD/MM/YYYY (today, from the environment's current date). If a stage deviated or was cut, say so here in a clause rather than pretending it was clean.
  2. Tick every stage marker. Replace each ## Stage N — … [current] or [not started] (the skeleton's three marker states are [done]/[current]/[not started]) with [done], and tick the remaining - [ ] step checkboxes that were completed. Confirm none are left:
    grep -nE '\[current\]|\[not started\]|^- \[ \]' docs/plans/<name>.md   # should print nothing
    A genuinely skipped step stays - [ ] with a deviation note — don't tick it to silence the grep.
  3. Clear the active-plan pointer. In docs/backlog.md, reset ## Now (this plan) to:
    - (none — no active plan)
    docs/backlog.md's ## Now (this plan) is this repo's single pointer to the live plan (the §3 active-plan pointer); a cold-start session reads it to know nothing is live.
  4. Archive the file. Move it so history follows — git mv if the plan is already tracked, plain mv if it was created this session and never committed (git mv errors on an untracked file; the mv fallback stages the new path explicitly, since the repo forbids git add -A):
    git mv docs/plans/<name>.md docs/plans/archive/<name>.md \
      || { mv docs/plans/<name>.md docs/plans/archive/<name>.md && git add docs/plans/archive/<name>.md; }
    Optionally add a trailing HTML comment recording archival and any friction worth a backlog item, matching the existing archived plans:
    <!-- Completed in-session; archived under docs/plans/archive/ (§3). -->

Out of scope

  • Shipping the plan's user-facing outcome to CHANGELOG.md — that is /release's job.
  • Deciding what runs next — picking the next backlog item is a separate step, not part of closing.

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.