deanpeters/Product-Manager-Skills
user-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
Before you install
- Last update
- Files in folder
- 5
- Scripts
- Contains scripts. Review them before running.
- SKILL.md size
- 11 KB (about 2,864 tokens of context each time it loads)
- License
- No license file
- Source on GitHub
- deanpeters/Product-Manager-Skills
Skills are plain text instructions the agent follows, sometimes with scripts. Check the source, prefer repositories with many installs and stars, and read any script it ships.
Install
npx skills add deanpeters/Product-Manager-Skills@user-storyRuns in a terminal with Node.js 18 or newer. Add -y to skip the prompts and -g to install for every project instead of this one.
Install for your agent
npx skills add deanpeters/Product-Manager-Skills@user-story --agent claude-code -y- Project install writes to
.claude/skills/user-story- Global install writes to
~/.claude/skills/user-story
Start a new session afterwards so the agent picks the skill up. In Claude Code you can also call it directly with /user-story.
What it does
Purpose 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 success criteria. This is not a feature spec—it's a conversation starter that captures who benefits, what they're trying to do, why it matters, and how you'll know it works. Input Works best with: The feature or user need the story captures. Also useful: The user role, the outcome they want, and…
Excerpt from the skill's own SKILL.md. Read the full file on GitHub before installing: skills run with your agent's permissions.
Related skills
- prd-development
deanpeters/Product-Manager-Skills
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
- roadmap-planning
deanpeters/Product-Manager-Skills
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
- company-research
deanpeters/Product-Manager-Skills
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
- discovery-process
deanpeters/Product-Manager-Skills
Run a full discovery cycle from problem hypothesis to validated solution. Use when a team needs a structured path through framing, interviews, synthesis, and experiments.
- jobs-to-be-done
deanpeters/Product-Manager-Skills
Uncover customer jobs, pains, and gains in a structured JTBD format. Use when clarifying unmet needs, repositioning a product, or improving discovery and messaging.
- discovery-interview-prep
deanpeters/Product-Manager-Skills
Plan customer discovery interviews with the right goal, segment, constraints, and method. Use when preparing interviews for problem validation, churn research, or new product ideas.