Create and validate User Stories using 3C and INVEST criteria.
npx skills add https://github.com/jason23452/my-skill --skill user-stories-jason23452
Please help me install this Agent Skill. Skill: user-stories Source: https://github.com/jason23452/my-skill/tree/main/flow/user-stories Command: npx skills add https://github.com/jason23452/my-skill --skill user-stories-jason23452
High-intent search queries and answers about installing and using this skill.
Decompose the requirements document into one story per coherent product slice, each with a Card statement, Conversation notes, and Confirmation acceptance criteria. Preserve the source requirement id and path for traceability.
INVEST checks that each story is Independent, Negotiable, Valuable, Estimable, Small, and Testable. A story passes when it can be planned alone, describes outcomes not implementation, and has observable pass/fail acceptance criteria.
This Skill requires at least three Given/When/Then scenarios: a happy path, a validation/permission/boundary path, and a state/failure/recovery or audit path. Add more for empty, error, or conflict states when the workflow requires them.
Use job stories when the situation and trigger matter more than the actor, such as event-driven workflows. Use the standard 'As a [actor]' format when user role and permissions drive the behavior.
Common issues include sequence-only titles like 'US-01', missing non-goals, untestable acceptance criteria, and stories that bundle multiple product slices. The batch quality gate rejects stories lacking scope, traceability, or coverage of requirement dimensions.
nimrodfisherIdentify and structure stakeholder requirements into actionable documents with acceptance criteria.
kernex-devConvert specifications into structured task lists with estimates and dependencies.
GustaPaesValidate and close product backlog stories for sprint readiness.
Dev10x-GuruGuide structured DDD Event Storming workshops to identify domain events and bounded contexts.
