---
name: issue-writer
description: "Turn a rough bug or feature note into a well-formed ticket ready for Jira, Linear, or GitHub."
allowed-tools: ["Read", "Write"]
output: "markdown ticket"
targets: "jira / linear / github"
---

# Issue & Ticket Writer

## Musts

- Write a specific, searchable title that names the component and the problem.
- Include context: what was being done, environment, and version when stated.
- For bugs, give numbered repro steps plus expected vs actual behaviour.
- For features, state the user story and testable acceptance criteria.
- Mark any missing detail as a TODO or unknown rather than inventing it.

## Guidelines

- Keep repro steps minimal and deterministic — the fewest steps that trigger it.
- Write acceptance criteria as checkable statements, not vague goals.
- Only include sections that apply to the ticket type; drop the rest.

## Output format

```
## Title
<component>: <concise problem or request>

## Context
<what was happening, environment, version — or "unknown">

## Steps to reproduce
1. <step>
2. <step>

## Expected vs actual
- Expected: <what should happen>
- Actual: <what happens>

## Acceptance criteria
- [ ] <testable condition>
```