feature-to-stories

Decompose GitHub Issues Features into User Story work items with dependency links.

Updated May 2, 2024
One-click install
npx skills add https://github.com/cman131/EatSomethingSourWhenYoureTired --skill feature-to-stories-cman131
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-to-stories
Source: https://github.com/cman131/EatSomethingSourWhenYoureTired/tree/main/.claude/skills/feature-to-stories
Command: npx skills add https://github.com/cman131/EatSomethingSourWhenYoureTired --skill feature-to-stories-cman131

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Breaking a large Feature into implementation-ready User Stories is slow and error-prone: stories get duplicated on re-runs, acceptance criteria leak implementation details, and dependency links are wired incorrectly. This Skill guides an iterative breakdown workflow that proposes stories, refines granularity with the user, then creates and links them in the issue tracker. ## Core Features & Use Cases - Iterative story breakdown: Proposes a story table with scope and dependencies, then merges, splits, or renames stories based on user feedback before creating anything. - Duplicate prevention on re-runs: Loads existing child stories under the Feature first so new stories never overlap with work already tracked. - Implementation-detail stripping: Rewrites acceptance criteria as observable Given/When/Then outcomes, removing file paths, symbol names, and API signatures. - Use Case: A product owner has Feature #4008989 for a mahjong club site dashboard and a PRD file. Run the Skill with the feature ID and PRD path to get a proposed story breakdown, approve it after one revision round, and have all stories created with predecessor links wired automatically. ## Quick Start Ask the AI to break down Feature 4008989 using the PRD at mahjong-site/plans/home-page-health-score-addin/prd.md into user stories with dependency links.

Frequently Asked Questions about feature-to-stories

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

FAQPage Schema
How do I break down a feature into user stories in GitHub Issues?▼

Provide the feature ID and optionally a PRD path or description as arguments. The Skill loads the feature and its existing stories, proposes a breakdown table with dependencies, and creates the stories only after you approve the proposal.

How to split user stories that are too large?▼

Split a story if it touches more than 8 files, produces over 300 lines of output, has more than 7 acceptance criteria, or spans 3+ distinct layers such as UI, API, and data model. Merge stories that share the same file set and form one shippable unit.

Can I re-run story breakdown on a feature that already has stories?▼

Yes, the Skill is re-runnable. It fetches all existing child stories under the feature first and displays their titles, so newly proposed stories never duplicate work already tracked.

Does this work with Jira or Azure DevOps instead of GitHub Issues?▼

The instructions illustrate Azure DevOps MCP tool names and field paths, but the workflow is tracker-agnostic. Swap in the equivalent tool names and field paths for GitHub Issues or Jira, such as issue/epic/description.

Why should acceptance criteria avoid implementation details?▼

Stories describe what needs to exist and how to verify it, never how to build it. File paths, function names, and API signatures are removed so engineers discover patterns themselves, and ACs are rewritten as observable outcomes like "the correct band label is displayed".

What happens if the issue tracker integration is not connected?▼

The Skill stops during preflight and tells you to enable the tracker integration in your Claude Code MCP settings and restart. No stories are proposed or created without the work-item-lookup tool available.