planning-and-task-breakdown

Break down development specifications into ordered, verifiable tasks with acceptance criteria.

1|Updated Jan 28, 2025
One-click install
npx skills add https://github.com/josuenavarroaguado/josuenavarroaguado.github.io --skill planning-and-task-breakdown-josuenavarroaguado
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/josuenavarroaguado/josuenavarroaguado.github.io/tree/main/.github/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/josuenavarroaguado/josuenavarroaguado.github.io --skill planning-and-task-breakdown-josuenavarroaguado

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decomposes large or vague work into small, ordered, verifiable tasks so implementations are testable, parallelizable, and leave the system in a working state after each step.

Core Features & Use Cases

  • Dependency mapping: Identify the foundation layers and map what depends on what to determine build order.
  • Vertical slicing: Create end-to-end feature slices so each task delivers a working outcome.
  • Task templates: Produce tasks with descriptions, explicit acceptance criteria, verification steps, probable files touched, declared dependencies, and estimated scope.
  • Parallelization & checkpoints: Highlight safe parallel work and insert verification checkpoints after small groups of tasks.
  • Use Case: Turn a feature spec (e.g., user registration flow) into a prioritized list of S/M-sized tasks with acceptance criteria and checkpoints for review.

Quick Start

Create an implementation plan for the "user registration" feature and break it into numbered tasks with acceptance criteria, verification steps, dependencies, files likely touched, 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
What is vertical slicing in software task breakdown and when should I use it?

Task estimation assigns an estimated scope, typically S/M-sized, to each decomposed feature slice. This sizing helps determine build order, map dependencies for parallelization, and insert verification checkpoints after small groups of tasks to keep the system in a working state.

How do I map dependencies and parallelize work in an implementation plan?

Vertical slicing applies to software features, API endpoints, data migrations, and multi-team projects. It creates end-to-end feature slices for each task, ensuring that even during complex migrations or parallel development, the system remains in a working state after each step.

When should I not use vertical slicing for task breakdown?

Dependency mapping identifies foundation layers and maps what depends on what to determine build order. The plan highlights safe parallel work opportunities and inserts verification checkpoints after small groups of tasks to manage the workflow effectively.

When should I avoid vertical slicing for task breakdown?

Vertical slicing is designed for large, unclear, or parallelizable work needing ordered, verifiable tasks. If your work item is already a small, clear, single-step task, decomposing it further into vertical slices with acceptance criteria and checkpoints adds unnecessary overhead.