planning-and-task-breakdown

Break specifications into ordered tasks with acceptance criteria and dependencies.

9|Updated Apr 3, 2026

Search Tags:#planning #estimation #acceptance-criteria #task-breakdown #dependency-graph #vertical-slicing

Ready to run

npx skills add https://github.com/klh/speedy-claude --skill planning-and-task-breakdown-klh

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks large, vague, or multi-part work into small, ordered, verifiable tasks so implementation proceeds predictably and can be parallelized when appropriate. It prevents unfinished integration work, unclear scope, and undone verification steps by making acceptance criteria and checkpoints explicit.

Core Features & Use Cases

Structured decomposition: Converts a specification into discrete tasks with titles, short descriptions, and estimated scope.
Dependency mapping: Identifies and orders tasks according to a dependency graph so foundational work comes first.
Verification-first tasks: Adds acceptance criteria and verification steps to ensure each task leaves the system in a working state.
Use case: Planning a new feature where database schema, API, and UI must be coordinated and parallelized safely.

Quick Start

Ask the skill to decompose the provided specification into an ordered task list with acceptance criteria, verification steps, dependencies, and estimated scope.

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 verifiable tasks?▼

To break a feature specification into verifiable tasks, decompose the work into discrete items with titles, descriptions, acceptance criteria, verification steps, dependencies, and estimated scope. This structured decomposition prevents unclear scope and ensures implementation proceeds predictably.

What is vertical slicing in task breakdown?▼

Vertical slicing in task breakdown is the process of splitting features so that each task leaves the system in a working state. It ensures database schema, API, and UI work are coordinated and can be parallelized safely without unfinished integration work.

How do I map dependencies when planning software implementation?▼

Mapping dependencies when planning software implementation involves identifying and ordering tasks according to a dependency graph. This ensures foundational work comes first, allowing parallelization scenarios to proceed safely once explicit dependencies are mapped.

How do I add acceptance criteria and verification steps to a task list?▼

Adding acceptance criteria and verification steps to a task list requires making checkpoints explicit for each decomposed task. This verification-first approach ensures each task leaves the system in a working state and prevents undone verification steps during implementation.

Can I parallelize tasks across database, API, and UI layers safely?▼

Yes, you can parallelize tasks across database, API, and UI layers safely by applying vertical slicing and mapping dependencies. This approach coordinates foundational work and produces an ordered task list that prevents unfinished integration work.

Best way to estimate scope for multi-part software features?▼

The best way to estimate scope for multi-part software features is to decompose vague work into small, ordered, verifiable tasks. Converting specifications into discrete tasks with explicit acceptance criteria makes scope estimation predictable and actionable.