Verified:GitHub

planning-and-task-breakdown

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

Updated May 19, 2026

Search Tags:#planning #task breakdown #acceptance criteria #implementation plan #agile #dependency graph #vertical slicing

Ready to run

npx skills add https://github.com/richardnguyen0715/agent-sharing --skill planning-and-task-breakdown-richardnguyen0715

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/richardnguyen0715/agent-sharing/tree/main/.github/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/richardnguyen0715/agent-sharing --skill planning-and-task-breakdown-richardnguyen0715

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or vague features are hard to implement reliably in one pass, leading to tangled code, missed edge cases, and rework. 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: Builds a dependency graph of components so implementation order follows foundations first. - Vertical Slicing: Splits work into complete feature slices (schema + API + UI) instead of horizontal layers, so every task delivers working functionality. - Structured Task Format: Each task includes description, acceptance criteria, verification commands, dependencies, files touched, and size estimates (XS to XL). - Use Case: Given a spec for a task-management app, produce a phased plan where Task 1 is user registration, Task 2 is login, and checkpoints verify tests pass and builds stay clean after each phase. ## Quick Start Ask the AI to break your feature spec into an ordered implementation plan with acceptance criteria and verification steps for each task.

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 working feature path such as schema plus API plus UI. Give every task acceptance criteria, verification steps, and a size estimate, and split anything larger than about five files.

What is vertical slicing in task planning?▼

Vertical slicing means building one complete feature path at a time, like user registration end to end, instead of building all the database, then all the API, then all the UI. Each slice produces working, testable 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 adds value when work is large, vague, parallelized, or has unclear implementation order.

How big should a single implementation task be?▼

Aim for small tasks touching one to two files or medium tasks touching three to five files. Anything estimated at five or more files, spanning multiple subsystems, or needing more than three acceptance criteria bullets should be broken down 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 stay sequential, and features sharing an API contract need the contract defined first.