work-breakdown

Splits requirements into independent vertical-slice work items spanning all technical layers.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/HACK-WU/skills --skill work-breakdown-hack-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-breakdown
Source: https://github.com/HACK-WU/skills/tree/main/skills/work-breakdown
Command: npx skills add https://github.com/HACK-WU/skills --skill work-breakdown-hack-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a finished requirement into an actionable implementation plan is hard: teams often split work horizontally by technical layer, creating tasks that cannot be independently built, tested, or verified. This Skill decomposes requirements into fully independent vertical slices that each cut through data, logic, interface, and output layers, so every work item can be developed in parallel and validated on its own. ## Core Features & Use Cases - Vertical Slice Decomposition: Splits requirements by user behavior, data entity, scenario, or complexity, ensuring each slice spans all technical layers end to end. - AFK/HITL Classification: Labels each work item as agent-completable (AFK) or requiring human decisions (HITL), preventing agents from attempting work that needs human judgment. - Independence Validation: Checks every slice pair for shared dependencies, flags strong dependencies for merging or re-splitting, and documents fallback plans for weak ones. - Use Case: After completing requirement mining for a user management feature, use this Skill to split it into independent slices like registration, login, and password reset, each ready to enter technical design separately and be developed in parallel. ## Quick Start Ask the AI to split this requirement into independent work items that can each be developed and verified separately.

Frequently Asked Questions about work-breakdown

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

FAQPage Schema
How do I break down a software requirement into independent tasks?

Split the requirement into vertical slices where each slice cuts through all technical layers (data, logic, interface, output) rather than splitting by layer. Each slice should be independently verifiable and free of strong dependencies on other slices.

What is a vertical slice in agile work breakdown?

A vertical slice is a work item that delivers end-to-end functionality across all technical layers, from interface entry to user-visible output. Unlike horizontal splits (database first, then API, then frontend), each vertical slice can be demonstrated and tested on its own.

When should work items be classified as HITL versus AFK?

Classify a work item as HITL when it requires architecture decisions, business judgment, design review, or external confirmations like third-party integration approval. Mark it AFK when an agent can complete it without any human decision-making.

What should I do when two work items have a strong dependency?

Strong dependencies, where one slice cannot start until another finishes, defeat the purpose of splitting. Merge the two slices into one, re-split along a different dimension to eliminate the dependency, or explicitly document the required execution order.

Does work-breakdown decide the technical design for each slice?

No, it only defines work boundaries and explicitly avoids prescribing implementation approaches. Each resulting slice is handed to a separate design skill (design-craft) for technical design, keeping decomposition and design as distinct phases.