user-stories

User stories are written by structuring them through the 3 C's framework (Card, Conversation, Confirmation) and validating them against the INVEST criteria to ensure they are independent, negotiable, valuable, estimable, small, and testable. This approach standardizes feature breakdown for product development workflows.

Feature breakdown is achieved by providing structured product context, feature details, and design specifications. The skill processes these inputs to generate structured backlog items that automatically adhere to standardized user story creation frameworks like the 3 C's and INVEST.

Yes, user story creation requires structured input for the product and feature context, but design links can be supplemented with explicit assumptions. You provide the feature name, product name, design context, and any known assumptions to generate the user stories.

The 3 C's framework improves backlog creation by ensuring every user story contains a Card (the short description), Conversation (the discussion details), and Confirmation (the acceptance tests). This structured approach enhances clarity and effectiveness for product managers and team leads.

INVEST criteria ensures feature breakdown results in user stories that are independent, negotiable, valuable, estimable, small, and testable. Applying these criteria prevents bloated backlog items and streamlines the creation of actionable, effective user stories for product development.

No platform integration is required as there are no external dependencies. The skill operates as a standalone component that processes your provided product, feature, design, and assumption parameters to output structured user stories for your existing workflows.