agentleFS
Sign inStart free
omeirhaegheomeirhaeghe/staffgent/skills/user-stories/SKILL.md

user-stories

Skill1 starsChanged 5 months agoMITView on GitHub

Decompose an initiative into epics and user stories ready to paste into Linear or Jira.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brainstorm-experiments-new, brainstorm-experiments-existing and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • skytiger6724Skill

    brainstorm-experiments-new

    Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.

    Also in 9 projects that use this

  • skytiger6724Skill

    brainstorm-experiments-existing

    Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.

    Also in 7 projects that use this

  • 45ckSkill

    pestle-analysis

    Also in 7 projects that use this

  • About-IntelligenceSkill

    positioning-ideas

    Brainstorm product positioning ideas differentiated from competitors.

    Also in 7 projects that use this

  • launchapp-devSkill

    interview-script

    Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.

    Also in 10 projects that use this

  • About-IntelligenceSkill

    product-name

    Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.

    Also in 7 projects that use this

  • +6 more from skytiger6724

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If there is no PRD yet, STOP: don't invent epics from nothing.

    line 12
  2. Distinctive:

    Only build epics/stories once the PRD (or enough agreed detail) exists.

    line 15
  3. Distinctive:

    Every story has at least one acceptance criterion.

    line 50
  4. Distinctive:

    Keep titles imperative and short.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

User stories & epic decomposition

Break a PRD or feature into a clean backlog: epics → stories, each with acceptance criteria, sized and ready to import into Linear/Jira.

Prerequisite — work from a PRD. First check the ledger item's draft for a PRD. If there is no PRD yet, STOP: don't invent epics from nothing. Tell your manager you need the PRD first, ask the key product questions (problem, target users, goals & non-goals, scope, success metrics), and offer to write the PRD before decomposing. Only build epics/stories once the PRD (or enough agreed detail) exists.

Method

  1. Identify epics — the 2–6 major chunks of work (by user journey or capability, not by team). Each epic has a goal and a definition of done.
  2. Write stories under each epic — vertical slices that deliver value. Use: As a <user>, I want <capability>, so that <benefit>.
  3. Acceptance criteria — for each story, list testable criteria in Given/When/Then form. These are the contract; keep them unambiguous.
  4. Sequence & MVP — mark which stories are MVP vs fast-follow. Note dependencies.
  5. Estimate — a rough size per story (S/M/L or points) and flag the spikes/unknowns.

Output format (paste-ready)

Group by epic. For each story use this block:

### [EPIC] <epic name>
- **Goal:** …
- **Definition of done:** …

#### <story title>
**Story:** As a <user>, I want <capability>, so that <benefit>.
**Acceptance criteria:**
- Given <context>, when <action>, then <result>.
- …
**Priority:** MVP | Fast-follow   **Estimate:** S/M/L   **Labels:** <area>
**Dependencies:** <story/system or none>

Also offer a CSV block for bulk import when asked (columns: Type,Epic,Title,Description,Acceptance Criteria,Priority,Estimate,Labels) — Linear and Jira both accept CSV import.

Rules:

  • Stories are independently shippable and testable; no "build the backend" tasks.
  • Every story has at least one acceptance criterion.
  • Keep titles imperative and short.

Save the breakdown with start_draft as "<initiative> — Backlog", link it to the ledger item, and move the item to define or prove. Then record the primary epic on the ledger item with add_epic (its title, and the Linear/Jira key + link if it's tracked there) so the item shows the epic that delivers it; keep its status current with update_epic. The golden-tests skill turns these acceptance criteria into test cases.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free