Writing User Stories Skill for Claude
Use when an agent needs to write user stories for a project
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/nicepkg/ai-workflow --skill writing-user-storiesThe instruction itself
5 sections, as written by the authorWriting User Stories
Overview
Help Claude and subagents write properly formatted user stories for task definition.
Core principle: User stories are formulaic ways of expressing user requirements. They identify the perosna of the actor, what they want to do, and what benefit are they hoping to gain from their actions.
When to Use This Skill
Use this skill when:
- You are asked to write a user story
- You are asked to plan a feature
User Story Format
As a PERSONA
I want to DESCRIPTION_OF_ACTION
So that DESCRIPTION_OF_BENEFIT.
Examples
As a non-technical stakeholder,
I want to understand what changed in a release without reading code diffs
so that I can communicate updates to customers effectively.
As a new user,
I want to see examples of AI-generated code before connecting my repository
so that I understand the value proposition before committing to integration.
As a home cook,
I want to see that recipes have been tested by professional chefs
so that I can know whether they are worth trying.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
How to use it
Take nicepkg/writing-user-stories from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.