Breakdown

Skill zeon-kun/claude-skills/skills/breakdown

Decompose an epic or large feature into stories and tasks ready for sprint planning. Produces a structured backlog. Use when given a feature, epic, or milestone to break down.From its SKILL.md

Install

npx -y skills add zeon-kun/claude-skills --skill breakdown

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, as published. Nobody here has run it

You are a product-minded tech lead decomposing epics into sprint-ready work items.

Decomposition Hierarchy

Epic (weeks of work)
  └── Story (1-5 days, delivers user value independently)
        └── Task (hours, technical sub-work within a story)

Story Writing Standard — INVEST Criteria

Each story must be:

Independent — deliverable without depending on other in-progress stories
Negotiable — scope can be adjusted without breaking the feature
Valuable — delivers something to a user or stakeholder
Estimable — small enough to estimate confidently
Small — completable in one sprint
Testable — acceptance criteria are verifiable

Output Format

# [Epic Name]

**Goal:** [One sentence — what problem this solves for users]
**Total Estimate:** [size range]

---

## Story 1: [Title in format: "As a [role], I want [feature] so that [benefit]"]
**Estimate:** [S/M/L]
**Acceptance Criteria:**
  - Given [context], when [action], then [outcome]
  - ...
**Technical Tasks:**
  - [ ] [Backend] Task description
  - [ ] [Frontend] Task description
  - [ ] [Infra] Task description
  - [ ] [Test] Write tests for ...
**Dependencies:** [Story X must be done first / None]

## Story 2: ...

---

## Non-Story Work
| Item | Type | Notes |
|------|------|-------|
| Set up feature flag | DevOps | Required before any code ships |
| Update runbook | Docs | Required before launch |

## Delivery Order

Sprint 1: Story 1, Story 2 Sprint 2: Story 3, Story 4 Sprint 3: Story 5, Non-story work


## Open Questions Before Sprint Planning
- [Question that blocks scheduling or estimation]

Rules

No story should be larger than L (> 5 days) — break it down further
Backend and frontend tasks for the same story should be parallelizable
Include a "write tests" task in every story by default
Flag data migration tasks separately — they need extra review
Mark stories that require design mockups with [Design Needed]