skills.rest
douglance
douglanceCOMMUNITY
Explore all skills by this author →
GitHub

planning-and-task-breakdown

Breaks specifications into ordered milestones, vertical-slice tasks, and atomic commits.

4|Updated Jun 19, 2026
Search Tags:#planning#task breakdown#implementation plan#milestones#dependency graph#atomic commits#vertical slicing
One-click install
npx skills add https://github.com/douglance/sdlc-plugin --skill planning-and-task-breakdown-douglance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/douglance/sdlc-plugin/tree/main/.rulesync/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/douglance/sdlc-plugin --skill planning-and-task-breakdown-douglance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an accepted specification into an implementable plan is hard: tasks end up too large, dependencies are unclear, and work cannot be parallelized or verified. This Skill converts specs into a structured plan of milestones, vertical-slice tasks with acceptance criteria, and atomic commits. ## Core Features & Use Cases - Dependency-graph planning: Maps component dependencies (schema, API, UI) and orders implementation bottom-up so foundations are built first. - Vertical slicing: Splits work into complete feature slices across all layers rather than horizontal layer-by-layer phases, with task sizing guidelines from XS to L. - Structured plan template: Produces a plan document with architecture decisions, prior-art evidence tables, checkpoints, risks, and open questions. - Use Case: Given a spec for a task-management app, generate a plan where Task 1 delivers account creation end-to-end (schema + API + UI), Task 2 delivers login, and each milestone closes with a verification checkpoint requiring human sign-off. ## Quick Start Ask the AI to break the attached feature specification into an ordered implementation plan with vertical-slice tasks, acceptance criteria, and atomic commits.

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 feature specification into implementable tasks?▼

Map the dependency graph first, then slice vertically so each task delivers one complete feature path through schema, API, and UI. Each task needs acceptance criteria, verification evidence, dependencies, and one or more atomic commits.

What is vertical slicing in task planning?▼

Vertical slicing means each task delivers a complete feature path through every layer at once, such as registration covering schema, API, and UI together. It avoids the all-database-then-all-API-then-all-UI approach so every task yields working, testable functionality.

When should a task be broken down further?▼

Split a task when it exceeds one focused session, needs more than three acceptance criteria bullets, touches two independent subsystems like auth and billing, or when its title contains the word 'and', which signals two tasks.

When should I not use a formal planning process?▼

Skip it for single-file changes with obvious scope or when the specification already contains well-defined tasks. The planning process targets specs that are too large or vague to implement directly.

Can implementation tasks be parallelized 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 features sharing an API contract need the contract defined first.

Related Skills

Explore More Software Engineering Skills→
jgaborjgabor
3

planera

Create structured PLAN.md files with tasks, constraints, and acceptance criteria.

Community
Advanced
HarmAalbersHarmAalbers
1

executing-plans

Executes written implementation plans in batches with review checkpoints between batches.

Community
Intermediate
kaptinlinkaptinlin
23

tdd-planning

Generate a TDD implementation plan from a PRD or design document.

Community
Advanced
Busboom-FooBusboom-Foo

oop

Apply small code changes directly to master with a deterministic test workflow.

Official
Intermediate