# Sw User Story Creator

> Use when user wants to create user stories, acceptance criteria, or a requirements document from a software idea, vision.md, or sw-idea-analyzer output – generates a complete structured requirements/user-stories.md file.

- Skill: `chfle/sw-user-story-creator` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add chfle/sw-user-story-creator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/chfle/sw-user-story-creator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: chfle (https://skillmd.com/u/chfle)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/chfle/sw-user-story-creator

---


# SW User Story Creator

## Overview

Reads `requirements/vision.md` (generated by `sw-idea-analyzer`) and produces a complete, professional user story document at `requirements/user-stories.md`. Operates silently – no file content is shown in the chat.

**Language detection:** Read the user's input language and respond entirely in that language. Default to German if undetectable.

---

## Required Input – Check in Order

1. **`requirements/vision.md` exists** → read it, extract idea title, target audience, core features, and risks. Use as the primary source.
2. **`requirements/vision.md` missing, user provided description** → use the description as input.
3. **`requirements/vision.md` missing, no input given** → stop and respond:

   > `requirements/vision.md` not found.
   > Run `/sw-idea-analyzer` first to generate it, or provide your idea directly:
   > `/sw-user-story-creator <your description>`

---

## User Story Format

Every story follows this exact structure:

```
### US-XXX: <Short Title>

**As a** [role], **I want** [goal] **so that** [benefit].

**Priority:** MVP | Nice-to-have

**Acceptance Criteria:**
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
```

**Rules:**
- Role = specific user type from the target audience (not "user" generically)
- Goal = concrete action, not a vague wish
- Benefit = measurable or observable outcome
- Each story gets 3–5 acceptance criteria minimum
- MVP = required for the first working version; Nice-to-have = can be deferred
- IDs start at `US-001` and increment sequentially across the entire document (never reset per epic)
- If `requirements/user-stories.md` already exists: read the entire file, find the highest `US-XXX` ID, continue from the next number, and **append** new epics/stories to the end — never modify existing content

---

## Epics

Group stories into epics derived from the core feature areas in the input. Name each epic after the feature cluster it represents.

**Example epics for a task manager:**
- Epic: Authentication & Onboarding
- Epic: Task Management
- Epic: Notifications
- Epic: Settings & Profile

Generate at least one story per core MVP feature. Add 1–2 Nice-to-have stories per epic.

---

## Output Rules

- **Never output the file content in the chat.** All content goes to the file only.
- Do not show any user stories, acceptance criteria, or Markdown in the chat response.
- The only chat output allowed is the two confirmation lines at the end.
- Use the user's language throughout the file content.
- Never truncate – include every story, every acceptance criterion in the file.

---

## File Output

After generating all stories, write to `requirements/user-stories.md` in the repository root.

**Steps:**
1. If `requirements/` does not exist: `mkdir -p requirements`
2. Write the complete document to `requirements/user-stories.md`
3. Print **only** these two lines to the chat – nothing else:

> ✅ File created: `requirements/user-stories.md`
> Open it in your editor or commit it.

One optional sentence max summarizing what was generated (e.g. "Generated 12 user stories across 4 epics."). No code blocks, no Markdown content, no full output.

**`requirements/user-stories.md` structure:**

```markdown
# User Stories: <Project Title>

> Generated: <YYYY-MM-DD>

---

## Epic: <Epic Name>

### US-001: <Title>

**As a** [role], **I want** [goal] **so that** [benefit].

**Priority:** MVP

**Acceptance Criteria:**
- [ ] ...
- [ ] ...
- [ ] ...

---

### US-002: <Title>
...
```

---

## Next Skill

> ▶ **Next steps:**
> 1. Run `/sw-use-case-creator` to expand user stories into detailed use cases with actor flows and exceptions
> 2. Run `/sw-tech-stack-planner` to select the tech stack and generate `requirements/tech-stack.yaml`
> 3. Optionally run `/sw-diagram-creator` to visualize the architecture