break-down-task

Decompose oversized development tasks into PR-sized units with dependency chains.

3|Updated May 7, 2026
One-click install
npx skills add https://github.com/bestdan/workflow-skills --skill break-down-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: break-down-task
Source: https://github.com/bestdan/workflow-skills/tree/main/skills/break-down-task
Command: npx skills add https://github.com/bestdan/workflow-skills --skill break-down-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the bottleneck of oversized tasks that exceed the recommended size limit, preventing stalled development and ensuring that work remains manageable and reviewable.

Core Features & Use Cases

  • Automated Task Slicing: Identifies natural shear points in complex tasks to divide them into smaller, independent units of work.
  • Dependency Management: Automatically chains component tasks using block-dependency logic to ensure correct execution order.
  • Use Case: When a feature request is flagged as too large to fit in a single pull request, this skill breaks it down into logical steps like refactoring, interface definition, and implementation, each with its own task card.

Quick Start

Invoke the break-down-task skill to split the currently identified oversized task into smaller, manageable components.

Frequently Asked Questions about break-down-task

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

FAQPage Schema
How do I split oversized development tasks into PR-sized units?

Automating task slicing identifies natural shear points and dependency chains in oversized development tasks, dividing complex work into smaller, independent, PR-sized component units.

Why does task management stall when working with oversized pull request components?

Task management stalls when pull request components exceed recommended size limits, preventing manageable development and making code reviews difficult to process.

What is the best way to chain dependent refactoring tasks in a workflow?

The best way to chain dependent refactoring tasks is using block-dependency logic to sequence component tasks like interface definition and implementation, ensuring correct execution order.

Does task decomposition work with Linear and repo-pr integrations?

Yes, task decomposition works with Linear and repo-pr integrations by utilizing handler-specific logic to maintain a consistent task-loop pipeline within your repository.

Do I need a specific task format to automate task slicing?

You need to adhere to a canonical task format within your repository files to properly automate task slicing and maintain the task-loop pipeline.

What are the limitations when breaking down feature requests into smaller tasks?

Limitations when breaking down feature requests include ensuring each sliced component remains within defined complexity limits and strictly following the canonical task format to prevent pipeline errors.