planning-and-task-breakdown

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

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/JacobThree/zero-bloat-mcp-stack --skill planning-and-task-breakdown-jacobthree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/JacobThree/zero-bloat-mcp-stack/tree/main/ai_blueprints/agent-skills/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/JacobThree/zero-bloat-mcp-stack --skill planning-and-task-breakdown-jacobthree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or vague work items cause AI agents and developers to produce tangled, incomplete implementations. This Skill turns a spec or set of requirements into a written plan of small, verifiable tasks with explicit acceptance criteria, dependencies, and checkpoints. ## Core Features & Use Cases - Dependency Mapping: Identifies what depends on what and orders implementation bottom-up so foundations are built first. - Vertical Slicing: Structures tasks as complete feature slices (schema + API + UI) rather than horizontal layers, so every task delivers working functionality. - Task Templates & Sizing: Provides a task format with acceptance criteria, verification steps, and file estimates, plus sizing rules (XS through XL) that force oversized tasks to be split. - Use Case: You have a spec for a new task-management feature. Use this Skill to produce a phased plan document with ordered tasks, checkpoints after every 2-3 tasks, and a risk register before any code is written. ## Quick Start Ask the agent to read the feature spec and produce an implementation plan broken into small tasks with acceptance criteria, dependencies, and verification checkpoints.

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 into smaller tasks?▼

Map the dependency graph first, then slice vertically so each task delivers one complete feature path across schema, API, and UI. Keep tasks to 1-5 files with acceptance criteria you can state in three bullet points or fewer.

What is vertical slicing in task planning?▼

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 working functionality.

When should I not write a task breakdown plan?▼

Skip formal planning for single-file changes with obvious scope, or when the spec already contains well-defined tasks. Planning overhead only pays off when work is large, vague, or involves multiple components.

How big should a single implementation task be?▼

Aim for small tasks touching 1-2 files or medium tasks touching 3-5 files, completable in one focused session. Anything touching 5 or more files, or whose title contains the word 'and', should be split further.

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, and shared API contracts should be defined before parallel work begins.