---
name: jira-linear-ticket-writer
description: "Turns a rough idea or complaint into a well-scoped Jira or Linear ticket: imperative title, context, repro or user story, checklist acceptance criteria, out-of-scope notes, and a sized estimate with ambiguities flagged. Use when a rough idea, complaint, or half-formed requirement needs writing up as a Jira or Linear ticket with acceptance criteria an engineer can pick up cold. Do not use for triaging severity of an incoming bug report or planning a whole sprint. Related topics: Engineering, Productivity, Planning."
---

# Jira / Linear Ticket Writer

Turns a rough idea or complaint into a well-scoped Jira or Linear ticket: imperative title, context, repro or user story, checklist acceptance criteria, out-of-scope notes, and a sized estimate with ambiguities flagged.

## When to use

Use this skill when a rough idea, complaint, or half-formed requirement needs writing up as a Jira or Linear ticket with acceptance criteria an engineer can pick up cold. Do not use it for triaging severity of an incoming bug report or planning a whole sprint.

## 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. Choose the ticket body shape from the type: repro steps for a bug, user story for a feature, cost of delay for a chore, a question and timebox for a spike.
3. Write an imperative title and a context paragraph that says who is affected and why it matters.
4. Turn the requirements into a checklist of observable acceptance criteria that a reviewer can pass or fail.
5. List what is out of scope and every ambiguity as an open question rather than deciding it.
6. Add a size estimate with its reasoning and the QA section if requested, formatted for the chosen tracker.

## Inputs

- **Tracker** (choose one: Jira, Linear, GitHub Issues, Asana, Generic)
- **Ticket type** (choose one: Bug, Feature, Chore or tech debt, Spike or investigation)
- **The rough idea** (longer free text)
- **Affected area** (free text, e.g. "Service or screen or component")
- **Priority** (choose one: Urgent, High, Medium, Low)
- **Include a QA and test plan section** (choose one: Yes, No)

## Output

A ticket with title, context, repro steps or user story, an acceptance criteria checklist, out of scope, open questions, a sized estimate with reasoning, and an optional test plan.

## Prompt template

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

### Jira / Linear Ticket Writer

Turn this into a ticket an engineer can pick up without asking me anything.

- Tracker: {{Tracker}}
- Ticket type: {{Ticket type}}
- The rough idea: {{The rough idea}}
- Affected area: {{Affected area}}
- Priority: {{Priority}}
- Include a QA and test plan section: {{Include a QA and test plan section}}

Write the title in the imperative mood and under about ten words. Add a short context paragraph on why this matters and who is affected. For a bug, give numbered steps to reproduce with expected and actual results; for a feature, a user story; for a chore, the current cost of leaving it; for a spike, the question to answer and a timebox. Write acceptance criteria as a checklist of observable, testable statements, each of which a reviewer can tick or fail. Add an out-of-scope list to stop scope creep. Give a rough size estimate with the reasoning behind it. Where a requirement is ambiguous, list it under Open questions instead of inventing a decision. Format for the chosen tracker.

## Pitfalls

- Writing acceptance criteria like "works well" that no reviewer can fail.
- Quietly choosing an answer to an ambiguous requirement, which the engineer then builds as if it were agreed.
- Bundling two changes into one ticket, so the estimate is meaningless and the review drags.
