User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
Разбивает Epic или крупное требование на независимые User Stories с acceptance criteria в формате Given-When-Then, проверкой по INVEST и оценкой Story Points (Fibonacci или T-shirt).
Install Pm User Stories
$ npx skills add serejaris/personal-corp-os --skill pm-user-stories -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install serejaris/personal-corp-os pm-user-stories --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pm-user-stories .claude/skills/pm-user-stories && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pm-user-stories" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-user-stories into .claude/skills/pm-user-stories/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-user-stories", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-user-storiesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add serejaris/personal-corp-os --skill pm-user-stories -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install serejaris/personal-corp-os pm-user-stories --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pm-user-stories .agents/skills/pm-user-stories && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pm-user-stories" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-user-stories into .agents/skills/pm-user-stories/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-user-stories", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add serejaris/personal-corp-os --skill pm-user-stories -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install serejaris/personal-corp-os pm-user-stories --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pm-user-stories .cursor/skills/pm-user-stories && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pm-user-stories" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-user-stories into .cursor/skills/pm-user-stories/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-user-stories", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/serejaris/personal-corp-os.git --path skills/pm-user-stories--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add serejaris/personal-corp-os --skill pm-user-stories -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install serejaris/personal-corp-os pm-user-stories --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pm-user-stories .gemini/skills/pm-user-stories && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pm-user-stories" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-user-stories into .gemini/skills/pm-user-stories/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-user-stories", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install serejaris/personal-corp-os pm-user-storiesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add serejaris/personal-corp-os --skill pm-user-stories -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pm-user-stories .github/skills/pm-user-stories && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pm-user-stories" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-user-stories into .github/skills/pm-user-stories/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-user-stories", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add serejaris/personal-corp-os --skill pm-user-stories -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install serejaris/personal-corp-os pm-user-stories --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pm-user-stories .opencode/skills/pm-user-stories && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pm-user-stories" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-user-stories into .opencode/skills/pm-user-stories/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-user-stories", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pm-user-stories- GitHub stars
- 229
- Token cost
- ~1.7k tokens
- SKILL.md length
- 720 words
- Files
- 4 (incl. assets)
- Skills in repo
- 36
- Repo updated
- First seen
- Licence
- MIT
At a glance
Разбивает Epic или крупное требование на независимые User Stories с acceptance criteria в формате Given-When-Then, проверкой по INVEST и оценкой Story Points (Fibonacci или T-shirt).
- Works in 5 steps: Map the full requirement → Pick a splitting pattern → Write each User Story + AC → …
- /pm-user-stories
- SKILL.md covers Inputs, Step 1 — Map the full…, Step 2 — Pick a splitting… and Step 3 — Write each User Story…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pm User Stories is an agent skill from serejaris/personal-corp-os. Разбивает Epic или крупное требование на независимые User Stories с acceptance criteria в формате Given-When-Then, проверкой по INVEST и оценкой Story Points (Fibonacci или T-shirt). На выходе — Story Map с предложением по Sprint-планированию. User-invoked only — do NOT auto-trigger. Triggers on /pm-user-stories, "разбей на user stories", "разбить эпик", "story map", "AC", "acceptance criteria", "break down into user stories", "split this epic", "write user stories".
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including assets (for example `README.md` and `README.ru.md`).
It sits in Product & Project Management, covering User stories. The repository describes itself as: Personal Corp OS — управление личной компанией через AI-агентов: задачи вне головы, отделы вместо памяти, недельное ретро. Открытые скиллы для Claude Code и Codex. The licence is MIT.
When your agent uses it
- /pm-user-stories
- Разбей на user stories
- Acceptance criteria
- Break down into user stories
Example prompts
- “разбей на user stories”
- “story map”
- “acceptance criteria”
- “/pm-user-stories”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 95e36c3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pm User Stories loads about 1.7k tokens when it runs. Until then it costs about 122 tokens; SKILL.md has 720 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from serejaris/personal-corp-os at commit 95e36c3, republished under its MIT licence (© serejaris). 720 words, ~1,726 tokens.
Download SKILL.mdSave it as
.claude/skills/pm-user-stories/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- pm-user-stories
- description
- Разбивает Epic или крупное требование на независимые User Stories с acceptance criteria в формате Given-When-Then, проверкой по INVEST и оценкой Story Points (Fibonacci или T-shirt). На выходе — Story Map с предложением по Sprint-планированию. User-invoked only — do NOT auto-trigger. Triggers on /pm-user-stories, "разбей на user stories", "разбить эпик", "story map", "AC", "acceptance criteria", "break down into user stories", "split this epic", "write user stories".
pm-user-stories — Break an Epic into User Stories
Part of the Personal Corp framework — running a one-person business through AI agents. Decompose a large requirement or Epic into independently-deliverable User Stories. Every Story is validated against INVEST. Output is ready to paste into Jira, Linear, or GitHub Issues.
Inputs
| Field | Required | Notes |
|---|---|---|
| Requirement description | yes | An Epic or large requirement; can paste a PRD section |
| Granularity | no | Sprint-level (1-3 days/story) or iteration-level (1-2 weeks); default Sprint |
| Team composition | no | FE+BE split / full-stack / has mobile — affects per-tier splitting |
| Estimation system | no | Fibonacci (1/2/3/5/8/13) or T-shirt (S/M/L/XL); default Fibonacci |
Step 1 — Map the full requirement
Extract from the requirement:
- Roles involved: who uses this? (end user, admin, ops, etc.)
- Core flow: main path? branches?
- Business rules: constraints and conditions?
- Data entities: what data objects are involved?
Step 2 — Pick a splitting pattern
Five patterns. Pick by requirement shape; combine for hybrids.
| Pattern | When to use | Example |
|---|---|---|
| By workflow step | Requirement is a complete process | Checkout → pick item / address / payment / confirm |
| By business-rule variant | Same feature with multiple rule sets | Discount → fixed-amount / coupon / points / combined |
| By CRUD operation | Requirement centers on one data object | Address book → create / edit / delete / set default |
| By role perspective | Multi-role feature | Order management → user view / merchant processing / ops dashboard |
| By complexity progression | Feature has simple and full versions | Search → keyword / filters / suggestions / history |
Selection principle: target ≤ 1 Sprint per Story. Hybrid requirements combine patterns.
Granularity calibration:
- Stories < 3 → likely too coarse; check for hidden sub-flows
- Stories > 20 → likely too fine, or this is multiple Epics; split Epics first
- Single Story estimate > 8 points → too big; split further
Step 3 — Write each User Story + AC
### US-{N}: {Story title — verb-led, e.g. "Choose payment method"}
**Role:** As a {role}
**Action:** I want to {specific action}
**Value:** so that {business value}
**Priority:** P0 (must) / P1 (important) / P2 (nice-to-have)
**Story Points:** {estimate}
**Acceptance Criteria:**
- [ ] Given {precondition}, When {action}, Then {expected result}
- [ ] Given {exception precondition}, When {action}, Then {error handling}
**Dependencies:** {other Story IDs, or "none"}
**Tech notes:** {dev callouts, optional}Story Point reference (Fibonacci):
| Points | Complexity | Effort | Typical scope |
|---|---|---|---|
| 1 | Trivial | < 0.5 day | Copy change, config tweak, add an event |
| 2 | Simple | 0.5-1 day | One CRUD operation, form validation |
| 3 | Medium | 1-2 days | A complete feature point with business logic |
| 5 | Complex | 2-4 days | Multi-module interaction |
| 8 | Big | 4-7 days | New system / new flow core module |
| 13 | Re-split | > 1 week | Means the Story is too big — must split |
AC quality rules — every AC must satisfy:
- Specific: Given clause has a concrete precondition ("user logged in AND balance ≥ 100"), not "user logged in"
- Testable: Then clause has a verifiable result ("balance decreases by 100 AND order status = paid"), not "payment succeeds"
- Edge coverage: every Story has ≥ 1 happy-path AC + ≥ 1 exception-path AC
Show full SKILL.md (324 more words)Show less
Step 4 — INVEST validation
Run each Story against the six checks:
| Principle | Check | If fails |
|---|---|---|
| Independent | Delete this Story — can the others still ship? | Cyclic deps → merge or re-split |
| Negotiable | Does it describe "what" or "how"? | Strip implementation detail, keep value |
| Valuable | Will the user perceive value when this ships? | Pure refactor → attach to a user-perceivable feature |
| Estimable | Can the team agree on points within 5 minutes? | Wide spread = unclear requirement; clarify first |
| Small | Fits in one Sprint? | Larger → split |
| Testable | Can QA write test cases directly from the AC? | Add concrete edge values and expected results |
Definition of Ready (must hold before entering development):
| Check | Standard | If unmet |
|---|---|---|
| AC complete | ≥ 1 happy + ≥ 1 exception | Fill ACs, then schedule |
| No blocking deps | All upstream Stories done or mockable | Tag "Blocked", push to a later Sprint |
| Designs ready | UI Stories have design specs | No designs → tag "Needs design" |
| Estimation consensus | Spread < 2× | Re-discuss scope until agreed |
| Business rules confirmed | All [TBD] resolved | Confirm with PM/business, then dev |
Dependency rules:
- Data dependency: Story B needs data created by Story A → B depends on A
- Interface dependency: Story B calls API provided by A → B depends on A
- No dependency: Stories on different objects or different roles → parallel
- Pseudo-dependency: looks dependent but mockable → tag "Mockable to decouple"
Step 5 — Output a Story Map
## Epic: {requirement name}
### Story Map (user journey → Story mapping)
| Journey stage | Stories | Priority | Points |
|---|---|---|---|
| {stage 1} | US-001, US-002 | P0 | 5 |
| {stage 2} | US-003, US-004 | P1 | 8 |
### Sprint planning
- **Sprint 1 (MVP):** {Story list}, total {X} points
- **Sprint 2:** {Story list}, total {X} points
### Dependencies
US-001 → US-003 → US-005 (must follow this order)
US-002, US-004 (parallel)Quality bar
- Every Story passes all six INVEST checks
- AC uses Given-When-Then with ≥ 1 happy + ≥ 1 exception
- Dependencies tagged explicitly, with mockability flagged
- 13-point Stories must be re-split
- Story Map includes Sprint planning suggestion
When input is incomplete
- One-sentence requirement → first output a feature outline, confirm scope, then split
- Too large (> 20 Stories) → recommend splitting into Epics; agree on MVP scope first
- Missing business rules → tag
[business rule TBD]and propose plausible assumptions for confirmation
Related skills
/pm-prd— write a PRD first to lock scope, then break into Stories/pm-prioritize— when there are many Stories, RICE-rank for Sprint priority
© serejaris, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (assets) in skills/pm-user-stories of serejaris/personal-corp-os.
- SKILL.md
- README.md
- README.ru.md
- assets/illustration.png
Open the folder on GitHubat commit 95e36c3
Compare with similar skills
Pm User Stories next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pm User Stories this skillserejaris/personal-corp-os | 229 | — | ~1.7k | Automated safety check: Pass | MIT | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Agile Product Owneralirezarezvani/claude-skills | 28k | 3 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| To Specbestofjs/bestofjs | 3.1k | 21 repos | ~757 | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
To Spec
bestofjs/bestofjs
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
More from serejaris/personal-corp-os
All 36 skills in this repoWeekly Planning
serejaris/personal-corp-os
A skill your agent uses when the user is transitioning from a completed retro into a weekly plan, choosing weekly outcomes, scheduling a full ISO week, or asking for "план на неделю", "weekly…
Gh Issues
serejaris/personal-corp-os
A skill your agent uses when creating, searching, updating, or managing GitHub issues via CLI.
Product Data Audit
serejaris/personal-corp-os
A skill your agent uses when auditing a product, business, or project ecosystem — analyzing data sources, decision loops, bottlenecks, and implementation contours.
Tg Bot Ops
serejaris/personal-corp-os
A skill your agent uses when operating, debugging, deploying, or monitoring a Telegram bot or Telegram-to-agent gateway.
Audit Agent Rules
serejaris/personal-corp-os
Audits the agent rules in the current folder (AGENTS.md, nested AGENTS.md files) and the skill descriptions the agent sees at start, then reports what to cut, move or rewrite and edits only after…
Make Landing
serejaris/personal-corp-os
Создаёт несколько вариантов дизайна 2D-поверхности (лендинг, герой, обложка, слайды): свой визуальный референс и автор на вариант, полный design.md с UTC/SHA-256 до кода, проверка в браузере…
Related
Categories
Questions about Pm User Stories
What does Pm User Stories do?
Разбивает Epic или крупное требование на независимые User Stories с acceptance criteria в формате Given-When-Then, проверкой по INVEST и оценкой Story Points (Fibonacci или T-shirt). Pm User Stories is an agent skill from serejaris/personal-corp-os. Разбивает Epic или крупное требование на независимые User Stories с acceptance criteria в формате Given-When-Then, проверкой по INVEST и оценкой Story Points (Fibonacci или T-shirt).
When should I use Pm User Stories?
Pm User Stories fits situations like: /pm-user-stories; Разбей на user stories; acceptance criteria; break down into user stories.
How do I install Pm User Stories in Claude Code?
Run `npx skills add serejaris/personal-corp-os --skill pm-user-stories -a claude-code`. Or copy the skill folder (skills/pm-user-stories in serejaris/personal-corp-os) into .claude/skills/pm-user-stories in your project. Claude Code loads it when a task matches its description.
How do I install Pm User Stories in Codex?
Run `npx skills add serejaris/personal-corp-os --skill pm-user-stories -a codex`. Or copy the skill folder (skills/pm-user-stories in serejaris/personal-corp-os) into .agents/skills/pm-user-stories in your project. Codex loads it when a task matches its description.
Can I use Pm User Stories in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add serejaris/personal-corp-os --skill pm-user-stories -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pm-user-stories, .gemini/skills/pm-user-stories, .github/skills/pm-user-stories and .opencode/skills/pm-user-stories in your project.
What does Pm User Stories need to run?
SKILL.md names no scripts, command-line tools or credentials: Pm User Stories is instructions for the agent only.
Does Pm User Stories access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Pm User Stories safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pm User Stories use?
Pm User Stories is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pm User Stories use?
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pm User Stories?
Skills that share tags, products or a category with Pm User Stories: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Agile Product Owner (alirezarezvani/claude-skills, 28k stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pm User Stories?
serejaris (a GitHub user) maintains it in serejaris/personal-corp-os, which has 229 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 7, 2026.
Source: serejaris/personal-corp-os on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.