ticket-authoringlisted
Install: claude install-skill rampstackco/claude-skills-pm
# Ticket Authoring
Turn specs, bug reports, and loose requests into work items someone can pull and start without asking a question. Tracker-agnostic: works in Jira, Linear, GitHub Issues, or your tracker of choice.
---
## When to use
- Turning a PRD or spec into a set of tickets
- Filing a bug that someone else will fix
- Writing a user story with checkable acceptance criteria
- Scoping a spike so it ends in a decision, not a shrug
- Opening an epic with a goal, a metric, and a way to kill it
- Auditing a backlog for tickets that are not ready to pull
- Tagging work items with a capitalization stage for finance
## When NOT to use
- Writing the PRD or spec itself (use `pm-spec-writing`)
- Deciding what ships this quarter (use `roadmap-planning`)
- Running sprint ceremonies or measuring the team (use `sprint-operations`)
- Writing up what went wrong after the fact (use `after-action-report`)
- Handing a whole plan to a coding agent to execute unattended (use `dispatch-authoring`)
---
## Required inputs
- The source material: a spec, a bug description, a request, or a conversation
- The ticket type, or enough context to pick one
- The tracker's field set, if it has required custom fields
- The parent epic or story, if one exists
- The capitalization policy, if the team capitalizes software development
If the source is vague, ask before writing. A ticket written around a guess becomes a second ticket later.
---
## The framework: five types, one definition of ready ea