addy-planning-and-task-breakdown

Break down specs into actionable tasks with acceptance criteria and dependencies.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/japurcell/skills --skill addy-planning-and-task-breakdown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: addy-planning-and-task-breakdown
Source: https://github.com/japurcell/skills/tree/main/skills/addy-planning-and-task-breakdown
Command: npx skills add https://github.com/japurcell/skills --skill addy-planning-and-task-breakdown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose large work into small, verifiable tasks with explicit acceptance criteria to reduce ambiguity and speed up delivery.

Core Features & Use Cases

  • Task slicing and vertical delivery: break a feature into end-to-end task slices.
  • Dependency mapping and sequencing: identify prerequisites and arrange tasks accordingly.
  • Checkpoints and verification: insert checkpoints to ensure steady progress and quality.

Quick Start

Create a concise implementation plan by breaking the spec into actionable tasks with acceptance criteria and checkpoints.

Frequently Asked Questions about addy-planning-and-task-breakdown

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down a project spec into actionable tasks?

To break down a project spec into actionable tasks, you slice the work into end-to-end vertical delivery blocks. Each task block requires explicit acceptance criteria, dependency mapping, and verification steps to reduce ambiguity and speed up delivery.

What is vertical task slicing in feature development?

Vertical task slicing in feature development is the process of breaking a large feature into small, end-to-end task slices. This technique ensures each slice delivers independent value and includes specific acceptance criteria for reliable execution.

How do I map dependencies and sequence tasks for parallel work?

You map dependencies and sequence tasks by identifying prerequisites within the work breakdown and arranging tasks accordingly. This dependency graph arrangement identifies parallel work opportunities and ensures correct execution sequencing.

When do I need to add checkpoints to a project plan?

You need to add checkpoints to a project plan when managing complex initiatives that require steady progress and quality assurance. Checkpoints act as verification steps inserted between task blocks to ensure reliable delivery.

Does this task breakdown approach work for complex initiatives with parallel work?

Yes, this task breakdown approach is designed for complex initiatives with dependencies and parallel work. It applies to project planning and feature development by requiring clearly defined task blocks with explicit acceptance criteria and verification steps.