planning-and-task-breakdown
Skill0 starsChanged 4 months agoMITView on GitHub
Plans approved multi-step work as verifiable outcomes with dependencies, file ownership, and safe parallel boundaries. Use when breaking down an agreed spec, sequencing delivery, or coordinating parallel tasks; not for unresolved requirements or a small direct edit.
81 other projects use a version of this.
Adopted by
Most recently taken up by
- zademy/lu-querytheir own version, first seen Nov 16, 2026
- sirius-cc-wu/sirius-skillstheir own version, first seen Nov 16, 2026
- tkbk-online/skillstheir own version, first seen Nov 15, 2026
- addyosmani/agent-skillstheir own version, first seen Nov 14, 2026
- ishandutta2007/Awesome-Agent-Skillstheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
Used with
Projects with it also use constraint-driven-development, deprecation-and-migration and 9 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.
MrCipherSmithSkillconstraint-driven-development
Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
Also in 14 projects that use this
HK-hubSkilldeprecation-and-migration
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
Also in 34 projects that use this
HK-hubSkillobservability-and-instrumentation
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
Also in 26 projects that use this
seikaikyoSkilldoubt-driven-development
對非平凡決策啟動新鮮 context 對抗審查(找碴不背書),在修正還便宜的時候抓出錯誤方向。適用:高風險改動(production、資安敏感邏輯、不可逆操作)、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。
Also in 30 projects that use this
seikaikyoSkillinterview-me
需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。
Also in 31 projects that use this
GSA-TTSSkillarchitecture-decision-records
Load when a user wants architecture decision records (ADRs) drafted from requirements or a design discussion, asks which decisions need an ADR, or wants an ADR draft reviewed for one-sided trade-offs, weak alternatives or missing requirement links. Not for setting up a project's whole documentation system (project-documentation-system).
Also in 3 projects that use this
- +2 more from HK-hub
Other versions81 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 81
- addyosmani/agent-skills★ 118ksame name
- ollaya-dev/ollaya★ 1.4ksame name
- shashankswe2020-ux/whoop-mcp★ 181same name
- tranhieutt/software_development_department★ 71same name
- larchanka/skills★ 50same name
- vinvcn/addyosmani-agent-skills-zh★ 46same name
- jmxt3/gitscape.ai★ 33same name
- sampleXbro/agentsmesh★ 27same name
- jaskirat1616/grok-skills★ 22same name
- ishandutta2007/Awesome-Agent-Skills★ 21same name
71 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 repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-tool-interface-designSkill
- codebase-explorationSkill
- code-reviewSkill
- copilot-cloud-agentSkill
- documentation-maintenanceSkill
- external-skill-reviewSkill
- git-and-pr-workflowSkill
- parallel-worktree-deliverySkill
- refactoring-and-dead-code-removalSkill
- repository-agent-bootstrapSkill
- requirements-and-spec-writingSkill
- security-reviewSkill
- shadow-architectureSkill
- shadow-dreamSkill
- shadow-driftSkill
- shadow-observeSkill
- skill-creatorSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- verification-before-completionSkill
- verification-disciplineSkill
- wayfinder-planningSkill
- web-research-and-verificationSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 74 edited versions we read keep these.
4
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 27
Check dependencies and coverage.
- Distinctive: line 35
Use workers for substantial independent scopes when coordination costs are justified.
- Distinctive: line 40
Before creating or resuming a persistent task ledger, read the ledger protocol.
- Distinctive: line 57
Use the plan template for a requested durable plan.
“Common” is measured: kept by at least 6 in 10 of the 74 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 and Task Breakdown
Turn agreed requirements into the smallest useful execution plan. A clear edit answerable in two to five direct calls does not need a task tree or workers.
Workflow
- Confirm the target is agreed. Resolve consequential ambiguity before planning; do not ask again for requirements already supplied.
- List independently verifiable outcomes and what existing behavior must remain. Split large or unrelated outcomes into vertical slices, not one task per command, file read, or checklist item.
- For each task record: ID, purpose, true prerequisites, owned files, observable acceptance criteria, exact verification command or inspection, and size. Split anything larger than a medium task; make unverifiable work an open question rather than a completion claim.
- Check dependencies and coverage. Order prerequisites before dependents; introduce an intermediate interface task only when it reduces real coupling.
- Mark safe parallel sets. Independence requires no ordering dependency, overlapping writes, or shared mutable validation resources. Tasks sharing generated output, temporary directories, ports, or build state must be isolated or serialized. Assign one owner to shared integration/release gates.
- Choose execution granularity. Independence permits delegation; it does not require it. Keep cheap or continuous work local unless delegation is requested. Use workers for substantial independent scopes when coordination costs are justified; faster wall-clock work can still consume more model interactions.
- Give each worker its context, owned paths, no-edit boundaries, prerequisites, narrow checks, and stop condition. Keep shared files such as changelogs with one coordinator. Do not duplicate the worker's investigation in the parent.
- Before creating or resuming a persistent task ledger, read the ledger protocol. Inspect actual schema and rows, reuse stable owned identities, and preserve existing progress. A plan alone does not require a database. Never recreate runtime-owned tables or ignore an incompatible existing task.
- Require a nonempty handoff: done/partial/blocked, changes and artifact paths, exact checks/results, and unresolved risks. Use completion notifications when available rather than polling; follow up with the known worker only for the same task. Preserve this checkpoint on pause and inspect state before resuming.
- Consolidate results, inspect the combined change, and run shared gates once after integration unless repository rules require intermediate gates. Do not treat successful worker checks as proof of integrated correctness.
Output
Return the ordered task list, safe parallel sets with exclusive ownership, and remaining dependency or coverage risks. Use a compact table when sufficient. Use the plan template for a requested durable plan; do not create an unrequested planning file.
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.

