Menu
Use when creating, drafting, or grooming a Linear or Superset ticket in this repo. Defines the canonical three-section structure.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create workspaces, spawn agents, schedule automations, and manage Superset projects/tasks/hosts via the `superset` CLI. Use to orchestrate coding agents across devices from the terminal.
Create a database migration with Drizzle on a fresh Neon branch. Use when changing the packages/db schema or generating migrations.
| name | ticket-format |
| description | Use when creating, drafting, or grooming a Linear or Superset ticket in this repo. Defines the canonical three-section structure. |
2–4 sentences. What's broken or wanted, and why. Outcome-focused, not solution-focused.
Where the ticket came from. Omit section if none.
| Source | Who | Link | Date |
|---|---|---|---|
| Slack #feedback | @alice | thread | 2026-05-10 |
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