agentsclimarketplace

NioPD PD stories

Skill 8421bit/NioPD-Skills/plugins/niopd/skills/NioPD-PD-stories

Agent Skills for AI-powered Product Management with Claude Code.

Install
npx -y skills add 8421bit/NioPD-Skills --skill NioPD-PD-stories

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generates user stories from PRD or initiative documents following agile best practices. Use for sprint planning, backlog creation, requirements decomposition, or development handoff.

SKILL.md

2.7 KB, as published. Nobody here has run it

User Story Generation Skill

This skill generates well-structured user stories from product documents, following agile best practices and INVEST criteria.

Theoretical Foundation

Origin

User stories emerged from Extreme Programming (XP) and were formalized by Mike Cohn in his book "User Stories Applied" (2004).

User Story Format

"As a [persona], I want to [capability], so that [benefit]."

INVEST Criteria

CriterionMeaning
IndependentCan be developed in any order
NegotiableDetails can be discussed
ValuableProvides value to user/business
EstimableCan be estimated by team
SmallFits in a sprint
TestableHas clear acceptance criteria

Story Levels

  • Epic: Large feature area (weeks-months)
  • Feature: Specific capability (days-weeks)
  • Story: Single piece of work (hours-days)
  • Task: Technical subtask (hours)

When to Use

  • Sprint planning
  • Backlog refinement
  • Requirements handoff
  • Feature scoping
  • Acceptance testing prep

Instructions

Step 1: Identify Source Document

Read from:

  • PRD in 03-docs/
  • Initiative in 03-docs/
  • Requirements summary

Step 2: Extract Requirements

List all capabilities mentioned:

  • Functional requirements
  • Non-functional requirements
  • User needs
  • Business rules

Step 3: Generate Stories

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]

Step 4: Organize by Epic

Group related stories under epics:

  • Epic 1: [Name]
    • Story 1.1
    • Story 1.2
  • Epic 2: [Name]

Step 5: Validate INVEST

For each story, verify:

  • Independent from other stories
  • Negotiable in implementation
  • Valuable to user/business
  • Estimable by team
  • Small enough for sprint
  • Testable with clear criteria

Step 6: Generate Report

File path: 03-docs/[YYYYMMDD]-user-stories-v0.md

Output Specifications

  • File Naming: [YYYYMMDD]-user-stories-v0.md
  • Location: 03-docs/
  • Template: references/user-story-template.md

Related Skills

  • niopd-pd-draft-prd: PRD source
  • niopd-pd-acceptance-criteria: Detailed criteria
  • niopd-pm-agile-planning: Sprint planning
  • niopd-ur-personas: Persona definitions

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.