planning-and-task-breakdown

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or vaguely defined work items cause agents and developers to start coding without a plan, producing tangled implementations, missed dependencies, and rework. This Skill turns a spec or clear requirements into an ordered list of small, verifiable tasks with explicit acceptance criteria, dependencies, and checkpoints. ## Core Features & Use Cases - Dependency-aware task ordering: Maps the dependency graph (schema → API → UI) and orders tasks bottom-up so foundations are built first. - Vertical slicing guidance: Splits work into complete feature slices rather than horizontal layers, so every task delivers working, testable functionality. - Task sizing and checkpoints: Provides XS–XL sizing rules, a plan document template, and verification checkpoints after every 2-3 tasks. - Use Case: Given a spec for a new user-management feature, produce a phased plan where Task 1 delivers account creation end-to-end, Task 2 delivers login, each with acceptance criteria, verification commands, and a human review checkpoint before proceeding. ## Quick Start Ask the agent to read the spec for your feature and produce a phased implementation plan with sized 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 (schema plus API plus UI). Keep tasks at S or M size, roughly 1-5 files, with acceptance criteria and a verification step each.

What is vertical slicing in task breakdown?▼

Vertical slicing builds one complete feature path at a time instead of building all database, then all API, then all UI layers. Each slice, such as user registration, delivers working and testable functionality on its own.

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, parallelized, or has unclear implementation order.

Can tasks from a plan be parallelized across multiple agents?▼

Independent feature slices, tests for implemented features, and documentation are safe to parallelize. Database migrations, shared state changes, and dependency chains must stay sequential, and shared API contracts should be defined before parallel work begins.