skills.rest
ankaboot-source
ankaboot-sourceOFFICIAL
Explore all skills by this author →
WebsiteGitHub

planning-and-task-breakdown

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

2|Updated Jul 25, 2026
Search Tags:#planning#task breakdown#acceptance criteria#checkpoints#dependency graph#vertical slicing#spec decomposition
One-click install
npx skills add https://github.com/ankaboot-source/boucle --skill planning-and-task-breakdown-ankaboot-source
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/ankaboot-source/boucle/tree/main/.jcode/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/ankaboot-source/boucle --skill planning-and-task-breakdown-ankaboot-source

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Large or vague work items cause agents and developers to produce tangled, incomplete implementations. 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-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 testable functionality. - Task sizing and checkpoints: Enforces XS-to-L sizing rules, flags XL tasks for further breakdown, and inserts verification checkpoints every 2-3 tasks. - Use Case: Given a spec for a task-management app, produce tasks/plan.md and tasks/todo.md containing phased tasks like "user can create an account" with acceptance criteria, verification steps, and file estimates. ## Quick Start Ask the agent to read the feature spec and break it into an ordered task list with acceptance criteria saved to tasks/plan.md and tasks/todo.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 spec into implementable tasks?▼

Read the spec in read-only mode, map the dependency graph between components, then slice vertically so each task delivers one complete feature path. Write each task with acceptance criteria, verification steps, dependencies, and an estimated file count.

What is vertical slicing in task breakdown?▼

Vertical slicing builds one complete feature path at a time, such as schema plus API plus UI for registration, instead of building all database, then all API, then all UI. Each slice delivers working, testable functionality.

How big should a single implementation task be?▼

Tasks should be Small (1-2 files) or Medium (3-5 files). Anything Large (5-8 files) or bigger should be broken down further, especially if it spans multiple subsystems or cannot be described in three acceptance criteria.

When should I not use a formal task breakdown?▼

Skip it for single-file changes with obvious scope, or when the spec already contains well-defined tasks. The planning step targets work that is too large, vague, or has unclear implementation order.

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 remain sequential.

Related Skills

Explore More Software Engineering Skills→
trydyddtrydydd

i-shape

Guide structured discovery interviews and convert insights into a design brief.

Community
Advanced
INNERJOINTINNERJOINT

ralph

Automate PRD-driven execution loops until all user stories pass verification.

Community
Advanced
giovannimnzgiovannimnz

gsd-verify-work

Evaluate phase acceptance criteria and definition of done to output READY or NEEDS_WORK status.

Community
Intermediate
jaxxstormjaxxstorm
4

openspec-explore

Guide early-stage idea exploration and requirement framing without executing code.

Community
Basic