Planning and Task Breakdown Skill for Muse
Break big builds into small, verifiable, shippable tasks
- What
- Break big builds into small, verifiable, shippable tasks
- Cost
- Free
- Needs
- a spec or clear requirements to break down; nothing else — no API keys, no tools. Works best when a task feels too large to start or parallel work is on the table.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
The difference between an agent that finishes work reliably and one that produces a tangled mess: it turns a spec or clear requirements into small, verifiable tasks with explicit acceptance criteria. The method has five steps: enter read-only plan mode before writing any code; map the dependency graph (build foundations first, bottom-up); slice vertically so each task delivers one complete working feature path instead of a horizontal layer of everything; write tasks with a fixed structure (acceptance criteria, verification step, dependencies, files touched, XS-to-XL sizing); then order them with checkpoints every 2-3 tasks and high-risk work early. Output conventions are fixed too: plan in `tasks/plan.md`, task list in `tasks/todo.md` (or an external tracker like GitHub Issues, Jira, or Linear when the project designates one) — and the skill's hard rule is to never overwrite an incomplete plan for different work without asking first. Includes sizing guidelines, parallelization rules for multi-agent work, a "Common Rationalizations" table ("planning is overhead" vs "planning is the task"), and red flags such as tasks without acceptance criteria. Discovered via skills.sh. Honest note: it assumes you already have a spec or clear requirements — it tells you when NOT to use it (single-file changes with obvious scope), and it plans implementation only, not product discovery or requirement gathering. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Curated by Skill Harbor — free, open-source skill (MIT) by @addyosmani.
Version:
Quick answer
Planning and Task Breakdown Skill for Muse is a free Muse skill that turns a spec or clear requirements into small, verifiable tasks with explicit acceptance criteria, so builds finish reliably instead of tangling. It enters read-only plan mode before coding, maps dependencies, slices vertically so each task delivers one working feature path, and writes tasks with verification steps.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 1401c8bStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a spec or clear requirements to break down; nothing else — no API keys, no tools. Works best when a task feels too large to start or parallel work is on the table. Install "Planning and Task Breakdown Skill for Muse" for me. Decomposes a spec or clear requirements into small, verifiable tasks: read-only plan mode, dependency-graph mapping, vertical slicing, structured task writing (acceptance criteria, verification, dependencies, XS-to-XL sizing), checkpoints every 2-3 tasks, output conventions (tasks/plan.md + tasks/todo.md or an external tracker), and a hard rule against overwriting someone else's incomplete plan. Repository: https://raw.githubusercontent.com/addyosmani/agent-skills/1401c8b8030e023baeebb31781a6653fe8e93026/skills/planning-and-task-breakdown/SKILL.md Pinned version: install the code at commit 1401c8b8030e023baeebb31781a6653fe8e93026 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files: references/) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "planning-and-task-breakdown". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. hand it the spec or requirements to break down). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 1401c8b · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.