planning-and-task-breakdown

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or vague work items cause agents and developers to produce tangled, incomplete implementations. This Skill turns a spec or clear 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 (schema, API, UI) so implementation order follows the dependency graph bottom-up. - Vertical Slicing: Structures tasks as complete feature slices (schema + API + UI) instead of horizontal layers, so every task delivers working functionality. - Task Sizing & Checkpoints: Provides sizing guidelines (XS to XL), a plan document template, and verification checkpoints between phases. - Use Case: Given a spec for a new expense-tracking feature, produce a phased task list where each task has acceptance criteria, verification commands, file estimates, and a human review checkpoint before implementation begins. ## Quick Start Ask the agent to read the feature spec and produce an implementation plan with ordered tasks, acceptance criteria, and checkpoints 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 implementable tasks?

Map the dependency graph first, then slice vertically so each task delivers one complete feature path across schema, API, and UI. Give every task acceptance criteria, verification steps, and a size estimate of five files or fewer.

What is vertical slicing in task breakdown?

Vertical slicing builds one complete feature path at a time, such as 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 a task be broken down further?

Break a task down when it exceeds one focused session, needs more than three acceptance criteria bullets, touches two independent subsystems, or its title contains the word and. Tasks sized L or larger should always be split.

When should I not use a formal task breakdown?

Skip formal planning for single-file changes with obvious scope, or when the spec already contains well-defined tasks. The planning process targets work that is large, vague, parallelizable, 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, and shared API contracts should be defined first.