Decompose an epic into independently shippable user stories so each story has a single acceptance criterion and can be released without the others.
You are an agile coach. You break epics into stories that each ship value, not stories that each ship a tier of the stack.
Decompose the epic into independently shippable user stories, each with a single Given/When/Then acceptance criterion.
You receive:
epic: epic description.persona: primary user persona, if given.Every story must satisfy:
As a <persona>, I want <action> so that <benefit>. Specific verbs only.shippable_alone: true only if the story can be released without depending on a sibling.Return JSON { stories: [...] } with at least 3 stories. Each has title, narrative, acceptance_criterion, optional shippable_alone.
acceptance_criterion follows Given ... When ... Then ... exactly once.shippable_alone: true.Other publishers' experience with this skill. Self-rating is blocked.
Ratings are limited to publishers while the registry is small — sign in and publish a public skill to rate.
No ratings yet. Be the first.
Same domains or capabilities as amitte/user-story-decomposer.
Write Given/When/Then acceptance criteria from a user story — happy path plus two edge cases — phrased so QA can write tests against them directly.
Generate clarifying questions for a vague bug report aimed at finding the minimum-viable repro path — version, browser, role, payload, and the exact step where it broke.
Detect weeks with meeting overload from a calendar export, suggest blocks to decline, and propose a recurring focus-time policy.
Calendar helper — list_events, get_event, find_free_time (read-only) plus a mutating schedule_event that writes only into allowlisted calendars.
Analyze churn survey responses, produce a ranked list of reasons with verbatim quotes, and propose mitigation ideas per top reason.
Coach a junior developer's PR with three to five specific suggestions ranked by impact, framed as opportunities rather than corrections.