skills.rest
nicorevo
nicorevoCOMMUNITY
Explore all skills by this author →
GitHub

planning-and-task-breakdown

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

Updated May 21, 2026
Search Tags:#planning#task breakdown#acceptance criteria#implementation plan#agile#dependency graph#vertical slicing
One-click install
npx skills add https://github.com/nicorevo/AI-SDLC-Template --skill planning-and-task-breakdown-nicorevo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/nicorevo/AI-SDLC-Template/tree/main/.opencode/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/nicorevo/AI-SDLC-Template --skill planning-and-task-breakdown-nicorevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or vague work items cause agents to produce tangled, unverifiable implementations. This Skill turns a spec or clear requirements into an ordered list of small, testable tasks with explicit acceptance criteria, dependencies, and checkpoints. ## Core Features & Use Cases - Vertical slicing: Breaks work into complete feature paths (schema + API + UI) instead of horizontal layers, so every task delivers working functionality. - Structured task format: Each task includes description, acceptance criteria, verification steps, dependencies, files touched, and size estimate (XS to XL). - Plan artifacts: Produces tasks/plan.md (implementation plan with phases, risks, and open questions) and tasks/todo.md (checklist task list) for downstream tooling. - Use Case: Given a spec for a task-management app, generate a phased plan where Task 1 is user registration end-to-end, Task 2 is login, and checkpoints verify tests and builds after every 2-3 tasks. ## Quick Start Break the attached spec into an ordered task list with acceptance criteria and save the plan to tasks/plan.md.

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, API, and UI together). Give every task acceptance criteria, verification steps, and a size estimate, keeping tasks to 1-5 files.

What is vertical slicing in task planning?▼

Vertical slicing builds one complete feature path at a time, such as user registration covering schema, API, and UI, instead of building all database, then all API, then all UI. Each slice leaves the system in a working, testable state.

When should a task be broken down further?▼

Break a task down when it exceeds one focused session, touches more than about five files, spans two independent subsystems, or its title contains 'and'. Tasks sized L or larger should be split into S or M tasks.

When should I skip formal task breakdown?▼

Skip it for single-file changes with obvious scope or when the spec already contains well-defined tasks. The planning process is designed for multi-component work where implementation order is not obvious.

How do I parallelize tasks across multiple agents?▼

Independent feature slices, tests for finished 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.

Related Skills

Explore More Software Engineering Skills→
ferdiangunawanferdiangunawan
6

plan

Convert validated research into a detailed implementation plan document.

Community
Advanced
astrosteveoastrosteveo

code

Enforce Test-Driven Development with failing tests, minimal code, and atomic commits.

Community
Advanced
sscciossccio

review

Review proposed plans for clarity, testability, and verification gaps.

Community
Basic
cubetribecubetribe
45

prototype-mode

Bypass production quality gates for disposable local prototyping experiments.

Community
Advanced