Generate traceable user stories from PMContext artifacts with 3C structure and INVEST validation.
npx skills add https://github.com/Wcof/PMSkill --skill pm-stories-wcof
Please help me install this Agent Skill. Skill: pm-stories Source: https://github.com/Wcof/PMSkill/tree/main/skills/delivery/pm-stories Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-stories-wcof
This Skill helps product teams convert a structured PMContext into delivery-ready user stories without losing traceability. It prevents vague backlog items, untestable acceptance criteria, and story definitions that drift away from the original requirement source.
Ask the agent to use pm-stories to generate user stories from the current PMContext for your target feature or product flow.
High-intent search queries and answers about installing and using this skill.
To generate user stories from product requirements, you need a structured PMContext artifact. The system decomposes user scenarios and business rules into traceable stories using 3C structure and INVEST validation, ensuring backlog items are sprint-ready with testable acceptance criteria.
The best way to write testable acceptance criteria is to decompose product requirements into 3C-structured user stories. This process drafts four to six observable acceptance criteria per story, flags missing source details, and ensures each item passes INVEST validation for sprint planning.
INVEST validation improves agile backlog creation by checking each user story for independence, negotiability, value, estimability, smallness, and testability. Applying INVEST to 3C-structured stories derived from PMContext prevents vague backlog items and ensures story definitions do not drift from original requirement sources.
Yes, you can cross-check generated user stories against existing sketch artifacts. This diff checking reveals gaps between your product visualization and the generated backlog, ensuring that your traceable stories and acceptance criteria accurately reflect the intended design outputs.
Yes, you need a structured PMContext to decompose product requirements effectively. The PMContext provides the necessary user scenarios, business rules, and boundary conditions required to generate traceable 3C-structured stories with single-role design and testable acceptance criteria.
Backlog user stories drift from the original requirement source when traceability is lost during decomposition. Generating stories directly from PMContext artifacts maps each story back to specific user scenarios and boundary conditions, while assumption labeling flags missing source details to prevent untestable acceptance criteria.
WcofGenerate a product vision and stakeholder alignment plan from structured PMContext.
AgLyx3Generate user stories and acceptance criteria for agile backlog management.
psd401Translate product ideas into structured PRDs and user stories.
newkayak12Decompose large user stories into smaller stories using eight splitting patterns.
