to-plan
Skill5 starsChanged 8 days agoMITView on GitHub
Generate the approach, phases, waves, and checks inside the locked `.harness/plans/active/{slug}.md`. Use after `brainstorm` for a `high-risk` plan; a `normal` plan goes straight to `work`.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Integralist/agent-skillstheir own version, first seen Nov 6, 2026
- GulajavaMinistudio/polya-sdlc-codertheir own version, first seen Oct 25, 2026
- bingelp/skillstheir own version, first seen Oct 20, 2026
- anis-dr/skillstheir own version, first seen Oct 15, 2026
- Jaeyong-Cho/skillstheir own version, first seen Aug 20, 2026
- SrdjanCoric/skillstheir own version, first seen Aug 2, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- chrisbanes/skills★ 1.1ksame name
- Integralist/agent-skills★ 23same name
- SrdjanCoric/skills★ 18same name
- GulajavaMinistudio/polya-sdlc-coder★ 16same name
- Akindu23/my-agent-skills★ 4same name
- anis-dr/skills★ 3same name
- Jaeyong-Cho/skills★ 1same name
- bingelp/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.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Write executable steps, not planning prose.
“Common” is measured: kept by at least 6 in 10 of the 8 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
Write executable steps, not planning prose.
Resolve the mode, then follow references/to-plan.md (.harness/WORKFLOW.md IF routing is unclear).
Resolve cross-stage transitions through the host's skill metadata; do not assume a shared installation parent. Resolve data paths from the consumer repository root. If a required skill or reference is unavailable, report the missing dependency and stop; retained legacy playbooks are not a fallback.
Defer to: work for a normal plan (lock already wrote its phase); brainstorm when the locked input is missing or weak; work executes the phase next; check gates after implementation.
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.