close-plan
Skill0 starsChanged 7 months agoMITView on GitHub
Close a completed .plan/ and persist valuable information into the project's own documentation. Discovers repo structure, extracts decisions/gotchas/parked items, proposes routing, gets human confirmation, writes updates, and removes .plan/. Use when a phased plan is fully complete.
- Deletes or force-pushes
3 other projects use a version of this.
Adopted by
Most recently taken up by
- koruworks/skillstheir own version, first seen Oct 15, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- tcrossland/claude-code-methodologytheir own version, first seen Oct 11, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- anthropics/knowledge-work-plugins★ 36ksame name
- koruworks/skills★ 0same name
- tcrossland/claude-code-methodology★ 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 repository8 other files it gives its agents.
- autopilot-executeSkill
- deep-modules-auditSkill
- docs-auditSkill
- execute-phaseSkill
- lint-fixSkill
- living-design-systemSkill
- phased-planSkill
- responsive-auditSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 7 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Read all .plan/ files:
- Distinctive: line 75
Read the top of each candidate file to understand its purpose and structure.
- Distinctive: line 124
If the human redirects items (e.g., "put parked items in TODO.md instead"), adjust accordingly.
- Distinctive: line 130
Read the destination file fully to understand its current structure
- Distinctive: line 131
Add the new information in a style consistent with the existing content — match heading levels, table formats, list styles, voice
- Distinctive: line 132
Don't duplicate information already present in the destination
- Distinctive: line 133
If adding to a table, continue the existing numbering
- Distinctive: line 134
If a destination file doesn't exist and the human approved creating it, create it with minimal structure
- Very specific: line 141
Check that .agents/TENSIONS.md has any tension entries from the plan (these already live outside .plan/)
- Very specific: line 142
Remove the .plan/ directory:
“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.
Files
Close Plan
Close a completed .plan/ directory by persisting valuable information into the project's permanent documentation, then cleaning up. This skill is project-agnostic — it discovers where things should go rather than assuming a fixed structure.
Prerequisites
- A
.plan/directory exists with completed plan files - The plan is fully complete (all phases done) or the human has decided to close it early
Step 1 — Read Plan Files
Read all .plan/ files:
.plan/PLAN.md— completed items, parking lot.plan/MEMORY.md— decisions, gotchas, architecture notes, technical context.plan/DRIFT.md— spec deviations that were accepted.plan/SESSION-LOG.md— skim for any context not captured elsewhere
Step 2 — Extract Persistable Information
Sort everything from the plan files into these categories:
A. Key Decisions
Decisions and their rationale that affect future work on this project. Skip decisions that were phase-specific and no longer relevant.
B. Gotchas & Warnings
Permanent gotchas that will trip up future sessions. Skip phase-specific workarounds that no longer apply.
C. Architecture Changes
Structural changes to the codebase — new packages, changed patterns, new conventions. Only include if the project's architecture docs don't already reflect them.
D. Parked Items
Unchecked items from the Parking Lot section of PLAN.md. These are future work candidates.
E. Accepted Drift
Spec changes from DRIFT.md that were accepted. The project's source of truth (spec, README, architecture docs) should reflect these if it doesn't already.
F. Tensions
Any entries added to .agents/TENSIONS.md during the plan. These already live outside .plan/ — just verify they're present.
Discard (do not persist)
- Session log entries (ephemeral — they served their purpose)
- Completed item checklists (the work is done, the code is the record)
- Phase-specific context that's no longer relevant
- Anything already captured in the repo's permanent docs
Step 3 — Discover Destination Candidates
Scan the repo for files that could receive persistent information. Look for:
# Common documentation files (check root, docs/, .agents/, .pi/)
find . -maxdepth 3 -type f \( \
-name "CLAUDE.md" -o \
-name "AGENTS.md" -o \
-name "README.md" -o \
-name "ARCHITECTURE.md" -o \
-name "ROADMAP.md" -o \
-name "CONVENTIONS.md" -o \
-name "TENSIONS.md" -o \
-name "ADR.md" -o \
-name "CHANGELOG.md" -o \
-name "TODO.md" \
\) | head -30Also check for directories like docs/, docs/adr/, .agents/.
Read the top of each candidate file to understand its purpose and structure.
Step 4 — Propose Routing
Present the extracted information and proposed destinations to the human in this format:
📋 Plan Close-Out: {plan name from PLAN.md header}
## Extracted Information
### Key Decisions ({count})
{List each decision with a one-line summary}
→ Proposed destination: {file} — {section or location within file}
(or: ⚠️ No obvious destination found — will skip unless you specify one)
### Gotchas & Warnings ({count})
{List each gotcha}
→ Proposed destination: {file} — {section}
### Architecture Changes ({count})
{List each change}
→ Proposed destination: {file} — {section}
### Parked Items ({count})
{List each item}
→ Proposed destination: {file} — {section}
(or: → No roadmap/TODO file found — create one? Skip?)
### Accepted Drift ({count})
{List each drift entry}
→ Proposed destination: {file} — {section}
(or: → Already reflected in source of truth — no action needed)
### Discarding
- {count} session log entries
- {count} completed checklist items
- {other ephemeral items}
Confirm this routing, or tell me what to change.Wait for human confirmation before proceeding.
If the human redirects items (e.g., "put parked items in TODO.md instead"), adjust accordingly. If the human says to skip a category, skip it.
Step 5 — Execute Writes
For each confirmed routing:
- Read the destination file fully to understand its current structure
- Add the new information in a style consistent with the existing content — match heading levels, table formats, list styles, voice
- Don't duplicate information already present in the destination
- If adding to a table, continue the existing numbering
- If a destination file doesn't exist and the human approved creating it, create it with minimal structure
Important: Integrate, don't append a dump. The destination file should read naturally — as if the information was always there. No "Persisted from .plan/" headers or metadata.
Step 6 — Verify & Clean Up
- Confirm all writes landed correctly — read back each modified file and verify the new content is present and well-integrated
- Check that
.agents/TENSIONS.mdhas any tension entries from the plan (these already live outside.plan/) - Remove the
.plan/directory:
rm -rf .plan/- Report what was done:
✅ Plan closed: {plan name}
Persisted:
- {count} decisions → {file}
- {count} gotchas → {file}
- {count} parked items → {file}
- ...
Discarded:
- {count} session log entries
- {count} completed items
Cleaned up:
- .plan/ removedRules
- Never persist without confirmation — Always show the routing proposal and wait for the human to confirm. This is the critical gate.
- Never lose parked items silently — Parked items are future work the human explicitly deferred. They must either be routed to a destination or the human must explicitly say to discard them.
- Integrate, don't dump — Destination files should read naturally after the update. Match existing style, structure, and voice.
- When in doubt, ask — If you're unsure whether something is worth persisting or where it should go, ask. Don't guess.
- No partial cleanup — Either complete the full close-out (all writes confirmed and executed) then delete
.plan/, or abort and leave everything intact. No half-states. - Idempotent discovery — If a decision or gotcha already exists in the destination file, skip it. Don't create duplicates.
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
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.

