# Ticket Format

Canonical three-section structure for Linear and Paradev tickets in this repo.

- Repository: https://github.com/ParadevAI/Paradev (15823 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add ParadevAI/Paradev --skill ticket-format -g -a claude-code -y`
Codex: `npx skills add ParadevAI/Paradev --skill ticket-format -g -a codex -y`
Cursor: `npx skills add ParadevAI/Paradev --skill ticket-format -g -a cursor -y`
Gemini CLI: `npx skills add ParadevAI/Paradev --skill ticket-format -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add ParadevAI/Paradev`

## Description

Canonical three-section structure for Linear and Paradev tickets in this repo. Use when creating, drafting, or grooming a ticket.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Ticket Format

## Context
2, 4 sentences. What's broken or wanted, and why. Outcome-focused, not solution-focused.

## References
Where the ticket came from. Omit section if none.

| Source | Who | Link | Date |
|--------|-----|------|------|
| Slack #feedback | @alice | [thread](…) | 2026-05-10 |

## Implementation notes
Agent-groomed. Leave empty if you don't have codebase context; a later grooming pass will fill it in. When you do fill it in, use these sub-headings and skip what doesn't apply:

- `### Files`: `path:line` + why relevant
- `### Approach`: one paragraph
- `### Related code`: similar patterns in the repo
- `### Gotchas`: constraints, prior incidents