work-breakdown_skill

Overview

This skill breaks down features, enhancements, and requirements into small, actionable tasks with clear scope and acceptance criteria. It produces ordered, right-sized work items, identifies dependencies, and assigns responsibility so teams or agents can implement independently. The output focuses on implementability and testability.

How this skill works

I read the full requirement or feature description and identify affected system components. I split work into phases (architecture, implementation, testing, documentation), create discrete tasks that are completable in 2–8 hours, and attach clear acceptance criteria. I then order tasks by dependencies and validate coverage so nothing essential is left unaddressed.

When to use it

• Planning a new feature implementation
• Breaking an enhancement into execution-ready work
• Creating sprint or iteration task lists
• Organizing multi-agent or cross-team workflows
• Preparing handoffs between architects, implementers, and testers

Best practices

• Keep tasks 2–8 hours each; avoid multi-day work items
• Give each task explicit acceptance criteria and expected output
• Assign an appropriate owner or agent for each task
• Group related tasks into phases (architecture → implementation → testing → docs)
• Explicitly list dependencies and ordering to prevent blocking
• Validate that task set covers all requirements and edge cases

Example use cases

• Add OAuth-based user authentication split into design, implementation, tests, and docs
• Turn a high-level performance improvement requirement into measurable sub-tasks with benchmarks
• Create a rollout plan for a new API version with migration tasks and compatibility tests
• Prepare a sprint backlog from a product spec, with clear owners and acceptance for each item
• Decompose cross-service feature into service-level tasks, integration tests, and deployment steps