Spec to Symphony
Use when a groomed Linear ticket already carries its design spec and the build must be handed to a Symphony autonomous pipeline — puts the spec on the remote under the filename that deployment actually reads, then arms the existing ticket so the poller dispatches it. The ticket must already exist; this skill never creates one. Triggers on: hand off to symphony, hand the build to symphony, arm the pipeline, arm the ticket, spec to symphony, spec-to-symphony.
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 spec-to-symphonygit clone --depth 1 https://github.com/adelrioj/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/spec-to-symphony ~/.claude/skills/spec-to-symphonyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Spec-to-Symphony Handoff
Hand a finished design spec to a [Symphony](https://github.com/openai/symphony) pipeline: put the spec on the remote where the pipeline will look for it, then arm the existing ticket so the poller picks it up.
**This skill does not create tickets. It continues one.** By the time it runs, `/to-linear` filed the ticket, `/linear-groom-ticket` made it coherent, `/linear-spec-ticket` attached the spec, and `/spec-review-codex` hardened the file on disk. What is still missing is that the ticket is still parked and the spec is still only on the ticket — and that is this skill's job. An earlier revision created the ticket itself, from a premise ("no ticket exists yet") the ticket line no longer has: creating one here yields a second ticket for work that already has one, with the groomed ticket and the branch pointing at each other's absence. **No ticket at all ⇒ run `/to-linear` first**, then groom it, then come back.
**What is load-bearing here is the arming, not the push.** That is a change of emphasis worth stating plainly, because the skill was written when the push was the *only* way a spec could reach a pipeline:
- On a deployment that **cannot** read attachments, the push is still the sole delivery channel and everything downstream depends on it.Details
- Skill name
spec-to-symphony- Repository
- adelrioj/claude-skills
- Path
skills/spec-to-symphony/SKILL.md- Repo updated
- 24 August 2026
FAQ
What does the Spec to Symphony skill do?
Use when a groomed Linear ticket already carries its design spec and the build must be handed to a Symphony autonomous pipeline — puts the spec on the remote under the filename that deployment actually reads, then arms the existing ticket so the poller dispatches it. The ticket must already exist; this skill never creates one. Triggers on: hand off to symphony, hand the build to symphony, arm the pipeline, arm the ticket, spec to symphony, spec-to-symphony.
How do I install the Spec to Symphony 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 Spec to Symphony 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.
AWS Cloudwatch Investigation
9sandbaseai/workbuddy-skill
Use when investigating AWS incidents with CloudWatch Logs, Metrics, Alarms, CloudTrail, and Health evidence, correlating deployments, narrowing blast radius, reconstructing timelines, or testing metric anomalies.
Watch Rollout
9flurdy/agent-skills
Choose and launch the appropriate rollout watcher. Prompts between implemented deployment stacks unless an explicit selector is supplied, then delegates without weakening stack-specific safety.
AWS Cost Optimize
9sandbaseai/workbuddy-skill
Use when analyzing an authorized AWS workload's IaC, usage metrics, and costs to produce evidence-backed optimization recommendations.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.