write-user-story

Generates structured user stories with acceptance criteria and dependency diagrams for feature planning.

5|Updated Sep 9, 2017
One-click install
npx skills add https://github.com/hpcsc/dotfiles --skill write-user-story-hpcsc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-user-story
Source: https://github.com/hpcsc/dotfiles/tree/main/link/common/claude/.claude/skills/write-user-story
Command: npx skills add https://github.com/hpcsc/dotfiles --skill write-user-story-hpcsc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into implementable work items is slow and error-prone. This Skill converts a feature description into a complete set of small, verifiable user stories with clear scope boundaries, so developers or AI agents can start implementation without ambiguity. ## Core Features & Use Cases - Clarifying Questions: Asks targeted, lettered-option questions when the feature description is ambiguous, enabling quick answers like "1A, 2B". - INVEST-Compliant Stories: Decomposes features using the Elephant Carpaccio technique into thin vertical slices with 3-7 verifiable acceptance criteria each. - Dependency Visualization: Builds a Mermaid flowchart from the stories' Depends on fields, shading the critical path and naming the bottleneck in prose. - Use Case: Given a request like "Add rate limiting to our API", the Skill produces a Markdown document with an overview, goals, delivery-order diagram, sequenced stories, non-goals, and open questions saved to user-stories/api-rate-limiting.md. ## Quick Start Ask the assistant to write user stories for your feature, for example: write user stories for adding rate limiting to our public API.

Frequently Asked Questions about write-user-story

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

FAQPage Schema
How do I write user stories for a new feature?▼

Provide a feature description and the Skill asks tailored clarifying questions with lettered options, then generates INVEST-compliant stories with acceptance criteria, dependencies, and a delivery-order diagram saved to user-stories/[feature-name].md.

What makes a good user story for developers or AI agents?▼

A good story follows INVEST criteria: independent, negotiable, valuable, estimable, small, and testable. It should have 3-7 verifiable acceptance criteria describing observable behavior, plus optional context explaining why the story exists without prescribing how to build it.

How do I break down a large feature into smaller stories?▼

Apply the Elephant Carpaccio technique: slice the feature into the thinnest vertical slices that still deliver end-to-end user value. Stories with more than 7 acceptance criteria should be split; those with fewer than 2 may be too granular.

Can user stories include technical implementation details?▼

No. Stories must avoid implementation details, code examples, and architecture guidance. Acceptance criteria describe observable behavior only, though precise domain terminology is acceptable for inherently technical domains like APIs or infrastructure.

How are dependencies between user stories visualized?▼

Dependencies are drawn as a Mermaid flowchart built from each story's Depends on field, with arrows from prerequisite to dependent. The critical path is shaded, and prose explains the bottleneck and which stories must ship together.