From pm-execution
Breaks features or PRDs into 5-15 backlog items in user stories, job stories, or WWA formats, each with 3-5 acceptance criteria, priorities, dependencies, and story map.
How this command is triggered — by the user, by Claude, or both
Slash command
/pm-execution:write-stories [user|job|wwa] <feature description or PRD>The summary Claude sees in its command listing — used to decide when to auto-load this command
# /write-stories -- Backlog Item Generator Break a feature into well-structured backlog items. Choose from three formats based on your team's preference, each with full acceptance criteria. ## Invocation ## Formats ### User Stories **Format**: "As a [user type], I want [capability], so that [benefit]" Apply the **user-stories** skill: - Follow the 3 C's: Card (brief), Conversation (context), Confirmation (acceptance criteria) - Validate against INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable - Include design links or mockup references where relevant ### Job Stor...
Break a feature into well-structured backlog items. Choose from three formats based on your team's preference, each with full acceptance criteria.
/write-stories user Allow users to export reports as PDF and CSV
/write-stories job Notification system for task deadlines
/write-stories wwa Dark mode for the mobile app
/write-stories [upload a PRD or feature spec] # asks format preference
/write-stories # asks for feature and format
Format: "As a [user type], I want [capability], so that [benefit]" Apply the user-stories skill:
Format: "When [situation], I want to [motivation], so I can [outcome]" Apply the job-stories skill:
Format: Why [strategic context] → What [deliverable] → Acceptance [criteria] Apply the wwas skill:
Accept in any form: PRD, feature description, user research finding, or verbal idea. If a PRD is provided, extract the requirements to decompose.
If not specified in the invocation, ask:
## Backlog: [Feature Name]
**Format**: [User Stories / Job Stories / WWA]
**Total stories**: [count]
**Estimated total effort**: [if possible]
### Stories
#### Story 1: [Short title]
**[The story in chosen format]**
Acceptance Criteria:
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]
Priority: [P0/P1/P2] | Effort: [S/M/L] | Dependencies: [none or list]
---
[Repeat for each story]
### Story Map
[Visual ordering: must-have → should-have → nice-to-have]
### Technical Notes
[Cross-cutting concerns: API changes, data migration, infrastructure]
### Open Questions
[Things that need answers before implementation can start]
Save as markdown.
npx claudepluginhub phuryn/pm-skills --plugin pm-execution/write-storiesDecomposes features or PRDs into 5-15 backlog items as user stories, job stories, or WWA format, each with acceptance criteria, priorities, story map, and tech notes.
/split-storiesAnalyzes user stories for linguistic red flags and proposes incremental splits with multiple alternative techniques, then generates a report with diagnostics and recommended delivery order.
/workflow-sprint-planningRuns Sprint Planning workflow to generate refinement notes, user stories with acceptance criteria, and edge cases from a backlog or PRD.
/featureCaptures, researches, and specs a feature for an existing product, producing a spec and actionable stories. Supports --deep, --epic, --ticket flags for context.