planning-and-task-breakdown

Decomposes specifications into ordered, verifiable implementation tasks with acceptance criteria.

Updated May 13, 2026
One-click install
npx skills add https://github.com/sapatamuku-creator/mastersapatamuku --skill planning-and-task-breakdown-sapatamuku-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/sapatamuku-creator/mastersapatamuku/tree/main/releases/v2.7/.agents/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/sapatamuku-creator/mastersapatamuku --skill planning-and-task-breakdown-sapatamuku-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or vague work items cause agents and developers to start coding without direction, producing tangled implementations and missed requirements. This Skill turns a spec into an ordered set of small, verifiable tasks with explicit acceptance criteria, dependencies, and checkpoints. ## Core Features & Use Cases - Dependency Mapping: Builds a dependency graph of components so implementation order follows foundations first. - Vertical Slicing: Splits work into complete feature slices (schema + API + UI) instead of horizontal layers, so every task delivers testable functionality. - Structured Task Templates: Each task includes acceptance criteria, verification commands, dependencies, files touched, and size estimates, with checkpoints between phases. - Use Case: Given a spec for a task-management app, produce a plan document at tasks/plan.md and a checklist at tasks/todo.md covering registration, login, and task creation as separate verifiable slices. ## Quick Start Break this feature spec into an ordered task list with acceptance criteria and save the plan to tasks/plan.md.

Frequently Asked Questions about planning-and-task-breakdown

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break a large feature spec into implementable tasks?▼

Map the dependency graph first, then slice vertically so each task delivers one complete feature path across schema, API, and UI. Write each task with acceptance criteria, verification steps, dependencies, and a size estimate of small or medium.

What is vertical slicing in task breakdown?▼

Vertical slicing builds one complete feature path at a time, such as user registration covering schema, API, and UI together. It contrasts with horizontal slicing, which builds all of one layer before the next and delays testable functionality.

How big should a task be for an AI coding agent?▼

Tasks should be small (1-2 files) or medium (3-5 files), completable in one focused session. Anything touching 5 or more files or spanning two subsystems should be broken down further.

When should I skip formal task breakdown?▼

Skip it for single-file changes with obvious scope or when the spec already contains well-defined tasks. Planning adds value when work is large, vague, parallelized, or has unclear implementation order.

Which tasks can run in parallel across multiple agents?▼

Independent feature slices, tests for already-implemented features, and documentation are safe to parallelize. Database migrations, shared state changes, and dependency chains must remain sequential.