Jira / Linear Ticket Writer skill for Claude and Codex
Turns a rough idea or complaint into a well-scoped Jira or Linear ticket: imperative title, context, repro or user story, checklist acceptance criteria…
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
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.
What it will ask you for
- 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)
How it works
- 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.
- Write an imperative title and a context paragraph that says who is affected and why it matters.
- Turn the requirements into a checklist of observable acceptance criteria that a reviewer can pass or fail.
- List what is out of scope and every ambiguity as an open question rather than deciding it.
- Add a size estimate with its reasoning and the QA section if requested, formatted for the chosen tracker.
What you get
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.
What it watches out for
- 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.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.