AGENT SKILL

deliver-user-stories

Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given/When/Then acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.

License 许可
Apache-2.0
最近更新
2026-11-14
Stars
★ 805
Forks
102

01 前言 Front Matter

name
deliver-user-stories
license
Apache-2.0
metadata
{ "phase": "deliver", "author": "product-on-purpose", "updated": 1781049600000, "version": "2.1.0", "category": "specification", "frameworks": [ "triple-diamond", "lean-startup", "design-thinking" ] }
description
Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given/When/Then acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.

02 资源文件 4

03 SKILL.md 正文

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

User Stories

User stories are concise descriptions of functionality from the user's perspective. They capture who needs something, what they need, and why - without prescribing how to build it. Good user stories enable teams to break large features into estimable, deliverable increments while maintaining focus on user value.

When to Use

  • After PRD approval, when breaking down features for implementation
  • During sprint planning to create actionable work items
  • When writing tickets for engineering teams
  • When communicating requirements to stakeholders in accessible terms
  • When prioritizing a backlog based on user value

When NOT to Use

  • You need deeper, QA-ready Given/When/Then coverage for a single story or slice -> use deliver-acceptance-criteria
  • You need the feature-wide catalog of boundary conditions and failure scenarios -> use deliver-edge-cases
  • The feature itself is not yet specified -> use deliver-prd first; stories should trace back to documented requirements
  • You want refinement-session outcomes (estimates, scope decisions, open questions) -> use iterate-refinement-notes

Instructions

When asked to create user stories, follow these steps:

  1. Understand the Feature Context Review the PRD or feature description. Understand the overall goal, target users, and scope boundaries. User stories should trace back to documented requirements.

  2. Identify User Personas Determine which users interact with this feature. Each story should be written for a specific persona, not generic "users." Different personas may need different stories for the same feature.

  3. Break Down by User Goal Decompose the feature into distinct user goals. Each story should deliver a complete, valuable capability - something the user can actually do when the story is done.

  4. Write Story Statements Use the format: "As a [persona], I want [action] so that [benefit]." The benefit clause is critical - it explains why this matters and helps prioritize.

  5. Define Acceptance Criteria Write specific, testable criteria using Given/When/Then format. Acceptance criteria define "done" - if all criteria pass, the story is complete.

  6. Apply INVEST Criteria Validate each story against INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable. Revise stories that don't meet these criteria.

  7. Add Context and Notes Include relevant design references, technical considerations, and dependencies. These help implementers understand the full picture.

Output Format

Use the template in references/TEMPLATE.md to structure the output. A complete output carries, per story: Story Header; User Story Statement; Context & Background; Acceptance Criteria; Design Notes; Technical Notes; Dependencies; Out of Scope; and Open Questions where any remain. Multi-story documents nest these sections under one heading per story, as the example shows.

Quality Checklist

Before finalizing, verify:

  • [ ] Each story follows "As a... I want... so that..." format
  • [ ] Stories are independent (can be built in any order)
  • [ ] Acceptance criteria use Given/When/Then format
  • [ ] Each criterion is testable (someone can verify pass/fail)
  • [ ] Stories are small enough to complete in one sprint
  • [ ] No implementation details in the story statement
  • [ ] Benefit clause explains why this matters to the user

Examples

See references/EXAMPLE.md for a completed example.

04 同仓库更多 Skills

product-on-purpose
product-on-purpose/pm-skills

utility-update-pm-skills

Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.

★ 805
product-on-purpose
product-on-purpose/pm-skills

utility-slideshow-creator

Generates professional presentations from a JSON deck specification using 18 slide types with dark/light variants, content-to-layout decision logic, and calibrated character limits. Ships with a default professional theme.

★ 805
product-on-purpose
product-on-purpose/pm-skills

utility-pm-workflow-orchestrator

Run an ordered sequence of pm-skills against one input, pausing for go/no-go and stopping on a failed or empty step. Accepts a saved prioritized action plan (Mode A) or an ad-hoc named chain (Mode B; the chain command routes here). Explicit invocation only; run --dry-run first while the native path is EXPERIMENTAL. To author a durable workflow instead, use utility-pm-workflow-builder.

★ 805
product-on-purpose
product-on-purpose/pm-skills

utility-pm-workflow-builder

Guides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update checklist) in a staging area for review. Runs overlap analysis against the existing workflows with a Why Gate, then helps select and sequence skills with authored handoffs. Use when creating a new multi-skill workflow or promoting a repeated ad-hoc chain into a durable one. To build a single skill instead, use utility-pm-skill-builder; to run a sequence without authoring anything, use the chain command or utility-pm-workflow-orchestrator.

★ 805
product-on-purpose
product-on-purpose/pm-skills

utility-pm-skill-validate

Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass/fail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.

★ 805
product-on-purpose
product-on-purpose/pm-skills

utility-pm-skill-iterate

Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.

★ 805