planning-and-task-breakdown

Decompose complex project work into structured task plans with acceptance criteria.

6|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/farzanmrz/oparax-chirp --skill planning-and-task-breakdown-farzanmrz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/farzanmrz/oparax-chirp/tree/main/.claude/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/farzanmrz/oparax-chirp --skill planning-and-task-breakdown-farzanmrz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizes ambiguous or large tasks into a clear, ordered plan with explicit acceptance criteria to enable reliable delivery and measurement of progress.

Core Features & Use Cases

  • Pattern recognition: identifies dependencies, risks, and constraints to shape task sequences.
  • Vertical slicing: breaks work into end-to-end slices that deliver testable functionality.
  • Plan documentation: produces checklists, risk notes, and open questions to guide human review.

Quick Start

Provide the project spec and constraints and this skill will output a structured, task-by-task plan with acceptance criteria and checkpoints.

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 down a large project into actionable tasks with dependencies?

Project task breakdown decomposes large specs into structured, ordered plans by mapping dependencies and constraints. It organizes ambiguous work into clear sequences with explicit acceptance criteria to enable reliable delivery and measurable progress tracking.

What is vertical slicing in task breakdown and when do I need it?

Vertical slicing is a task breakdown method that splits work into end-to-end functional pieces delivering testable functionality. You need it when decomposing large tasks requiring modular breakdown to enable parallel work and incremental verification.

How do I create a project plan with checkpoints and acceptance criteria?

Create a project plan with checkpoints by providing your project spec and constraints to generate a task-by-task plan. This enforces explicit task acceptance criteria, verification steps, and checkpointing to ensure a reproducible implementation plan.

Can I use task breakdown planning for complex specs needing risk management?

Task breakdown planning suits complex specs by identifying dependencies, risks, and constraints to shape task sequences. It produces checklists, risk notes, and open questions that guide human review and enable reliable delivery.

What's the best way to map dependencies for parallel work in a project plan?

Map dependencies for parallel work by applying pattern recognition to identify task relationships and constraints within your project spec. This shapes an ordered task sequence that enables modular breakdown and parallel execution.

Why does my project plan lack measurable progress and reproducible implementation?

Your project plan lacks reproducible implementation when it omits explicit task acceptance criteria and verification steps. Enforcing checkpointing and documenting risk notes ensures measurable progress and reliable delivery.