planning-and-task-breakdown

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

Updated May 5, 2026
One-click install
npx skills add https://github.com/UlaYuga/promo-preflight --skill planning-and-task-breakdown-ulayuga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/UlaYuga/promo-preflight/tree/main/.agents/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/UlaYuga/promo-preflight --skill planning-and-task-breakdown-ulayuga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or vague development tasks often lead to tangled implementations, missed dependencies, and rework. This Skill turns a spec or set of requirements into a written plan of small, verifiable tasks with explicit acceptance criteria, so work can be executed, tested, and reviewed reliably. ## 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 rather than horizontal layers, so each task delivers working, testable functionality. - Task Templates & Checkpoints: Provides a task format with acceptance criteria, verification steps, file estimates, and phase checkpoints for human review. - Use Case: Given a spec for a new user registration feature, produce a phased plan where each task (schema, endpoint, UI) has testable acceptance criteria and a checkpoint confirms the end-to-end flow works before proceeding. ## Quick Start Ask the agent to read the 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 smaller tasks?▼

Map the dependency graph first, then slice vertically so each task delivers one complete feature path across schema, API, and UI. Each task should have acceptance criteria, verification steps, and touch no more than about five files.

What is vertical slicing in task planning?▼

Vertical slicing builds one complete feature path at a time, such as registration covering schema, API, and UI together, instead of building all of one layer first. Each slice produces working, testable functionality.

How big should a single implementation task be?▼

Tasks should be small or medium, roughly one to five files, completable in a single focused session. If a task touches more than five files, spans two subsystems, or needs more than three acceptance criteria bullets, break it down further.

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 adds the most value for multi-component features, unclear implementation order, or parallel work.

Can multiple agents work on a task plan in parallel?▼

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 first.