wv-decompose-work

Break down an epic into features and tasks with dependencies.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/AGM1968/weave --skill wv-decompose-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wv-decompose-work
Source: https://github.com/AGM1968/weave/tree/main/.claude/skills/wv-decompose-work
Command: npx skills add https://github.com/AGM1968/weave --skill wv-decompose-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down large initiatives into manageable features and tasks with clear dependencies to align teams and streamline execution.

Core Features & Use Cases

  • Feature-based decomposition: converts an epic into a structured set of features.
  • Task-level planning: breaks features into atomic tasks with expectations and acceptance criteria.
  • Dependency graph: establishes the sequence and blocking relationships for the work.

Quick Start

Provide a breakdown of the epic described in ARGUMENTS into features and tasks with clear dependencies.

Frequently Asked Questions about wv-decompose-work

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

FAQPage Schema
How do I decompose an epic into actionable tasks with dependencies?

To decompose an epic, you break it down into a structured set of features, then further into atomic tasks with acceptance criteria and explicit blocking relationships to form a dependency graph.

What is epic decomposition in an agile workflow?

Epic decomposition in an agile workflow is the process of breaking large initiatives across product, engineering, and operations into structured features and atomic tasks before work execution starts.

How do I generate a dependency graph for feature-based task planning?

You generate a dependency graph by identifying features within an epic, creating atomic tasks with expectations, and establishing the sequence and blocking relationships required for a graph-ready plan.

Can I use this for large initiatives across product and engineering teams?

Yes, this applies to large initiatives across product, engineering, and operations that require upfront decomposition to identify features and create atomic tasks with clear dependencies.

What is the best way to break down features into atomic tasks?

The best way to break down features into atomic tasks is to define expectations and acceptance criteria for each task while mapping their sequence and blocking relationships within the epic plan.

Do I need upfront decomposition before starting work on a large initiative?

Yes, large initiatives across product, engineering, and operations require upfront decomposition to align teams and streamline execution by identifying features and creating a graph-ready plan.