Linear Spec Ticket
Use when a Linear ticket has been groomed and now needs a design spec written onto it so work can start — drafts the spec from the ticket and the codebase and uploads it to the ticket as a file attachment. Also refreshes that attachment after /spec-review-codex hardens the spec. Never changes the ticket state. Triggers on: add a spec to this ticket, write the spec for NBS-123, deja el ticket listo para trabajar, añade spec al ticket, adjunta la spec al ticket, prepare this ticket for work, spec this ticket, refresh the spec attachment, re-upload the hardened spec, linear-spec-ticket.
Install
/plugin marketplace add adelrioj/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add adelrioj/claude-skills --skill linear-spec-ticketgit clone --depth 1 https://github.com/adelrioj/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/linear-spec-ticket ~/.claude/skills/linear-spec-ticketPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Add a Spec to a Linear Ticket Close the gap between *"ticket groomed"* and *"ticket with a reviewable spec"*: draft the spec and attach it to the ticket as a file. **The ticket's state is never touched** — advancing it is `/spec-to-symphony`'s job, and it advances it only after proving the spec is on the remote. **Two modes.** *Draft* (the default) writes the spec and attaches it. *Refresh* re-uploads the local spec file over the existing attachment after `/spec-review-codex` has hardened it. Refresh skips Steps 4–5 entirely and uploads what is on disk; everything else — both gates, the burst, the read-back proof — is identical. **Sibling skills, and the leg each one owns:** | Skill | Owns | |---|---| | `/linear-groom-ticket` | before: makes the ticket coherent | | **this skill** | the attachment, in both directions. No state change, no git writes | | `/spec-review-codex` | after: hardens the spec on disk — **this skill never runs it** | | `/spec-to-symphony` | after that: puts the spec on the remote, then advances the state | `/spec-to-symphony` used to be the near-twin that *created* a ticket for an existing spec. It no longer creates anything — it continues this skill's ticket. Nothing here creates a ticket either; that is `/to-linear`.
Details
- Skill name
linear-spec-ticket- Repository
- adelrioj/claude-skills
- Path
skills/linear-spec-ticket/SKILL.md- Repo updated
- 24 August 2026
FAQ
What does the Linear Spec Ticket skill do?
Use when a Linear ticket has been groomed and now needs a design spec written onto it so work can start — drafts the spec from the ticket and the codebase and uploads it to the ticket as a file attachment. Also refreshes that attachment after /spec-review-codex hardens the spec. Never changes the ticket state. Triggers on: add a spec to this ticket, write the spec for NBS-123, deja el ticket listo para trabajar, añade spec al ticket, adjunta la spec al ticket, prepare this ticket for work, spec this ticket, refresh the spec attachment, re-upload the hardened spec, linear-spec-ticket.
How do I install the Linear Spec Ticket skill?
Claude Code plugin: /plugin marketplace add adelrioj/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Linear Spec Ticket popular?
It lives in adelrioj/claude-skills, which has 5 GitHub stars and 0 forks.
Related skills
Architect Review PR
5adelrioj/claude-skills
Use after a feature is built — e.g. the final step of a ship-it run, right after review-pr — to check it is actually complete and wired, not just line-correct. Dispatches a fresh-context Claude subagent that traces the whole repo to hunt completeness and integration gaps in the branch's changes, reports ranked, evidence-backed findings, then fixes the CRITICAL ones and verifies with a fresh re-review (capped at 3 passes; pass report-only to skip fixing). Triggers on: architect review, architecture review, completeness review, wiring review, is this wired, did we finish this, find the gaps, inc
Blind Spot
5adelrioj/claude-skills
Use BEFORE starting work on a task to surface the unknown-unknowns you're about to walk into but can't see. Dispatches a fresh-context Claude subagent that hunts what you don't know you don't know about the codebase, the domain, and the decisions ahead, calibrated to your stated experience, then reports ranked, evidence-backed findings and fixes nothing. Triggers on: blind spot pass, blindspot, unknown unknowns, what don't I know, what am I missing, help me prompt better, I know nothing about, teach me my unknowns, before I start, de-risk this task, surface my blind spots.
Claude Md Slim
5adelrioj/claude-skills
Use when CLAUDE.md has grown bloated and is taxing every session's context — the inverse of claude-md-improver. Triages each block into session-invariant rules (stay always-on) vs feature/subsystem detail (page out to docs/ behind a plain-path pointer), moving — never deleting — the detail so nothing is lost and the always-on token bill drops. Triggers on: slim claude.md, minimal claude.md, claude.md is bloated, shrink claude.md, split claude.md, make claude.md minimal, page out claude.md, claude.md too long, reduce project memory, point claude.md to docs, trim claude md.
Linear Triage Ticket
5adelrioj/claude-skills
Use when a Linear ticket needs a priority, a complexity rating and an effort estimate backed by evidence from the code — reads the repo the ticket is about, runs two read-only codex analysts, and after your explicit approval writes the priority, the estimate (when provable) and one living rationale comment to Linear. Triggers on: triage this ticket, size NBS-123, prioritize this ticket, estimate this ticket, how big is this ticket, how urgent is this, triaje este ticket, prioriza el ticket, estima el esfuerzo, linear-triage-ticket.
Linear Groom Ticket
5adelrioj/claude-skills
Use when a Linear ticket needs to be made ready to work on, or judged not worth working on. Analyses one ticket across four dimensions — whether its claims hold in the code, whether it is complete against the team template, whether it duplicates another ticket, and whether it is implementable — then proposes a corrected description and applies it to Linear only after you approve. Triggers on: groom this ticket, prepare NBS-123, is this ticket ready, revisa este ticket, ¿este ticket está listo?, deja el ticket listo para trabajar, candidato a borrar, dedupe this ticket.
Plan to Dex
5adelrioj/claude-skills
Use when running an already-hardened Superpowers implementation plan through the dex orchestrator (codex backend). Triggers on: convert plan to dex, plan to dex, dex from plan, run plan with dex, plan-to-dex.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.