User Story & Acceptance Criteria Writer
Turn a feature idea into sprint-ready stories: specific role, real outcome, Given/When/Then criteria, out-of-scope, vertical splits.
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
Stories a developer can pick up without a meeting and a tester can verify without guessing. It fixes empty roles, solutions disguised as needs, vague criteria, and splits that ship nothing.
What it does
- Writes the story with a specific role and the outcome that actually matters
- Writes Given/When/Then acceptance criteria covering rules, empty states, errors, and permissions
- Checks readiness against INVEST and lists open questions before estimation
- Splits oversized stories into vertical slices using proven patterns, never by layer
- Marks unknown limits and values for confirmation instead of inventing them
What you get
A ticket-ready story with context, acceptance criteria, out-of-scope, dependencies, open questions, and a split plan when needed.
Best for
Product managers, product owners, and engineers turning requests into sprint-ready tickets.
SKILL.md preview
---
name: user-story
description: Turn a feature idea, request, or vague ticket into sprint-ready user stories - a specific role, a real outcome, testable acceptance criteria in Given/When/Then, explicit out-of-scope, dependencies, and a vertical split when it is too big - and flag the questions the team must answer before it can be estimated. Use when the user says "write a user story for this", "turn this into a Jira ticket", "add acceptance criteria", "this story is too big, split it", "is this story ready for sprint?", or casually "make this a ticket devs can pick up" or "write ACs for CSV export".
---
# User Story & Acceptance Criteria Writer
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Product Practice Diagnostic
Trace a product-team symptom (unused features, roadmap churn, priority fights) to the broken stage of the loop and fix one thing first.
Feature Launch Go-to-Market Plan
Plan one feature launch: tier, plan access, audience messages, readiness gates for support, sales, billing, and docs, and success metrics.
Pricing Tier and Packaging Diagnosis
Finds why your pricing tiers underperform and redesigns value metric, fences, price gaps, and upgrade triggers with a migration plan.
Product Specs, Roadmaps, and Research Decisions
Turn customer evidence into testable PRDs, dependency-aware roadmaps, and stakeholder updates with clear decisions and tradeoffs.