planning-and-task-breakdown

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

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/jason23452/my-skill --skill planning-and-task-breakdown-jason23452
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/jason23452/my-skill/tree/main/flow/planning-and-task-breakdown
Command: npx skills add https://github.com/jason23452/my-skill --skill planning-and-task-breakdown-jason23452

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Large or vague features are hard to implement reliably in one pass. This Skill turns a spec or clear requirement into an ordered list of small, verifiable tasks with acceptance criteria, dependencies, and checkpoints, so implementation stays focused and reviewable. ## Core Features & Use Cases - Dependency-aware ordering: Maps what depends on what (schema, API, UI) and sequences tasks from foundation upward. - Vertical slicing: Splits work into end-to-end feature slices instead of horizontal layers, so every task delivers working, testable functionality. - Structured task format: Each task includes description, acceptance criteria, verification commands, dependencies, files touched, and size estimate (XS to XL). - Use Case: Given a spec for a task-management app, produce tasks/plan.md and tasks/todo.md with phased tasks like "user can register" and "user can log in", each with test commands and checkpoints for human review. ## Quick Start Ask the agent to read the feature spec and produce an implementation plan with a task breakdown saved to tasks/plan.md and tasks/todo.md before writing any code.

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 working feature path end to end. Give every task acceptance criteria, verification commands, and a size estimate, and split anything larger than about five files.

What is vertical slicing in task planning?▼

Vertical slicing means each task completes a full feature path across schema, API, and UI, rather than building one entire layer at a time. Each slice stays testable and keeps the system working after every task.

How big should an implementation task be for an AI agent?▼

Aim for small to medium tasks touching one to five files, completable in a single focused session. Tasks needing more than about five files, two hours, or three acceptance criteria bullets should be split further.

When should I skip writing a task breakdown?▼

Skip it for single-file changes with clear scope, or when the spec already defines well-formed tasks. Planning adds the most value when work is large, ambiguous, parallelized, or has unclear ordering.

Which tasks can run in parallel and which cannot?▼

Independent feature slices, tests for finished features, and documentation can run in parallel. Database migrations, shared state changes, and dependency chains must run sequentially, and shared API contracts should be defined before parallel work begins.