user-stories

Name: user-stories
Availability: InStock
Author: cna-bootcamp

Generates INVEST-compliant user stories from Event Storming results and solution selections.

23|5|Updated Jul 17, 2025

Search Tags:#requirements #microservices #agile #user stories #product backlog #event storming

Ready to run

npx skills add https://github.com/cna-bootcamp/clauding-guide --skill user-stories-cna-bootcamp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: user-stories
Source: https://github.com/cna-bootcamp/clauding-guide/tree/main/.claude/skills/15-user-stories
Command: npx skills add https://github.com/cna-bootcamp/clauding-guide --skill user-stories-cna-bootcamp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of translating Event Storming outcomes and selected solutions into well-defined, actionable user stories that adhere to the INVEST principles, ensuring clarity and efficiency in product development.

Core Features & Use Cases

User Story Generation: Creates user stories from Event Storming artifacts like events, commands, and actors.
Microservice Mapping: Guides the identification and definition of microservices based on event clustering and aggregate identification.
INVEST Principle Adherence: Ensures stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable.
Use Case: After an Event Storming session for a new e-commerce platform, use this Skill to automatically generate the initial backlog of user stories for the 'User Service' and 'Order Service', complete with acceptance criteria and priority levels.

Quick Start

Use the user-stories skill to generate user stories from the provided event storming diagrams.

Frequently Asked Questions about user-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate INVEST-compliant user stories from Event Storming results?▼

Generate INVEST-compliant user stories by mapping Event Storming artifacts like events, commands, and actors into structured requirements. This process ensures stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable for agile development.

What's the best way to define microservices from an event storming backlog?▼

Define microservices from an event storming backlog by clustering related events and identifying aggregates. This approach structures the product backlog and aligns microservice boundaries with domain events for clearer agile development.

Can I map Event Storming events directly to a sprint plan?▼

Yes, you can map Event Storming events directly to a sprint plan. The process structures requirements by transforming event clusters and actors into prioritized user stories complete with acceptance criteria for agile sprints.

How do you write non-functional requirements from event storming outcomes?▼

Write non-functional requirements from event storming outcomes by analyzing selected solutions and event artifacts. This translates architectural constraints into testable specifications that complement the generated user stories.

Does generating user stories from event storming support feature story mapping?▼

Generating user stories from event storming supports feature story mapping by structuring events and commands into a prioritized product backlog. This organizes requirements hierarchically for iterative sprint planning.