decompose-plan
Skill2 starsChanged 6 days agoMITView on GitHub
Splits an epic or feature into child tasks a build can check: EARS criteria, scope, dependencies and a demonstration command. Use to split work into tasks, or when the plan gate refuses a child.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- niksavis/handilyedited, first seen Nov 8, 2026
- RndmCodeGuy20/ordnancetheir own version, first seen Aug 25, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- niksavis/handily★ 217% same
Wrote their own version · 1
- RndmCodeGuy20/ordnance★ 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 repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- best-practices-auditSkill
- catalog-authoringSkill
- cli-toolsSkill
- conventional-commitsSkill
- councilSkill
- falsify-firstSkill
- find-skillsSkill
- harness-clientSkill
- harness-loopSkill
- hill-climbSkill
- interface-factsSkill
- no-commentsSkill
- nodeSkill
- plain-englishSkill
- pythonSkill
- release-processSkill
- repair-in-placeSkill
- retention-probeSkill
- root-causeSkill
- session-finishSkill
- skill-creatorSkill
- swarmSkill
- test-disciplineSkill
- tier-injectionSkill
- validate-as-consumerSkill
- work-trackerSkill
- worktree-isolationSkill
- best-practices-auditSkill
- catalog-authoringSkill
- cli-toolsSkill
- conventional-commitsSkill
- councilSkill
- decompose-planSkill
- falsify-firstSkill
- find-skillsSkill
- harness-clientSkill
- harness-loopSkill
- hill-climbSkill
- interface-factsSkill
- no-commentsSkill
- nodeSkill
- plain-englishSkill
- pythonSkill
- release-processSkill
- repair-in-placeSkill
- retention-probeSkill
- root-causeSkill
- session-finishSkill
- skill-creatorSkill
- swarmSkill
- test-disciplineSkill
- tier-injectionSkill
- validate-as-consumerSkill
- work-trackerSkill
- worktree-isolationSkill
The file
Files
<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. -->Decompose a plan the gate accepts
Cut one parent record, an epic or a feature, into children that each do something a consumer can see. The plan gate refuses an incomplete child before any build starts.
Rules
- Slice vertically. Each child changes something a consumer can see, so verify has something to check. A schema-only or tests-only child is a horizontal cut.
- Give every child a runnable demonstration in backticks, on one line.
- Scope the file that produces the value, not the file that shows it, and name the child's own file, never a directory glob. Scoping shows how to find the producer.
- Flatten, never nest. A child that needs children was cut wrong.
Steps
- Find the producer of each value the work changes, as scoping shows.
Write
plan.toml:[[children]] title = "Refuse a flag with no expiry" acceptance = ["When basicly flag add runs without --expires, the command shall exit 2 and name the flag."] scope = ["src/basicly/flags.py", "tests/test_flags.py", "changelog.d/PARENT-ID.1.added.md"] depends_on = [] demonstration = "`basicly flag add beta --owner me` exits 2 and prints the missing --expires"Preview it with
--dry-run. A line that reads`PATH`: collapses the groupingmeans more than one child writes that path. Give the path to one child, or list it undersharedwhen each child only appends to it. Then run without--dry-run:basicly decompose PARENT-ID --plan plan.toml --dry-run basicly decompose PARENT-ID --plan plan.toml
The plan fields
| Field | Refused when | Notes |
title | absent | Sibling titles are the names depends_on uses. |
acceptance | absent | Write each criterion in EARS form (trigger, state, condition, optional feature, ubiquitous), so a check can be derived from it. |
scope | absent | Two children that write one path serialize. |
depends_on | absent, or cyclic | An empty list is a declaration; an absent key is not. A cycle is refused with its members before any record is created. |
demonstration | absent, no backticked runnable span, or spread over several lines | A command, a request or a test through the consumer surface. |
shared | optional | Paths from scope that each child only appends its own entry to, such as a lockfile. |
type | empty, or not a string | Optional. An absent type makes the child a task. |
budget_tokens | present but invalid | Optional. Omit it when the user sets no limit. |
integrity | present but invalid | Optional. |
Spending limits and historical integrity fields are optional.
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.

