← ClaudeAtlas

epicslisted

Decomposes the PRD and architecture into user-value epics and stories with testable acceptance criteria, checks every requirement is covered, writes docs/epics.md, and creates GitHub milestones and issues. Use after the PRD and architecture exist and before creating stories, or when the user says "create epics", "break down the PRD", or "plan stories".
rterakedis/leanwheel-skills · ★ 2 · AI & Automation · score 65
Install: claude install-skill rterakedis/leanwheel-skills
# Epics Skill **Goal:** Decompose PRD into epics and stories; produce `docs/epics.md` and GitHub milestones. **Role:** Organize around user value, not tech layers. ## Activation 1. Read `docs/prd.md` (required; stop if missing). 2. Read `docs/architecture.md` (required; stop if missing). 3. Check for `docs/epics.md` (may be update run). 4. Confirm: "Read PRD and architecture. Ready to design epics." ## Phase 1 — Design Epic List Principles: - User value (not tech layers); independently shippable; natural progression - 3–6 stories per epic; minimize file churn Process: 1. Group PRD FRs by user capability 2. Draft: title + one-sentence goal per epic 3. Confirm with user: standalone value? right FRs? correct sequence? 4. Iterate until approved ## Phase 2 — Generate Stories Rules: - One dev session per story; split if too large - Sequential dependencies only (N.3 depends on N.1, N.2 only) - Create only what needed (no speculation) - 2–4 testable ACs per story - Track FR coverage explicitly For each epic: 1. List FRs it covers 2. Propose breakdown: title + one-liner + FRs satisfied 3. Get user confirmation, adjust 4. Write full entries using template **Testability foundation story (Apple app projects):** if the architecture targets iOS/iPadOS/macOS, Epic 1 must include an early story (immediately after project scaffold, before the first feature story) that ships the foundation from `docs/setup/swift/testability.md`: the `SeedScenario` registry (empty/firstRun/typical/he