AugmentClaude

Ticket Format

Format Linear or Superset tickets with a standardized three-section structure.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/ticket-format-superset-sh/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Use when creating, drafting, or grooming a Linear or Superset ticket in this repo. Defines the canonical three-section structure.

What this skill does

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.

SourceWhoLinkDate
Slack #feedback@alicethread2026-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:

  • ### Filespath:line + why relevant
  • ### Approach — one paragraph
  • ### Related code — similar patterns in the repo
  • ### Gotchas — constraints, prior incidents

Related skills