breakdown
/breakdown
Use when a feature with a spec and a plan needs its ordered task list: \"break this into tasks\", \"make the task list\", \"what are the steps to build this?\", \"generate tasks.md\", a feature folder with plan.md and no tasks.md, or a task list made stale by a spec or plan change. Not for a feature with no plan (that's `blueprint`), not for one session's to-do list.
- Author
- mehrad-dm ↗
- Repository
- mastermind ↗
- Licence
- MIT
- Last repository change
- 08.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 08.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when a feature with a spec and a plan needs its ordered task list: \"break this into tasks\", \"make the task list\", \"what are the steps to build this?\", \"generate tasks.md\", a feature folder with plan.md and no tasks.md, or a task list made stale by a spec or plan change. Not for a feature with no plan (that's `blueprint`), not for one session's to-do list.
Triggers from the description
Original author description
Use when a feature with a spec and a plan needs its ordered task list: \"break this into tasks\", \"make the task list\", \"what are the steps to build this?\", \"generate tasks.md\", a feature folder with plan.md and no tasks.md, or a task list made stale by a spec or plan change. Not for a feature with no plan (that's `blueprint`), not for one session's to-do list.
How it works
- Read first
- The task line
- The phases
- Rules
- Gotchas
- Report
SKILL.md preview
--- name: breakdown description: "Use when a feature with a spec and a plan needs its ordered task list: \"break this into tasks\", \"make the task list\", \"what are the steps to build this?\", \"generate tasks.md\", a feature folder with plan.md and no tasks.md, or a task list made stale by a spec or plan change. Not for a feature with no plan (that's `blueprint`), not for one session's to-do list." --- # MasterMind: Breakdown `tasks.md` is the build order: small enough that each task is checkable, ordered so each user story ships alone. Layout and IDs: `~/.mastermind/engineering/core/spec-driven.md`. Input: **$ARGUMENTS**. ## Read first `spec.md` for the stories and their priorities, `plan.md` for paths and structure, then `data-model.md`, `contracts/`, `research.md` and `quickstart.md` where they exist. Use `specs/.templates/tasks.md` if present, else [`template.md`](template.md). ## The task line ```text - [ ] T014 [P] [US1] Add the export button to src/reports/ReportHeader.tsx (US1/AC1, FR-002) ``` - `- [ ]` then a `T###` ID in execution order. IDs are never reused or renumbered. - `[P]` only when it touches different files from every unfinished task before it. - `[US#]` on every task inside a story phase, and on no other. - The exact file path, and the spec IDs it serves in parentheses. ## The phases 1. **Setup**: what the project needs before anything else, such as dependencies, config and env vars. 2. **Foundation**: what every story needs and no story can deliver alone. Keep it small; most work belongs to a story. 3. **One phase per user story, in priority order.** Each is a vertical slice: its models, logic, interfaces and wiring, ending in a **checkpoint** that runs the story's independent test. 4. **Polish**: cross-cutting work that touches several stories. Delete a phase with no tasks. Never write a heading over "None". Refactoring the code needs before a story can land goes first, as its own tasks in Foundation. A change too wide for one slice, such as renaming a column every story reads, is sequenced expand, migrate, contract (`deprecate`), never forced into a story. Within a story: tests first when they are required, then data, then logic, then the surface, then the wiring that connects them. ## Rules - **Tests are tasks only when required.** Required means the constitution demands them, the spec asks for them, or the user said so. Otherwise `qa` verifies, and tests are offered after the build. - **Quote the constraint.** A field with a length limit, an enum or a validation rule from `data-model.md` has that rule copied into its task, so it is not left to memory at build time. - **Every requirement gets a task.** Before writing the file, check each `FR-###` and each acceptance criterion maps to at least one task. List any that do not in your report. - **A task that needs "and" is two tasks.** One task, one change, one way to tell it worked. ## Gotchas - **Horizontal phases are the failure this prevents.** "All models, then all services, then all UI" hides every integration bug until the end. Group by story, never by layer. - **Do not plan here.** A task that introduces a library, file or pattern the plan does not mention means the plan is incomplete. Fix `plan.md`, then the tasks. - **Regenerating loses progress.** When a `tasks.md` with ticked boxes exists, add and amend tasks; never rewrite the file from scratch. ## Report The task count per phase, the parallel opportunities, the requirements with no task, and the next step: `analyze` before building a feature that touches money, auth or data, else `build`. Set the spec's status to `tasked`. Then run `mastermind next` and end with the step it names, so the user sees where the feature stands.
Files in this package (3)
- ABOUT.md 2 KB
- SKILL.md 4 KB
- template.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · mehrad-dm/mastermind | 100 | MIT |
| userKael/rastro | 100 | MIT |
| lamngockhuong/aiteamkit | 100 | MIT |
| artemnovitckii/claude-animation-skills | 100 | MIT |
| mrlemoos/galicia | 81 | MIT |
Database snapshot: 13.11.2026 · package version bdc91ffb3552 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100planning-and-task-breakdown
Decompose specs into small, ordered tasks with acceptance criteria and verification steps. Use when you have requirements and need an implementable plan or task list. Triggers: "break down tasks", "implementation plan", "task breakdown", "plan mode". - 100blueprint
Use when a written feature spec needs its technical plan: \"plan this spec\", \"how should we build this spec?\", \"make the technical plan for this feature\", a spec in specs/ with no plan.md yet, or a plan that a spec or constitution change has made stale. Not for a feature… - 100work-breakdown
Splits a spec into an ordered list of tasks, each with a single verifiable outcome, an assigned tier, and a delegation brief. Use when a spec exists but there is no plan, when work must be divided across agents or people, or when a task is too large to verify in one step.… - 100brief-to-tasks
Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown". - 100spec-to-todo
Generate a TODO task list from a design specification. Reads a spec file from Specs/, explores the codebase to identify what's already implemented vs. what remains, and produces a markdown TODO file with checkboxes in TODO/. Use when asked to: "create a task list from a spec",… - 100planning-and-task-breakdown
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.