product-on-purpose/pm-skills

deliver-user-stories

Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/product-on-purpose/pm-skills --skill deliver-user-stories

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

<!-- 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.

  1. 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.

  1. 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.

  1. 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.

  1. Define Acceptance Criteria

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

  1. Apply INVEST Criteria

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

  1. 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.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
product-on-purpose
커뮤니티

discover-interview-synthesis

Synthesizes user research interviews into actionable insights, patterns, and recommendations. Use after conducting user interviews, customer calls, or usability sessions to extract and communicate findings across participants. Distinct from foundation-meeting-recap, which summarizes one internal meeting for its attendees; this skill aggregates research conversations into evidence-backed findings.

1시간 설치 수
1
GitHub Stars
777
업데이트
10월 31일
product-on-purpose
커뮤니티

tool-design-sprint-prototype-plan

Day 4 (Thursday) move of a Design Sprint that produces the planning artifact for the day. Output covers the prototype role plan (Maker, Stitcher, Writer, Asset Collector, Interviewer), prototype brief (what to build, fidelity bar, time allocation per role), canonical Five-Act Interview script (Welcome, Context, Intro, Tasks, Debrief), trial-run checklist, and Friday participant confirmation tracker. The actual prototype build is craft work outside the skill's AI invocation surface. Use Thursday

1시간 설치 수
1
GitHub Stars
777
업데이트
10월 31일
product-on-purpose
커뮤니티

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.

1시간 설치 수
1
GitHub Stars
777
업데이트
10월 31일
product-on-purpose
커뮤니티

deliver-acceptance-criteria

Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.

1시간 설치 수
2
GitHub Stars
746
업데이트
10월 20일