new-plan
Skill0 starsChanged 6 months agoMITView on GitHub
Scaffold a new docs/plans/YYYY-MM-DD-<slug>.md design doc. Use before starting any feature or non-trivial change — the team requires a plan before implementation.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- MusserLab/lab-claude-skillstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- MusserLab/lab-claude-skills★ 6same 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 repository3 other files it gives its agents.
- checkSkill
- new-registry-entrySkill
- new-routeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 15
Get the date: Run date +%Y-%m-%d for today's date as YYYY-MM-DD.
- Very specific: line 17
Get the slug: Use the user's argument if given, else ask.
- Very specific: line 24
Mirror existing shape: Look at the 2–3 most recent files in docs/plans/:
- Distinctive: line 47
Stop after creating the file: Do not start implementing — give the user a chance to read, edit, and approve the plan first.
- Distinctive: line 52
After creating the file, print:
≈ “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.
Files
/new-plan — scaffold a planning doc
Project rule (workflow): write a plan in docs/plans/ before implementing
any feature or non-trivial change. The plan is the contract; the PR
should match it.
Steps
- Get the date. Run
date +%Y-%m-%dfor today's date asYYYY-MM-DD. - Get the slug. Use the user's argument if given, else ask. Slug
format: lowercase, hyphenated, ~3–5 words, no trailing extension.
Example:
request-id-propagation. - Path:
docs/plans/<date>-<slug>.md. If the file already exists, stop and ask the user whether to update or pick a different slug. - Mirror existing shape. Look at the 2–3 most recent files in
docs/plans/:
Teams converge on a particular section structure. Skim those files and use the same headings + ordering. Do not invent new shapes.ls -t docs/plans/*.md | head -3 - Typical sections (cross-check against the recent files):
- Problem / context — what's broken or missing, with concrete
pointers (
file:line, ticket links, prior plan references). - Goal — one or two sentences of what done looks like.
- Non-goals — explicit out-of-scope, to prevent scope creep.
- Design — chosen approach. Include alternatives considered if the decision was non-obvious.
- Milestones — discrete, reviewable steps. Map to commits or PR stages.
- Risks / unknowns — what could go wrong, what you don't know yet.
- Test plan — how we'll know it works (unit, integration, manual, observability).
- Rollout — flag gating, env order (local → dev → uat → prod), any migration steps.
- Problem / context — what's broken or missing, with concrete
pointers (
- Stop after creating the file. Do not start implementing — give the user a chance to read, edit, and approve the plan first.
Output
After creating the file, print:
created docs/plans/<date>-<slug>.md — open it, fill in the sections, then
say "go" when you're ready to implement.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.

