User Story Writer
Turn a feature idea or requirement into a well-formed user story with clear acceptance criteria.
Before & after
Same prompt, same agent — the only difference is the skill.
Sure, I can help with that. A user story for payment would probably involve a user being able to upgrade their subscription. You'd want to capture what they're trying to do and why. Acceptance criteria are important to include. You might also want to think about different scenarios, like if their card declines or if they cancel midway. Here's a basic template you could adapt. Would you like me to focus on any particular payment gateway, or should I keep it generic?
USER STORY: Subscriber Upgrades to Annual Plan During Trial
AS A trial user seeing their 7-day trial expiring in 2 days
I WANT TO lock in an annual subscription at the trial discount rate
SO THAT I secure annual pricing before tier pricing resets to standard rates on day 30
ACCEPTANCE CRITERIA
• Annual plan shows $139/year (vs $179 standard); displays "Lock-in expires in 48 hours" countdown
• User clicks Upgrade → Stripe payment modal appears (no redirect, no context switch)
• On success: Subscription row created, webhook fires, "upgrade confirmed" email sent within 60s
• On card decline: User sees retry prompt ("expired card?") + option to use backup payment method or contact support
• On user cancels payment modal: Modal closes, discount offer remains (re-trigger in 24h if not claimed)
• Audit log shows upgrade source (trial_upgrade flow) for analytics
EDGE CASES
• Already on annual plan → skip upgrade flow; show upsell to Pro tier instead
• Card declines 3x → lock payment method for 30min, show "verify with your bank" message
• User in trial 1 day remaining, clicks upgrade → trial immediately ends, billing starts today
NON-FUNCTIONAL REQUIREMENTS
• Page load time <400ms (CDN-cached pricing, no backend call for display)
• Stripe SDK loaded async (doesn't block first paint)
• Support cancellation refunds for 48 hours post-upgrade only
About this skill
name: user-story description: Use when Structured Claude skill that gives Claude a repeatable workflow for user story.
User Story
One of 337+ skills in the original author's multi-agent claude-skills mega-collection (~19k GitHub stars). Packages the User Story workflow with its own instructions and validation so outputs stay consistent.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the user-story skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches User Story; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: user-story
description: Use this skill when a feature idea needs to be turned into a structured user story with acceptance criteria before development begins.
version: 1.0.0
category: AI Agents / Development
author: AgentVolt
license: proprietary
tags:
- ai-agents
- development
---
# User Story
Packages a repeatable workflow for turning a feature idea or requirement into a well-formed user story with clear acceptance criteria.
## When to use
… (sign up to view the full skill)More ai & agents skills
View all AI & Agents skills →Skill Status Report
Scan every skill in a project and report which pass validation, which are stale, and which lack required metadata.
Skills Scaffolder
Scaffold a new skills directory — folder structure, metadata, a baseline validation pass — with the right conventions from day one.
Research Bundle
Run a multi-step research task as one pipeline: gather sources, extract findings, validate consistency, emit one structured bundle.
Workspace Admin
Administer a Cowork or Claude workspace — settings, access, configuration — with every change scoped and verified.