planning-and-task-breakdown

Decomposes specifications into ordered, verifiable tasks with acceptance criteria and checkpoints.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/CodeCrafterAdi2006/Ink-and-Code --skill planning-and-task-breakdown-codecrafteradi2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/CodeCrafterAdi2006/Ink-and-Code/tree/main/Skills/planning-and-task-breakdown
Command: npx skills add https://github.com/CodeCrafterAdi2006/Ink-and-Code --skill planning-and-task-breakdown-codecrafteradi2006

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, dependency ordering, and checkpoints. ## Core Features & Use Cases - Dependency Graph Mapping: Identifies what depends on what so foundations are built before dependent layers. - Vertical Slicing: Structures tasks as complete feature slices (schema + API + UI) instead of horizontal layers, so every task delivers working functionality. - Task Sizing Guidelines: Classifies tasks from XS to XL and forces breakdown of anything too large for a single focused session. - Standardized Outputs: Produces a plan document at tasks/plan.md and a checklist at tasks/todo.md for downstream tooling. - Use Case: Given a spec for a user authentication feature, generate an ordered task list covering registration, login, and session handling, each with acceptance criteria, verification commands, and checkpoints. ## Quick Start Ask the agent to read the feature spec and produce a task breakdown plan saved to tasks/plan.md and tasks/todo.md 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 implementable tasks?

Map the dependency graph first, then slice vertically so each task delivers one complete working feature path. 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 breakdown?

Vertical slicing builds one complete feature path at a time, covering schema, API, and UI together, instead of building all of one layer first. 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, needs more than three acceptance criteria bullets, touches multiple independent subsystems, or its title contains the word and. Tasks sized L or XL should always be split.

When should I not use a formal task breakdown process?

Skip it for single-file changes with obvious scope or when the spec already contains well-defined tasks. The planning overhead only pays off when work is large, vague, or needs coordination.

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.