break-down-request

name	Break Down Request
description	Decompose a V3 Request into specific, actionable WorkItems based on semantic understanding of the task.
version	1.0.0
category	task-management
skillType	claude-skill
assignableRoles	["orchestrator","team-leader","architect","product-manager","developer","backend-developer","frontend-developer","fullstack-dev"]
triggers	["break down request","decompose request","split request into tasks"]
tags	["v3","request","decomposition","work-items"]
execution	{"type":"script","script":{"file":"execute.sh","interpreter":"bash","timeoutMs":30000}}

Break Down Request

Decompose a V3 Request (L2 or L3) into specific, actionable WorkItems in the TaskPool. Use your LLM understanding to create meaningful task breakdowns -- do NOT use generic templates.

WHEN to use this skill

Call this skill after creating an L2+ Request via the create-request skill. The orchestrator should:

1. Analyze the user's actual request
2. Determine the specific steps needed
3. Call this skill with a tailored list of tasks

DO NOT use generic decomposition. Every breakdown should be specific to what the user asked for.

How to decompose

Think about the request like a senior engineer would:

• What are the concrete steps to accomplish this?
• What order should they happen in?
• Who is best suited for each step?
• Are there any review or validation steps needed?

Task Types

Type	When to use
delegate	Work that should be assigned to an agent for execution
check	Validation or verification step (tests pass, build succeeds)
notify	Inform someone of a status change or result
review	Code review, design review, or approval step

Parameters

Flag	Required	Description
--request-id	Yes	The Request ID to decompose (from create-request output)
--tasks	Yes	JSON array of task objects (use --file for complex JSON)

Task Object Structure

Each task in the --tasks array should have:

{
  "title": "Create team V3-QA-Team",
  "description": "Create a new QA team named V3-QA-Team with testing focus",
  "type"