メニュー
Generates user stories from PRD or initiative documents following agile best practices. Use for sprint planning, backlog creation, requirements decomposition, or development handoff.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Drafts or converts documents into Product Requirements Documents (PRD). Supports two modes - (1) Create new PRD from initiative documents and research, or (2) Convert existing documents to PRD format using standard or daily iteration templates.
Generates new feature ideas based on user feedback, internal notes, and historical PRDs using advanced pattern recognition and semantic analysis. Use when planning quarterly roadmaps, responding to accumulated user feedback, identifying next features after major releases, or conducting strategic planning sessions.
Analyzes market opportunity and sizing using TAM/SAM/SOM framework with supporting data research. Use when evaluating market potential, creating business cases for new products, preparing investor presentations, or assessing business opportunities.
Creates a new product initiative document using Socratic questioning and guided discovery. Use when starting a new product feature, clarifying vague product ideas, structuring informal concepts into formal proposals, or aligning stakeholders on initiative scope and goals.
Applies first principles thinking to break down complex problems to fundamental truths and reconstruct innovative solutions. Use when facing seemingly impossible challenges, when existing solutions are too costly or complex, when innovative breakthroughs are needed, or when challenging industry assumptions.
Applies the Five Whys root cause analysis method to identify underlying causes of problems through systematic questioning. Use when problems recur despite fixes, surface solutions fail, systematic improvement is needed, or team alignment on root causes is required.
| name | niopd-pd-stories |
| description | Generates user stories from PRD or initiative documents following agile best practices. Use for sprint planning, backlog creation, requirements decomposition, or development handoff. |
This skill generates well-structured user stories from product documents, following agile best practices and INVEST criteria.
User stories emerged from Extreme Programming (XP) and were formalized by Mike Cohn in his book "User Stories Applied" (2004).
"As a [persona], I want to [capability], so that [benefit]."
| Criterion | Meaning |
|---|---|
| Independent | Can be developed in any order |
| Negotiable | Details can be discussed |
| Valuable | Provides value to user/business |
| Estimable | Can be estimated by team |
| Small | Fits in a sprint |
| Testable | Has clear acceptance criteria |
Read from:
03-docs/03-docs/List all capabilities mentioned:
For each capability:
### Story: [Title]
**As a** [persona],
**I want to** [capability],
**So that** [benefit].
**Priority**: P0/P1/P2
**Estimate**: [Story Points]
**Acceptance Criteria**:
- [ ] Given [context], when [action], then [result]
- [ ] Given [context], when [action], then [result]
**Notes**: [Additional context]
Group related stories under epics:
For each story, verify:
File path: 03-docs/[YYYYMMDD]-user-stories-v0.md
[YYYYMMDD]-user-stories-v0.md03-docs/references/user-story-template.mdniopd-pd-draft-prd: PRD sourceniopd-pd-acceptance-criteria: Detailed criterianiopd-pm-agile-planning: Sprint planningniopd-ur-personas: Persona definitions