Feature Forge
Jeffallan/claude-skills
Runs a structured requirements interview to produce a feature specification with EARS requirements, acceptance criteria and an implementation checklist.
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
Install User Story Writer
$ npx skills add deanpeters/Product-Manager-Skills --skill user-story -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install deanpeters/Product-Manager-Skills user-story --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/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/user-story .claude/skills/user-story && 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 "user-story" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/user-story into .claude/skills/user-story/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-story", 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/deanpeters/Product-Manager-Skills/tree/main/skills/user-storyType 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 deanpeters/Product-Manager-Skills --skill user-story -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install deanpeters/Product-Manager-Skills user-story --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/user-story .agents/skills/user-story && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "user-story" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/user-story into .agents/skills/user-story/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-story", 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 deanpeters/Product-Manager-Skills --skill user-story -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install deanpeters/Product-Manager-Skills user-story --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/user-story .cursor/skills/user-story && 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 "user-story" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/user-story into .cursor/skills/user-story/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-story", 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/deanpeters/Product-Manager-Skills.git --path skills/user-story--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 deanpeters/Product-Manager-Skills --skill user-story -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install deanpeters/Product-Manager-Skills user-story --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/user-story .gemini/skills/user-story && 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 "user-story" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/user-story into .gemini/skills/user-story/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-story", 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 deanpeters/Product-Manager-Skills user-storyInstalls 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 deanpeters/Product-Manager-Skills --skill user-story -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/user-story .github/skills/user-story && 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 "user-story" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/user-story into .github/skills/user-story/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-story", 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 deanpeters/Product-Manager-Skills --skill user-story -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install deanpeters/Product-Manager-Skills user-story --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/user-story .opencode/skills/user-story && 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 "user-story" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/user-story into .opencode/skills/user-story/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-story", 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
user-story- GitHub stars
- 7.2k
- Used in
- 2 other repos
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,152 words
- Files
- 5 (incl. scripts)
- Skills in repo
- 75
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
- Works in 5 steps: Gather Context → Write the Use Case → Write the Acceptance Criteria → …
- Turning a feature request into a story with acceptance criteria
- SKILL.md covers Purpose, Input, Key Concepts and Application, plus 3 more sections
- Runs Python scripts from its folder; calls python3; reaches github.com
What it does
Each story pairs the Mike Cohn form, a persona, the action they want and the outcome they are after, with Gherkin-style criteria built from a scenario, given conditions, a triggering event and an expected result. The skill treats the story as a conversation starter rather than a feature spec: it records who benefits, what they are trying to do, why it matters and how you will know it works, so product, engineering and QA share one language.
You can supply the feature, the user role, the desired outcome and edge cases up front, and anything passed with the invocation counts as already answered and is not asked again. With no input, the skill first asks who the user is and what they want. It warns against four anti-patterns: a technical task dressed as a story, a feature list that needs splitting, a vague wish with no measurable outcome and a locked-in contract. A template, two sample stories and a Python template script are included.
When your agent uses it
- Turning a feature request into a story with acceptance criteria
- Writing testable Gherkin scenarios for a backlog item
- Rewriting a vague or oversized story into a clear one
Example prompts
- “Write a user story for exporting invoices as CSV, with Gherkin scenarios for an empty invoice list.”
- “This story says I want a better experience. Rewrite it with a clear outcome and acceptance criteria.”
- “Split this request for dashboards, reports and analytics into separate user stories.”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Gather Context
- Write the Use Case
- Write the Acceptance Criteria
- Add a Summary
- Validate and Refine
What it can do on your machine
Read from SKILL.md and the folder at commit 1b5a524. 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
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
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
User Story Writer loads about 2.9k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 1,152 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); the scripts in this folder are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,152 words (~2,852 tokens).
“Create clear, concise user stories that combine Mike Cohn's user story format with Gherkin-style acceptance criteria. Use this to translate user needs into actionable development work that focuses on outcomes, ensures shared understanding between product and engineering, and provides testable…”
- name
- user-story
- argument-hint
- [feature or user need]
- intent
- Create clear, concise user stories that combine Mike Cohn's user story format with Gherkin-style acceptance criteria. Use this to translate user needs into…
- type
- component
- theme
- pm-artifacts
- best_for
- Writing user stories with proper acceptance criteria, Converting requirements into development-ready stories, Establishing story quality standards across your…
- scenarios
- I need to write a user story for a new notification system in our B2B SaaS app, Convert this PRD requirement into a properly formatted user story with Gherkin…
- estimated_time
- 5-10 min
Files
SKILL.md and 4 other files (scripts) in skills/user-story of deanpeters/Product-Manager-Skills.
- SKILL.md
- examples/sample-industrial.md
- examples/sample.md
- scripts/user-story-template.py
- template.md
Open the folder on GitHubat commit 1b5a524
Used in 2 other repositories
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in deanpeters/Product-Manager-Skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
User Story Writer 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 |
|---|---|---|---|---|---|---|
| User Story Writer this skilldeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Feature ForgeJeffallan/claude-skills | 12k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Specificationcitypaul/.dotfiles | 740 | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Find Gapscitypaul/.dotfiles | 740 | — | ~6.6k | Automated safety check: Pass | Custom licence | |
| Backlog Groomingforcedotcom/salesforcedx-vscode | 1k | — | ~1.5k | Automated safety check: Pass | BSD-3-Clause | |
| Ambiguity DetectorArabelaTso/Skills-4-SE | 253 | — | ~2.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Specification
citypaul/.dotfiles
Turn fuzzy intent into shared understanding and acceptance criteria — specification as a conversation, run one question at a time, before any story is split or planned.
Find Gaps
citypaul/.dotfiles
Adversarially review an existing written artifact — stories, plans, acceptance criteria, specs, or design mocks — to surface missing states, unhandled edge cases, unstated assumptions, unverifiable…
Backlog Grooming
forcedotcom/salesforcedx-vscode
Triage the team's open GUS backlog — propose closing done-but-open work items (with code/test citations), flag under-specified items for grilling, catch wrong-epic / orphan / unpointed / dead-link…
Ambiguity Detector
ArabelaTso/Skills-4-SE
Detects and analyzes ambiguous language in software requirements and user stories.
Requirement Enhancer
ArabelaTso/Skills-4-SE
Iteratively enhance user requirements into clear, complete, actionable specifications through analysis and clarification.
More from deanpeters/Product-Manager-Skills
All 75 skills in this repoTAM SAM SOM Calculator
deanpeters/Product-Manager-Skills
Calculates total, serviceable available and serviceable obtainable market size for a product idea with explicit assumptions, methods and caveats.
Organic Growth Path Advisor
deanpeters/Product-Manager-Skills
Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.
Prioritization Framework Advisor
deanpeters/Product-Manager-Skills
Picks the right prioritization framework for your stage and context instead of defaulting to RICE or ICE out of habit.
Strategic Roadmap Planning
deanpeters/Product-Manager-Skills
Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.
User Story Mapping
deanpeters/Product-Manager-Skills
Lays out a user journey as activities, steps, and tasks on a two-dimensional map that then informs backlog slicing.
Company Research Brief
deanpeters/Product-Manager-Skills
Builds a company research brief covering executive quotes, product strategy, transformation efforts and org context, tailored to interview prep, competitor or partnership work.
Related
Categories
Questions about User Story Writer
What does User Story Writer do?
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions. Each story pairs the Mike Cohn form, a persona, the action they want and the outcome they are after, with Gherkin-style criteria built from a scenario, given conditions, a triggering event and an expected result. The skill treats the story as a conversation starter rather than a feature spec: it records who benefits, what they are trying to do, why it matters and how you will know it works, so product, engineering and QA share one language.
When should I use User Story Writer?
User Story Writer fits situations like: turning a feature request into a story with acceptance criteria; writing testable Gherkin scenarios for a backlog item; rewriting a vague or oversized story into a clear one.
How do I install User Story Writer in Claude Code?
Run `npx skills add deanpeters/Product-Manager-Skills --skill user-story -a claude-code`. Or copy the skill folder (skills/user-story in deanpeters/Product-Manager-Skills) into .claude/skills/user-story in your project. Claude Code loads it when a task matches its description.
How do I install User Story Writer in Codex?
Run `npx skills add deanpeters/Product-Manager-Skills --skill user-story -a codex`. Or copy the skill folder (skills/user-story in deanpeters/Product-Manager-Skills) into .agents/skills/user-story in your project. Codex loads it when a task matches its description.
Can I use User Story Writer 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 deanpeters/Product-Manager-Skills --skill user-story -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/user-story, .gemini/skills/user-story, .github/skills/user-story and .opencode/skills/user-story in your project.
What does User Story Writer need to run?
Going by SKILL.md and its folder, User Story Writer needs Python for the scripts in its folder and the command-line tools its instructions call (python3).
Does User Story Writer access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is User Story Writer 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does User Story Writer use?
User Story Writer has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does User Story Writer use?
About 2.9k tokens (SKILL.md is roughly 11k 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 User Story Writer?
Skills that share tags, products or a category with User Story Writer: Feature Forge (Jeffallan/claude-skills, 12k stars), Specification (citypaul/.dotfiles, 740 stars), Find Gaps (citypaul/.dotfiles, 740 stars) and Backlog Grooming (forcedotcom/salesforcedx-vscode, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains User Story Writer?
deanpeters (a GitHub user) maintains it in deanpeters/Product-Manager-Skills, which has 7,224 GitHub stars. The repository holds 75 skills in this directory. The repository was last updated on September 1, 2026.
Source: deanpeters/Product-Manager-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.