write-plan
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Use when you've already decided on a discrete piece of work and want to file it as one self-contained plan in a repo's plans/ for a separate zero-context executor (e.g. the plan-executor loop) to implement. Triggers — "/write-plan", "write a plan", "save/capture this as a plan", "file this for the executor", "hand this off", "turn this into a plan". Not for discovering what to do (use improve) or plans this same session will execute itself (use writing-plans).
- Commits and pushes
25 other projects use a version of this.
Adopted by
Most recently taken up by
- adhamhaithameid/write-skillstheir own version, first seen Nov 8, 2026
- Ovich/charrettetheir own version, first seen Nov 7, 2026
- nikhilw/structured-agentic-workflowtheir own version, first seen Nov 6, 2026
- javierbrea/eslint-plugin-boundariestheir own version, first seen Nov 2, 2026
- pahlevikun/levistacktheir own version, first seen Nov 1, 2026
- davisbuilds/dojotheir own version, first seen Nov 1, 2026
Used with
Projects with it also use write-spec, execute-plan and 8 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.
AnthropicSkillwrite-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
Also in 6 projects that use this
TheKREATORSSkillexecute-plan
Deprecated - use the superpowers:executing-plans skill instead
Also in 6 projects that use this
renatorozasSkillgrill
Adversarial code review. Don't let me ship until the changes pass your scrutiny.
Also in 3 projects that use this
varun29ankuSSkillorchestrate
This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 5 projects that use this
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 3 projects that use this
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- foambubble/foam★ 17ksame name
- javierbrea/eslint-plugin-boundaries★ 1ksame name
- Arman-Kudaibergenov/1c-ai-development-kit★ 163same name
- alamops/skills★ 53same name
- Ovich/charrette★ 14same name
- Ovich/swarmstorm★ 14same name
- ariadoss/superskills★ 12same name
- nikhilw/structured-agentic-workflow★ 7same name
- preetamnath/agent-skills★ 4same name
- Gusen1453/creed★ 3same name
15 more not listed
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 repository12 other files it gives its agents.
- devSkill
- followupsSkill
- glow-paneSkill
- html-designSkill
- image-paneSkill
- simplifySkill
- thermo-nuclear-code-quality-reviewSkill
- verifying-thoroughlySkill
- web-design-guidelinesSkill
- worktree-cleanupSkill
- worktree-shipSkill
- worktree-syncSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 3 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 19 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.
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.