task-breakdown

Decompose large development requests into 5-12 actionable micro-tasks for user approval.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill tackles the challenge of overwhelming, large development requests by automatically breaking them down into small, sequential, and easily implementable micro-tasks. It prevents scope creep and ensures a structured, efficient approach to coding, letting you focus on execution.

Core Features & Use Cases

  • Micro-task Generation: Divides large requests (e.g., new pages, complex flows, major refactors, API integrations) into 5-12 focused, actionable tasks.
  • Structured Planning: Each generated task includes a clear title, predicted files, and a brief objective, ensuring clarity and guiding the development process.
  • User Validation Loop: Presents the detailed plan to the user for approval or adjustment before any code is written, ensuring alignment and reducing rework.
  • Use Case: When a user requests a new "Habits" page, this Skill will generate a step-by-step plan, from defining data types to creating UI components and routing, ensuring a smooth, predictable development process.

Quick Start

I need to implement a new 'Timeline' feature. Can you use the task-breakdown skill to create a detailed plan of micro-tasks for me before I start coding?

Frequently Asked Questions about task-breakdown

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

FAQPage Schema
How do I break down a large development task into smaller steps?

Break down large requests by decomposing them into 5–12 focused micro-tasks, each with a clear title, target files, and objective achievable in under 15 minutes. This structured approach prevents scope creep and ensures efficient, sequential implementation before writing any code.

When should I use task breakdown for software development?

Use task breakdown when tackling new pages or features, complex flows like onboarding, major refactors, or external API integrations. It's most effective for requests that feel overwhelming, where structured planning reduces rework and clarifies execution order.

How do I plan a new feature like a page or workflow before coding?

Generate a detailed plan specifying each micro-task's title, predicted files, and brief objective. Present this plan to stakeholders for validation and adjustment before implementation begins, ensuring alignment and reducing scope misalignment.

Can task breakdown help with project planning and workflow automation?

Yes. Task breakdown applies to project planning by decomposing large requests into manageable steps and supports workflow automation by generating structured, sequential micro-tasks with clear dependencies and file scope for predictable execution.

What's the benefit of micro-tasks over tackling a large request all at once?

Micro-tasks limit scope per iteration, reduce cognitive load, prevent feature creep, and enable faster validation cycles. Each task is completable in under 15 minutes, making progress visible and recovery from mistakes simpler.