planning-workflow
Skill0 starsChanged 7 months agoMITView on GitHub
Use when work is already clear enough to execute but still too large to implement safely without a written plan. Trigger for multi-step features, refactors, risky bug fixes, or coordinated agent work that should be broken into bounded tasks with validation checkpoints. Do not use to clarify vague goals; start with `spec-writing` when the request itself is still underspecified.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- pfeff/claude-skillstheir own version, first seen Nov 1, 2026
- DITlieD/ELAI-archivetheir own version, first seen Sep 5, 2026
- 2702207741-dev/agent-skills-pipelinetheir own version, first seen Jul 9, 2026
- Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrationstheir own version, first seen Jun 19, 2026
- indubitably-ai/indubitably-skillstheir own version, first seen Apr 17, 2026
- LazyWorkshopCreate/agent-based-workflowtheir own version, first seen Mar 25, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations★ 73same name
- DITlieD/ELAI-archive★ 24same name
- LazyWorkshopCreate/agent-based-workflow★ 9same name
- pfeff/claude-skills★ 3same name
- 2702207741-dev/agent-skills-pipeline★ 1same name
- indubitably-ai/indubitably-skills★ 1same 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- decision-recordingSkill
- harness-bootstrapSkill
- issue-driven-workflowSkill
- review-workflowSkill
- spec-writingSkill
- subagent-workflowSkill
- technical-learning-noteSkill
- troubleshooting-workflowSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
4
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
- Distinctive: line 14
Read the current issue or spec before changing code.
- Distinctive: line 17
Prefer vertical slices over layer-by-layer work when possible.
- Distinctive: line 18
Put acceptance and validation beside each task, not only at the end.
- Very specific: line 19
Use the issue doc's Plan and Validation sections unless the plan is large enough to deserve its own note.
- Distinctive: line 20
Stop once the next implementation steps are explicit enough to execute and track in the issue doc.
“Common” is measured: kept by at least 6 in 10 of the 5 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
Planning Workflow
Break a spec or issue into small tasks that another Codex user can execute without re-scoping the problem.
This skill is for implementation sequencing, not initial problem discovery.
Default flow
- Read the current issue or spec before changing code.
- Identify dependencies, risky areas, and blockers.
- Split the work into small validated steps.
- Prefer vertical slices over layer-by-layer work when possible.
- Put acceptance and validation beside each task, not only at the end.
- Use the issue doc's
PlanandValidationsections unless the plan is large enough to deserve its own note. - Stop once the next implementation steps are explicit enough to execute and track in the issue doc.
Good fit
- features that touch multiple files
- work that will span more than one session
- tasks that may involve sub-agents
- fixes where implementation order matters
Avoid for
- tiny edits with obvious scope
- tasks where the issue doc already has a solid task list
Resources
- See
references/plan-checklist.mdfor a short planning rubric. - Pair with
issue-driven-workflowto keep the plan attached to the real execution record.
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.