agentleFS
lechithinhlechithinh/ba-claude-skills/skills/user-story-writer/SKILL.md

user-story-writer

Skill1 starsChanged 9 days agoMITView on GitHub

Writes INVEST-compliant user stories with Gherkin (Given/When/Then) acceptance criteria from requirements, features or a functional decomposition, including edge cases, business-rule references, and a Jira-ready CSV export. Use when the user asks to write user stories, acceptance criteria, Gherkin scenarios, backlog items, Jira tickets, or says "viết user story", "viết acceptance criteria", "tạo backlog".

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use 0-template, github-actions-builder 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.
  • JayRHaSkill

    0-template

    Template for creating a new Agent Skill. Copy this folder, rename it to your skill's kebab-case name, and fill in every section. Use this as the starting point whenever you author a new skill for the AgentSkills library.

    Also in 3 projects that use this

  • JayRHaSkill

    github-actions-builder

    Builds reliable, fast, and secure GitHub Actions CI/CD workflows with dependency caching, build matrices, scoped secrets, concurrency control, and reusable/composite workflows. Use this skill when the user asks to "create a GitHub Actions workflow", "set up CI", "add CI/CD", "fix a flaky/slow GitHub Actions pipeline", "add a build matrix", "cache dependencies in CI", "write a reusable workflow", "configure deployment with environments and secrets", or mentions files under .github/workflows.

    Also in 3 projects that use this

  • MehdibargachSkill

    okr-writer

    Turn business goals into structured OKRs with measurable Key Results, linked initiatives, alignment check, and anti-goals. Takes a strategic priority and outputs ready-to-use OKRs.

    Also in 4 projects that use this

  • xmqywxSkill

    meeting-summarizer

    Transform meeting transcripts into structured summaries with action items, decisions, follow-ups, and efficiency analysis. Works with any meeting format.

    Also in 3 projects that use this

  • pbc-osSkill

    secrets-manager

    Set up and configure cloud secrets management for your AI agent. Guides users through platform selection (GCP, AWS, Azure, 1Password, Doppler, HashiCorp Vault), account setup, CLI configuration, and secure credential storage.

    Also in 3 projects that use this

  • +7 more from JayRHa

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 6 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:

    INVEST check: every story. If a story is too big (> ~5 AC scenarios or several roles/goals), split it using a named pattern: workflow …

    line 25
  2. Distinctive:

    When I select that slot and confirm Then the booking is created with status "Confirmed" And I receive a confirmation notification

    line 44
  3. Distinctive:

    After all stories, provide:

    line 59
  4. Distinctive:

    Avoid UI-prescriptive AC ("click the blue button") unless the user asks for UI-level detail.

    line 68

“Common” is measured: kept by at least 6 in 10 of the 6 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 Story Writer

Act as a senior Business Analyst / Product Owner writing backlog-ready user stories that developers can estimate and testers can verify.

Language

Reply in the user's language. Gherkin keywords stay in English (Given/When/Then/And/But) because test tools expect them, unless the user asks for Vietnamese keywords (Cho/Khi/Thì).

Input

Requirements, a feature list, a functional decomposition (IDs like 1.1.1), or a short idea. Reuse source IDs for traceability.

Process

  1. One story per user goal. Format: As a <specific role>, I want <goal> so that <business value>. Role must be concrete (Patient, Receptionist) — never "user" if a better role exists.
  2. Acceptance criteria in Gherkin, at least:
    • 1 happy path
    • 1–3 alternative / error paths (invalid input, permission denied, empty state, limit reached, concurrency)
    • Business-rule scenarios referencing BR IDs where available
  3. INVEST check every story. If a story is too big (> ~5 AC scenarios or several roles/goals), split it using a named pattern: workflow steps, business-rule variations, CRUD operations, data variations, happy/unhappy path, or platform.
  4. Add metadata: ID, source trace, priority (MoSCoW if known), dependencies, notes for UI/NFR.
  5. Never invent business values (limits, fees, timeouts). Use [value — confirm] placeholders.

Output format

### US-01 · Book an appointment
**Trace:** FD 1.1.1, FR-03 · **Priority:** Must · **Depends on:** US-00 (Login)

**As a** Patient
**I want** to book an available slot with a chosen doctor
**so that** I don't have to call the clinic and wait.

**Acceptance criteria**
```gherkin
Scenario: Book an available slot
  Given I am logged in as a Patient
  And Dr. An has an available slot at 09:00 tomorrow
  When I select that slot and confirm
  Then the booking is created with status "Confirmed"
  And I receive a confirmation notification

Scenario: Slot taken by someone else meanwhile
  Given the slot was booked by another patient after I opened it
  When I confirm
  Then I see "This slot is no longer available"
  And I am shown the next 3 available slots
```

**INVEST:** ✅ I ✅ N ✅ V ✅ E ✅ S ✅ T
**Notes:** BR-02 limits patients to [2 — confirm] future bookings.

After all stories, provide:

  • Story map summary — table of stories grouped by module/feature.
  • Jira CSV (only if the user asks or says "Jira"): columns Summary,Issue Type,Description,Priority,Labels with descriptions escaped for CSV.

Domain knowledge

If the work belongs to a business domain that has a domain pack in this collection — domain-banking, domain-ecommerce (more under skills/domain-*) — load that skill too and apply its checklist.md and business-rules.md. Add the domain's typical alternative/error scenarios to acceptance criteria and reference the business-rule pattern used. If no pack exists, state which domain assumptions you made.

Guardrails

  • Stories describe behaviour visible to a user; technical tasks go in "Notes" or a separate "Enabler" item.
  • Avoid UI-prescriptive AC ("click the blue button") unless the user asks for UI-level detail.
  • Pair with requirements-linter to verify the result.

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.