Issue & Ticket Writer
Turns a rough bug or feature note into a well-formed ticket — title, context, repro steps, expected vs actual, and acceptance criteria — ready for Jira, Linear, or GitHub.
What this skill does
Key features
- Writes a specific, searchable title
- Structures context, repro steps, and expected vs actual
- Adds testable acceptance criteria for features
- Marks missing details as unknown instead of inventing them
Use cases
- Filing a bug from a quick note or chat message
- Turning a feature idea into an actionable ticket
- Standardising ticket quality across a backlog
SKILL.md
The skill definition — its metadata and the exact instructions an agent follows. Copy it into a SKILL.md file in your agent's skills folder.
| 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 |
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>FAQ
What if the note is missing repro steps or version info?
It leaves a clearly marked TODO or 'unknown' placeholder for each missing field instead of guessing. That way the ticket shows exactly what still needs gathering rather than shipping fabricated steps.
Does it handle both bugs and feature requests?
Yes. Bugs get repro steps and expected vs actual; features get a user story and acceptance criteria. It picks the right shape from the note and keeps only the sections that apply.
Before running any skill, read its instructions and the tools it's allowed to use, and test it on a safe target first. See LLM security best practices.