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/story-template.md
View on GitHub# Story Template
A story delivers one outcome a user can see or feel. It links to the spec rather than restating it, and it carries acceptance criteria that someone other than the author can check.
If no spec exists yet and the story is larger than a few days of work, write the spec first with `pm-spec-writing`.
---
## Template
```
TITLE: [user-facing outcome, in a few words]
TYPE: Story
OWNER: [one name, or unassigned]
PARENT EPIC: [link]
LABELS: [component, platform, segment]
CAPITALIZATION STAGE: [inherited from epic, or override with a note]
ESTIMATE: [points]
USER STORY
As a [specific user], I want [action], so that [outcome].
SPEC
[Link to the PRD or spec section. Do not paste it.]
ACCEPTANCE CRITERIA
- [ ] Given [context], when [action], then [observable outcome]
- [ ] Given [context], when [action], then [observable outcome]
- [ ] Given [context], when [action], then [observable outcome]
NON-GOALS
- [What this story does not do, even though someone might expect it]
- [What this story does not do]
DESIGNS
- [Wireframe or mockup link or screenshot, or none]
ANALYTICS EVENTS
| Event name | Trigger | Properties |
|---|---|---|
| [object_action] | [when it fires] | [property: type] |
FEATURE FLAG
[flag name, default state, rollout plan, or none]
QA NOTES
- [States to test: empty, error, loading, long content]
- [Platforms or roles to cover]
- [Regression areas]
DEFINITION OF DONE
- [ ] Every acceptance criterion checked by someone other than the author
- [ ] Analytics events verified firing with correct properties
- [ ] Flag default confirmed in each environment
```
---
## Writing acceptance criteria that can be checked
Each criterion should pass a simple test: could two people check it independently and agree?
| Not checkable | Checkable |
|---|---|
| Search is fast | Given a workspace with 10,000 records, when the user types 3 characters, then results render within 1 second |
| The form is user-friendly | Given an invalid email, when the user leaves the field, then an inline error names the problem |
| Works on mobile | Given a 375px wide viewport, when the user opens the page, then no content scrolls horizontally |
Cover the empty state, the error state, and the permission boundary. Those are the three most often forgotten.
---
## Writing non-goals
Non-goals stop scope creep in review. Write the ones a reasonable reviewer might assume are included.
- "Does not add bulk edit. Single-record edit only."
- "Does not change the email notification. That is a separate story."
- "Does not support the legacy mobile app."
---
## Naming analytics events
Use one convention across the product. A common one is `object_action` in snake case, past tense: `report_exported`, `invite_sent`. Define each property and its type. If the team runs a tracking plan, link the row instead of redefining it.
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 |