rampstackco/claude-skills / skills/ticket-authoring
ticket-authoring
VerifiedWrite complete, ready-to-pull work items for an issue tracker: bugs, tasks, stories, spikes, and epics, each with the fields, attachments, and done test its type requires. Use this skill whenever the user wants to write a ticket, create a Jira issue, Linear issue, or GitHub issue, file a bug report, write a user story or acceptance criteria, scope a spike, open an epic, or break work into tasks. Triggers on write a ticket, create an issue, file a bug, bug report, user story, spike, epic, task breakdown, turn this into tickets, break this down, acceptance criteria, definition of ready, ready for dev, backlog item, capitalization stage. Also triggers when the user pastes a PRD, a spec, or a bug description and asks what to do with it, even if they never say the word ticket.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 357 B |
| SKILL.md | skill md | 10.2 KB |
| references/bug-template.md | markdown | 3.9 KB |
| references/capitalization-guide.md | markdown | 5.8 KB |
| references/definition-of-ready-checklist.md | markdown | 3.3 KB |
| references/epic-template.md | markdown | 2.4 KB |
| references/example-bug-and-story.md | markdown | 5.8 KB |
| references/spike-template.md | markdown | 2.3 KB |
| references/story-template.md | markdown | 2.8 KB |
| references/task-template.md | markdown | 2.7 KB |
references/definition-of-ready-checklist.md
View on GitHub# Definition of Ready Checklist
Run the section for the ticket's type before it enters a sprint. Every box should be checked or explicitly marked "none" with a reason. An unchecked box is a question someone will ask mid-sprint.
---
## All types
- [ ] Title is specific enough to find in search
- [ ] Type is set and matches the work
- [ ] Owner is one name, or the ticket is explicitly unassigned for pull
- [ ] Parent link is set, or "none" is deliberate
- [ ] Capitalization stage is set (inherited or overridden with a reason), if the team capitalizes
- [ ] No pasted spec text. The spec is linked.
---
## Bug
- [ ] Title follows `[area] [symptom] when [trigger]`
- [ ] Repro steps are numbered, one action per step, from a known starting state
- [ ] Reproduction rate is stated (every time, N of M, once)
- [ ] Environment lists build, device or browser, account type, and data state
- [ ] Observed and expected are separate lines
- [ ] Current test result is stated (failing test name, or "no test covers this")
- [ ] Severity and priority are set as separate fields
- [ ] Regression risk names the code paths that share this behavior
- [ ] QA notes list edge cases beyond the repro
- [ ] Fix verification method names a specific test or numbered steps
- [ ] Expected test result after the fix is stated in observable terms
- [ ] A screenshot, recording, or log excerpt is attached
---
## Task
- [ ] Task spec says what changes in plain language
- [ ] Parent story is linked, or "none" is deliberate
- [ ] Touches list names files or modules, services, flags, tables, and config
- [ ] "Does not touch" names nearby things that must stay unchanged
- [ ] Estimate is set
- [ ] Screenshots of the affected area are attached, if user-visible
- [ ] QA notes are present
- [ ] Definition of done lists observable outcomes, not "done" and "tested"
- [ ] Task fits in one to two days, or it has been split
---
## Story
- [ ] User story statement names a specific user, an action, and an outcome
- [ ] Spec or PRD is linked
- [ ] Every acceptance criterion is checkable by someone other than the author
- [ ] Empty, error, and permission states are covered by criteria
- [ ] Non-goals are listed
- [ ] Designs are attached or linked, or "none" is deliberate
- [ ] Analytics events are named with trigger and properties, or "none" is deliberate
- [ ] Feature flag is named with default state, or "none" is deliberate
- [ ] QA notes are present
- [ ] Estimate is set and fits within one sprint
---
## Spike
- [ ] Question is one sentence ending in a question mark
- [ ] Why-now names the decision this unblocks
- [ ] Timebox is set in days, with a hard stop date
- [ ] Exit criteria define what counts as an answer
- [ ] Resources, services, and platforms to evaluate are listed
- [ ] Competitor or prior-art examples are listed, or "none" is deliberate
- [ ] Output artifact is a decision memo with a named location
- [ ] Capitalization stage is preliminary, or the override is explained
---
## Epic
- [ ] Date opened is set
- [ ] Goal is one sentence
- [ ] Success metric has a baseline, a target, and a measurement date
- [ ] Kill criteria are observable, dated, and owned
- [ ] Owner is one name
- [ ] Roadmap fitment names the quarter and the objective
- [ ] Scope in and scope out are listed
- [ ] Capitalization stage is set, with the date it last changed
- [ ] At least one child story or spike exists
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |