create-user-stories

Break down product features into structured user stories with BDD acceptance criteria.

6|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-user-stories-jerelvelarde
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-user-stories
Source: https://github.com/jerelvelarde/chalk-skills/tree/main/skills/create-user-stories
Command: npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-user-stories-jerelvelarde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams need a structured, testable bridge from feature ideas to actionable work items. This Skill automates the creation of a story-map with persona-based user stories and Given/When/Then acceptance criteria, reducing planning time and miscommunication.

Core Features & Use Cases

  • Break a feature down into 3-7 high-level activities to form the backbone of a story map.
  • Generate 2-4 acceptance criteria per story using Given/When/Then format.
  • Create edge-case stories for errors, empty states, boundaries, and permissions.
  • Reference available product context (PRD, product profile) to ensure alignment with goals.

Quick Start

Describe a feature description or PRD to generate a complete user-story map with acceptance criteria.

Frequently Asked Questions about create-user-stories

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

FAQPage Schema
How do I break down product features into user stories with BDD acceptance criteria?

To break down features into user stories with BDD acceptance criteria, input your PRD or feature description to generate a structured story map organized by 3-7 high-level activities with Given/When/Then validation rules.

What is story mapping and how does it structure feature breakdown for QA?

Story mapping structures feature breakdown by organizing persona-based user stories into a backbone of high-level activities, ensuring each story includes Given/When/Then acceptance criteria and priority tags for QA-ready planning.

Can I use a PRD to generate edge-case user stories for empty states and permissions?

Yes, you can use a PRD to generate edge-case user stories. The system creates specific stories for error handling, empty states, boundary conditions, and permissions alongside the primary functional flow.

How do I write Given/When/Then acceptance criteria for multiple user stories?

Writing Given/When/Then acceptance criteria for multiple user stories is automated by generating 2-4 BDD conditions per story, applying persona-based statements mapped directly to the feature's high-level activities.

Does this user story generation approach work without a full product requirements document?

Yes, user story generation works without a full PRD. You can provide a direct feature request or product brief, and the system will reference available product context to align stories with goals.

What's the best way to tag user stories with priority and complexity for sprint planning?

The best way to tag user stories with priority and complexity for sprint planning is to map them against the generated story map backbone, applying the automated priority and complexity tags outputted with each story.