breakdown

Decompose requirements documents into prioritized executable tasks with dependencies.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/mitchdowd/skills --skill breakdown-mitchdowd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breakdown
Source: https://github.com/mitchdowd/skills/tree/main/breakdown
Command: npx skills add https://github.com/mitchdowd/skills --skill breakdown-mitchdowd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down a requirements document into a structured set of executable tasks, enabling faster planning and delivery.

Core Features & Use Cases

  • Clear task boundaries: Convert vague requirements into discrete tasks with defined scope.
  • Dependency-aware planning: Identify task order and blockers to support sprint planning.
  • Multi-tool readiness: Create tasks suitable for Jira, GitHub Issues, or other trackers, with consistent acceptance criteria.
  • Use Case: Given a product spec, generate a task list that a team can implement in 2-week sprints.

Quick Start

Provide a requirements document and have the tool generate a prioritized list of executable tasks for assignment.

Frequently Asked Questions about breakdown

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

FAQPage Schema
How do I break down a product requirements document into actionable tasks for sprint planning?

To break down a product requirements document, you provide the specification to generate a prioritized list of executable tasks. Each task is structured as a thin vertical slice with defined acceptance criteria, clear boundaries, and identified blockers to support 2-week sprint planning.

Can I create Jira tickets or GitHub Issues directly from a requirements document?

You can create tasks suitable for Jira, GitHub Issues, or other trackers from a requirements document. The breakdown applies across these platforms to ensure consistent task boundaries and dependencies for project planning.

What is a thin vertical slice in agile task breakdown and why use it?

A thin vertical slice in agile task breakdown is an executable task with defined scope and acceptance criteria that delivers independent value. Using this approach ensures clear task boundaries and helps identify blockers, enabling faster planning and delivery.

Does task breakdown include testing and deployment steps for the generated tasks?

Task breakdown explicitly excludes testing or deployment steps from the generated tasks. It focuses solely on decomposing requirements into executable development tasks with clear boundaries and dependencies.

How do I identify task dependencies and blockers when decomposing project requirements?

To identify task dependencies and blockers, the breakdown process analyzes the requirements document and structures the output as a prioritized list. This dependency-aware planning maps task order and blockers to support sprint planning and project execution.