From product-ops
Decompose a requirement into well-sequenced child items with structured metadata. Takes an epic and produces stories, or takes a story and produces subtasks. Each child includes YAML frontmatter compatible with GitHub Issues and Jira.
How this skill is triggered — by the user, by Claude, or both
Slash command
/product-ops:decompose-requirementThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Break a requirement into sequenced child items, each with structured metadata output.
Break a requirement into sequenced child items, each with structured metadata output.
$ARGUMENTS = title or description of the requirement to decompose.
Determine the decomposition level:
Use vertical slicing (mandatory) — each child delivers a thin, user-visible slice of functionality across all layers. Pick the best-fit strategy:
Explicitly avoid horizontal slicing (e.g., "build the database layer", "build the API", "build the UI") — these produce children with no standalone user value.
Order by priority, applying these criteria in order:
For each child, produce:
type, title, parent (set to the input requirement's title), labels, priority, size, status: draft, dependencies, acceptance_criteria- [ ] checkboxesThese are outlines, not full specifications. The user can run /write-story on individual items for full INVEST validation and detail.
Each child's markdown body MUST use ### headings in this order:
### User Story### Acceptance CriteriaOptional fields: omit entirely if empty. Never include blank bullets or placeholder text.
A summary table first, then individual child specs.
## Decomposition Summary
**Parent**: [input requirement title]
**Level**: epic → stories | story → subtasks
**Children**: N items
| # | Title | Type | Size | Depends On | Parallel With |
|---|-------|------|------|------------|---------------|
| 1 | Title | story | S | — | — |
| 2 | Title | story | M | #1 | — |
| 3 | Title | story | S | — | #2 |
---
## Child 1
---
type: story
title: "Child title"
parent: "Parent requirement title"
labels:
- "area:relevant"
priority: high
size: S
status: draft
dependencies: []
acceptance_criteria:
- "Given X, when Y, then Z"
---
### User Story
As a [role], I want [capability], so that [benefit].
### Acceptance Criteria
- [ ] Given X, when Y, then Z
- [ ] ...
---
## Child 2
[... same pattern ...]
npx claudepluginhub cpliakas/claude-code-digital-coworkers --plugin product-opsThis skill should be used when the user asks to "break down this initiative", "decompose into tasks", "create tasks from initiative", "how to size tasks", "when to decompose", "vertical slices", "task granularity", or needs guidance on breaking higher-level work into lower-level work items.
Decomposes epics into INVEST-validated user stories with Given-When-Then acceptance criteria, Fibonacci/T-shirt estimates (default Sprint-level), and a Story Map for sprint planning.
Breaks plans, specs, or PRDs into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Useful for turning high-level direction into actionable, demoable tasks.