---
name: user-story-acceptance-criteria-writer
description: "A Jira-ready ticket for one feature: a clear story, testable acceptance criteria in your chosen format, and the edge cases, scope limits, and dependencies engineers ask about. Use when a product owner or developer needs one feature written up as a single ready-to-paste Jira or Trello ticket. Do not use for splitting a large epic into many stories or full product specifications. Related topics: product, agile, management."
---

# User Story & Acceptance Criteria Writer

A Jira-ready ticket for one feature: a clear story, testable acceptance criteria in your chosen format, and the edge cases, scope limits, and dependencies engineers ask about.

## When to use

Use this skill when a product owner or developer needs one feature written up as a single ready-to-paste Jira or Trello ticket. Do not use it for splitting a large epic into many stories or full product specifications.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Write a verb-first ticket title and the story in the chosen format for the stated role.
3. List acceptance criteria as single testable statements, happy path first, done when each can pass or fail.
4. Add the chosen sections (edge cases, out of scope, dependencies) under their own headings.
5. Include technical notes only if requested and label them as suggestions, not requirements.
6. Flag any unclear point that would block estimation.

## Inputs

- **Feature** (longer free text)
- **Target user role** (free text, e.g. "Registered customer")
- **Story format** (choose one: As a role I want a goal so that a benefit, Given When Then)
- **Sections to include** (choose any: Acceptance criteria, Edge cases, Out of scope, Dependencies)
- **Technical implementation notes** (choose one: Yes, No)

## Output

One ticket with a title, the story, acceptance criteria, the chosen extra sections, and a list of open questions.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Jira-Ready Story Ticket

Write a ticket for the feature below.

- Feature: {{Feature}}
- Target user role: {{Target user role}}
- Story format: {{Story format}}
- Sections to include: {{Sections to include}}
- Technical implementation notes: {{Technical implementation notes}}

Write one ticket with a short title that starts with a verb, then the story in the chosen format. Make each acceptance criterion a single testable statement with a pass or fail outcome, and cover the happy path first. Add the requested sections under clear headings. Edge cases cover empty input, expiry, repeated attempts, and permissions. Out of scope names things a reader might assume are included. If technical notes are on, keep them to suggestions on approach and risks, clearly labelled as not requirements. End by flagging any unclear point that blocks estimation.

## Pitfalls

- Writing criteria that describe implementation instead of observable behaviour.
- Bundling several features into one ticket, which makes it impossible to estimate.
- Mixing technical notes into the criteria so they read as requirements.
