---
name: paradevai-ticket-format
description: "Canonical three-section structure for Linear and Paradev tickets in this repo. Use when creating, drafting, or grooming a ticket."
license: "NOASSERTION"
metadata:
  decimalai-skill-id: "33181e05-03d7-4fac-9ce5-c73dc3d68a25"
  decimalai-version-id: "4c747ebb-893b-4f5d-a44c-c7d446c3c501"
  decimalai-version: "1"
  decimalai-body-sha256: "91d28de38d014ef266d32d327abd226afd5f6b8d5e411ee4de2f042a6ed6e565"
  decimalai-name: "paradevai/ticket-format"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "productivity"
  decimalai-source: "https://app.decimal.ai/s/paradevai-ticket-format@1/SKILL.md"
---
# 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