skills.rest
echoVic
echoVicCOMMUNITY
Explore all skills by this author →
Website𝕏@echo_vicGitHub

scrum-master/task-breakdown

Breaks requirements into executable development tasks using WBS and SMART principles.

553|50|Updated Jan 10, 2026
Search Tags:#task breakdown#effort estimation#SCRUM#wbs#smart criteria#AGILE#Sprint Planning
One-click install
npx skills add https://github.com/echoVic/boss-skill --skill scrum-master-task-breakdown
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scrum-master/task-breakdown
Source: https://github.com/echoVic/boss-skill/tree/main/skill/skills/scrum-master/task-breakdown
Command: npx skills add https://github.com/echoVic/boss-skill --skill scrum-master-task-breakdown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large, vague requirements are hard to estimate, assign, and track. This Skill provides a structured methodology for decomposing requirements into concrete, estimable development tasks that a team can execute.

Core Features & Use Cases

  • WBS-Based Decomposition: Applies Work Breakdown Structure with SMART criteria (Specific, Measurable, Achievable, Relevant, Time-bound) to every task.
  • Granularity Guidelines: Defines task sizing tiers (2-4 hours, 1-2 days, 3-5 days) with a rule that no task exceeds 2 days without further splitting.
  • Dependency Modeling: Distinguishes serial dependencies, parallel tasks, and blocking tasks so scheduling prioritizes unblockers.
  • Use Case: When planning a sprint, feed a feature requirement to the scrum-master agent and receive a task list with size estimates and dependency ordering ready for assignment.

Quick Start

Ask the scrum-master agent to break down the current feature requirement into development tasks with effort estimates and dependencies.

Frequently Asked Questions about scrum-master/task-breakdown

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

FAQPage Schema
How do I break down a feature requirement into development tasks?▼

Apply the WBS method: decompose the requirement into smaller units until each task satisfies the SMART criteria. Tasks should be specific, measurable, achievable, relevant, and time-bound, with none exceeding two days of work.

What is the right task granularity for sprint planning?▼

Small tasks take 2-4 hours for single function points, medium tasks take 1-2 days for complete modules, and large tasks of 3-5 days should be split further. The guiding rule is that no task should exceed two days.

How do I handle dependencies between development tasks?▼

Classify each relationship as serial (B waits for A), parallel (A and B run simultaneously), or blocking. Prioritize blocking tasks first since they gate the progress of other work in the pipeline.

When should a task be split into smaller tasks?▼

Split any task estimated at more than two days, or any task that fails the SMART criteria such as lacking a measurable outcome. Oversized tasks hide risk and make progress tracking unreliable.

Can this task breakdown method be used outside the Boss agent workflow?▼

The methodology is agent-invocable within the Boss scrum-master role and is not user-invocable directly. The underlying WBS and SMART principles, however, are general practices applicable to any sprint planning process.

Related Skills

Explore More Product & Management Skills→
codetail-aicodetail-ai

pm

Creates structured PRDs with user stories, acceptance criteria, and scope boundaries.

Official
Advanced
maxwalser001-delmaxwalser001-del

feature-lifecycle

Coordinate end-to-end feature delivery across seven gated phases.

Community
Advanced
omeragaakbasomeragaakbas

sprint-plan

Estimate team capacity and select committed backlog stories for a sprint.

Community
Intermediate
JaviMontanoJaviMontano

metodologia-workshop-facilitator

Plan and run collaborative discovery workshops with structured facilitation guides.

Community
Advanced