breakdown

Converts a Plan document into executable task files and Jira-ready summaries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breakdown helps transform a Plan doc into concrete, delta-ready tasks and Jira-ready artifacts that keep delivery aligned with strategy.

Core Features & Use Cases

  • Convert Plan milestones into task files with standardized naming conventions and templates.
  • Generate a Jira-ready breakdown summary to kick off work items and track dependencies.
  • Provide structured guidance for creating task content, dependencies, testing, and migration considerations.

Quick Start

Provide a Plan doc and have Breakdown generate all required task breakdown files and Jira artifacts.

Frequently Asked Questions about breakdown

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

FAQPage Schema
How do I turn a plan document into executable tasks for Jira?

To turn a plan document into executable tasks, you provide the plan to generate standardized task files with deterministic naming and a Jira-ready breakdown summary. This enforces source references and plan-to-task traceability for delivery alignment.

What is work breakdown structure automation for product initiatives?

Work breakdown structure automation translates product milestones into structured tasks, dependencies, and artifacts. It provides templates for task files and Jira summaries, ensuring plan-to-task traceability and standardized naming conventions.

Can I generate Jira summaries and task dependencies from a planning document?

Yes, you can generate Jira summaries and task dependencies directly from a planning document. The process creates structured guidance for task content, dependencies, testing, and migration considerations to kick off work items.

Do I need a structured plan doc to automate milestone task generation?

Yes, you need a structured plan doc to automate milestone task generation because the process relies on translating existing plan milestones into delta-ready tasks. Providing the plan doc is the required entry point for generating the breakdown.

What is the best way to ensure plan-to-task traceability during work breakdown?

The best way to ensure plan-to-task traceability is by enforcing deterministic naming conventions and source references when generating task files. This keeps the structured tasks aligned with the original product strategy.