---
name: jira-ticket-refinement
description: When the user shares a Jira ticket and wants to refine it before implementing. Produces a REFINEMENT-*.md with plan, context, and acceptance criteria.
---

# Jira ticket refinement — workflow

When the user shares a **Jira ticket** (issue + expected behavior) or asks to **refine** a ticket, follow this workflow. Do not skip to implementation until refinement is agreed.

## 1. Refinement first

- If there is **no** refinement document yet: use the **refine-jira-ticket** skill (`.cursor/skills/refine-jira-ticket/SKILL.md`) to produce `.refinements/REFINEMENT-<ticket-number>.md`.
- Before producing the refinement, **read all project rules** in `.cursor/rules/` (conventions, workflows) and ensure the plan follows them.
- Do **not** start implementing until the user has seen and (optionally) adjusted the plan.

## 2. References

- Refinement doc structure: `.cursor/templates/REFINEMENT-TEMPLATE.md`
- Skill to generate the first draft: **refine-jira-ticket** (see `.cursor/skills/refine-jira-ticket/SKILL.md`)
- Once the plan is approved, implementation follows the **jira-ticket-implementation** workflow (`.cursor/rules/workflows/jira-ticket-implementation.mdc`).
