user-story

Convert rough descriptions into spec-task user stories with acceptance criteria.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-kit --skill user-story-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-story
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/user-story
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill user-story-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Take rough descriptions and convert them into a fully fleshed out spec-task user story in chat — including As-a/I-want/So-that, scope, acceptance criteria, and references. The output is plain text only and does not write files, alter backlog, or assign a task ID.

Core Features & Use Cases

  • Generate a complete user story with As-a/I-want/So-that, Scope, Acceptance criteria, and References.
  • Enforce a no-file/write policy; outputs are chat-only for immediate review and iteration.
  • Surface assumptions when inputs are incomplete, enabling quick handoff to /task or /auto-task.

Quick Start

Provide a fleshed-out user-story draft from a rough idea.

Frequently Asked Questions about user-story

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

FAQPage Schema
How do I write a user story from a rough idea?

To write a user story from a rough idea, provide a brief description of your feature request. The tool converts it into a structured draft including As-a/I-want/So-that format, scope, acceptance criteria, and references for immediate review.

What is the standard format for user story acceptance criteria?

Acceptance criteria define the conditions a user story must meet to be considered complete. This tool automatically generates clear acceptance criteria alongside the As-a/I-want/So-that structure and scope based on your rough feature input.

Can I generate project-management user stories without creating files?

Yes, you can generate project-management user stories without creating files. The tool enforces a no-file write policy and outputs plain text directly in chat, ensuring nothing lands in your backlog and no task IDs are assigned.

How do I handle missing information when drafting product requirements?

When drafting product requirements with missing information, the tool surfaces assumptions explicitly within the generated output. This allows you to identify gaps in your rough idea quickly and iterate on the user story directly in chat.

What is the best way to turn a feature idea into a spec task?

The best way to turn a feature idea into a spec task is using a one-shot request command. The tool converts your raw text into a ready-to-use spec-task user story draft, covering the full scope and references needed for product planning.