user-story-generator

Generate Markdown user stories with hierarchical IDs from backlog items and codebase context.

1|Updated Mar 24, 2026

Search Tags:#markdown #codebase #requirements #backlog #generate #user-stories #story-writing

Ready to run

npx skills add https://github.com/gridi-ai/gridi-skills --skill user-story-generator-gridi-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: user-story-generator
Source: https://github.com/gridi-ai/gridi-skills/tree/main/skills/user-story-generator
Command: npx skills add https://github.com/gridi-ai/gridi-skills --skill user-story-generator-gridi-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

backlog items often lack concrete, implementation-grounded user stories, causing misalignment between product intent and development work. This skill analyzes backlog items and current code context to produce clear, Markdown-formatted user stories that can be used directly by developers and product teams.

Core Features & Use Cases

Generate hierarchical user stories with IDs (US-001, US-002, etc.) based on backlog items.
Tailor stories to the codebase context by extracting relevant entities and workflows.
Output to a standardized location: docs/{backlog-keyword}/user-stories.md with consistent formatting and a recommended structure.

Quick Start

Provide backlog items to the system and it will generate codebase-informed user stories saved under docs/{backlog-keyword}/user-stories.md.

Frequently Asked Questions about user-story-generator

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

FAQPage Schema

How do I generate user stories from a backlog?▼

To generate user stories from a backlog, provide your backlog items to the system so it can analyze them alongside codebase context to produce structured, Markdown-formatted stories with sequential IDs saved directly to your project documentation.

What is the best way to write requirements documentation that aligns with my codebase?▼

Writing requirements documentation that aligns with your codebase is best achieved by analyzing backlog items and extracting relevant code entities to produce hierarchical user stories, ensuring product intent matches development workflows.

Can I automatically format user stories in Markdown for my software project?▼

Yes, you can automatically format user stories in Markdown. The system analyzes backlog inputs and outputs consistent, maintainable Markdown files to a standardized location within your project documentation directory.

How do I structure user stories with sequential IDs for backlog analysis?▼

To structure user stories with sequential IDs for backlog analysis, the system processes your backlog items and assigns hierarchical identifiers like US-001 and US-002 to maintain clear storytelling and organization across your software project.

Does generating user stories require manual codebase context extraction?▼

Generating user stories does not require manual codebase context extraction. The system automatically analyzes your provided backlog items and current code context to tailor each story without needing manual entity mapping.

Where should I save generated user stories to maintain consistent formatting?▼

You should save generated user stories to maintain consistent formatting in a standardized location, specifically outputting the Markdown file as docs/{backlog-keyword}/user-stories.md within your project repository.