New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cy Issue To Spec

by compozy in compozy/compozy

Publishes a Compozy spec set to compozy-specs and mirrors it into a GitHub + Linear issue pair — or starts from a bare issue and authors the spec first.

MITAuto-check passedDevelopment

Install Cy Issue To Spec

skills CLI
$ npx skills add compozy/compozy --skill cy-issue-to-spec -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install compozy/compozy cy-issue-to-spec --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/compozy/compozy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cy-issue-to-spec .claude/skills/cy-issue-to-spec && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cy-issue-to-spec
GitHub stars
2.8k
Token cost
~1.3k tokens
SKILL.md length
669 words
Files
4 (incl. scripts, references)
Skills in repo
47
Repo updated
First seen
Licence
MIT

At a glance

Publishes a Compozy spec set to compozy-specs and mirrors it into a GitHub + Linear issue pair — or starts from a bare issue and authors the spec first.

  • Works in 6 steps: Author the spec → Stage the spec set → Resolve the report → …
  • Tasks that involve Spec-driven development
  • SKILL.md covers Branches, Step 0 — Author the spec, Step 1 — Stage the spec set and Step 2 — Resolve the report, plus 4 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Cy Issue To Spec is an agent skill from compozy/compozy. Publishes a Compozy spec set to compozy-specs and mirrors it into a GitHub + Linear issue pair — or starts from a bare issue and authors the spec first.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/issue-body.md`, `scripts/check-tracker-sync.py` and `scripts/publish-spec.py`).

It sits in Development, covering Spec-driven development. It works with GitHub and Linear. The repository describes itself as: An operating system for AI agents. Plug in the agent CLIs you already use (Claude Code, Codex, Gemini CLI, Cursor) and they become a team: they split the work, hand tasks to each… The licence is MIT.

When your agent uses it

  • Tasks that involve Spec-driven development

Example prompts

  • “Use the cy-issue-to-spec skill to publish a Compozy spec set to compozy-specs and mirrors it into a GitHub + Linear issue pair — or starts from a…”
  • “/cy-issue-to-spec”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Author the spec
  2. Stage the spec set
  3. Resolve the report
  4. Index and push
  5. Write the issue body
  6. Open the mirror

What it can do on your machine

Read from SKILL.md and the folder at commit c15729c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cy Issue To Spec loads about 1.3k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 42 tokens; SKILL.md has 669 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~42
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from compozy/compozy at commit c15729c, republished under its MIT licence (© compozy). 669 words, ~1,274 tokens.

Download SKILL.mdSave it as .claude/skills/cy-issue-to-spec/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
cy-issue-to-spec
description
Publishes a Compozy spec set to compozy-specs and mirrors it into a GitHub + Linear issue pair — or starts from a bare issue and authors the spec first.
disable-model-invocation
true
argument-hint
[spec slug or issue number]

Issue ↔ Spec

One feature lives in three places: the working spec set under .compozy/tasks/<slug>/, its published folder in the compozy/compozy-specs repo, and its mirror — a GitHub issue and a Linear issue that read identically. This skill moves a feature between those places and leaves all three agreeing.

Branches

Starting pointEnter at
A spec set already exists under .compozy/tasks/<slug>/Step 1
A GitHub issue exists carrying no spec behind itStep 0

Step 0 — Author the spec

Only when starting from a bare issue.

Read the issue and restate its scope in one sentence. When it bundles separable features, split it first: retitle the original to the narrower scope, open a second issue for the remainder, and cross-link both — then spec one of them.

Activate cy-spec-preflight, then cy-create-spec. Offer cy-spec-peer-review after the user approves the spec. Run cy-create-tasks last.

Done when: .compozy/tasks/<slug>/ holds _spec.md (or _prd.md + _techspec.md), its companions, adrs/, and _tasks.md, and the user has approved the spec.

Step 1 — Stage the spec set

Run the staging helper (mutating — writes into the specs repo working tree):

bash
python3 .agents/skills/cy-issue-to-spec/scripts/publish-spec.py \
  --spec-dir .compozy/tasks/<slug> \
  --specs-repo <specs-repo-checkout> \
  --repo-root "$(pwd)"

It publishes _*.md, task_NN.md, and adrs/*.md; it leaves analysis/, qa/, memory/, evidence/, reviews-*/, state.yaml, and handoff notes in the workspace. Pass --include '<glob>' for a document that carries spec content under a name outside those patterns, and --archived when the workstream is already closed.

The folder is named YYYY-MM-DD-<slug>, dated by when the work began: the source folder's own date prefix when it carries one, else state.yaml's created_at, else the earliest document. Active specs sit at the repo root; closed ones under _archived/.

Done when: the helper exits 0, reporting the staged path, file count, and a clean scan.

Step 2 — Resolve the report

The helper scrubs machine-local paths and repairs ../adrs/ links itself. Two findings need a decision:

  • A surviving local path or a possible secret exits the helper non-zero. Edit the staged document, then re-run the scan.
  • A broken relative link points at something the filter left behind. Either publish that material too, or accept the dangling reference — the repo README already tells readers that older documents point at files they will not find.

Done when: every reported path, secret, and link is fixed or consciously accepted.

Step 3 — Index and push

Add one row to the specs repo README.md, in the Active or Archived table: the folder link, one sentence on what the spec covers, the tracking-issue link, and the Documents column naming its shape (spec, prd + techspec, brief + techspec, …). Newest first.

Commit as docs: add <slug> spec set and push.

Done when: every relative link in the README resolves and the commit is on main.

Show full SKILL.md (233 more words)Show less

Step 4 — Write the issue body

Read .agents/skills/cy-issue-to-spec/references/issue-body.md in full and build the body against it.

Done when: the body opens with the spec-set link block and every section of the skeleton is either written or deliberately absent.

Step 5 — Open the mirror

Create or update the GitHub issue: title matching the spec's subject, labels roadmap + planned (removing needs-plan), the Step 4 body, and a closing Roadmap item tracked in Linear: [CY-NNN](…) line.

Create or update the Linear issue with the same title and the same body, swapping the footer for Tracked on GitHub: <url>. Linear renders GitHub callout syntax as plain text — convert a > [!NOTE] block to a bold sentence.

Verify with the audit helper (read-only):

bash
python3 .agents/skills/cy-issue-to-spec/scripts/check-tracker-sync.py --linear-json <export>

Save the Linear MCP list_issues result to a file first; without --linear-json the helper audits only the GitHub half.

Done when: the helper exits 0 with no defects, and both issues carry a link to each other.

Reference

  • Publishing an already-archived spec skips Step 0 and Step 4's tracking link when no issue exists — the README row is then the only index entry.
  • Renaming a published folder breaks the links already sitting in both trackers; update the issue bodies in the same change.
  • references/issue-body.md — the issue-body skeleton and where each part comes from in the spec.
  • scripts/publish-spec.py — mutating; stages, scrubs, scans, and link-checks a spec set.
  • scripts/check-tracker-sync.py — read-only; audits titles, states, and links across the mirror.

© compozy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in .agents/skills/cy-issue-to-spec of compozy/compozy.

  • SKILL.md
  • references/issue-body.md
  • scripts/check-tracker-sync.py
  • scripts/publish-spec.py

Open the folder on GitHubat commit c15729c

Compare with similar skills

Cy Issue To Spec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cy Issue To Spec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cy Issue To Spec this skillcompozy/compozy2.8k—~1.3kAutomated safety check: PassMIT
Draft Pull Request Creatorwordpress-mobile/WordPress-Android3.2k—~881Automated safety check: NotesGPL-2.0
Review Spdzhu1090093659/spec_driven_develop985—~1.5kAutomated safety check: PassMIT
React Router RFC Implementerremix-run/react-router57k—~2.3kAutomated safety check: PassMIT
Spec Driven Developzhu1090093659/spec_driven_develop985—~5.1kAutomated safety check: PassMIT
SddSpillwaveSolutions/sdd-skill106—~5.7kAutomated safety check: PassMIT

Similar skills

  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated today
    DevelopmentAuto-check: notes

  • Review Spd

    zhu1090093659/spec_driven_develop

    Findings-first code review workflow for AI coding agents. An agent skill from zhu1090093659/spec_driven_develop.

    985 GitHub stars~1.5k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • React Router RFC Implementer

    remix-run/react-router

    Turns a React Router RFC discussion on GitHub into an implementation, weighing community feedback and settling open questions with you before coding.

    57k GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Spec Driven Develop

    zhu1090093659/spec_driven_develop

    Automates pre-development workflow for large-scale complex tasks.

    985 GitHub stars~5.1k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • Sdd

    SpillwaveSolutions/sdd-skill

    This skill should be used when users want guidance on Spec-Driven Development methodology using GitHub's Spec-Kit.

    106 GitHub stars~5.7k tokensUpdated 10 mo ago
    DevelopmentAuto-check passed

  • Speckit Taskstoissues

    kunstmusik/blue

    Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

    154 GitHub starsUsed in 17 repos~2k tokens
    DevelopmentAuto-check passed

More from compozy/compozy

All 47 skills in this repo

  • Eng Real Scenario QA

    compozy/compozy

    Dogfoods Compozy through an autonomous startup scenario with live providers, cross-surface observation, and strict evidence audit.

    2.8k GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Eng Test Conventions

    compozy/compozy

    Go test-shape discipline for Compozy. An agent skill from compozy/compozy.

    2.8k GitHub stars~467 tokensUpdated today
    Auto-check passed

  • Assistant UI

    compozy/compozy

    Guide for assistant-ui library - AI chat UI components. An agent skill from compozy/compozy.

    2.8k GitHub stars~958 tokensUpdated today
    Auto-check passed

  • Assistant UI Primitives

    compozy/compozy

    Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive.

    2.8k GitHub stars~999 tokensUpdated today
    Auto-check passed

  • Assistant UI Runtime

    compozy/compozy

    Guide for assistant-ui runtime system and state management. An agent skill from compozy/compozy.

    2.8k GitHub stars~856 tokensUpdated today
    Auto-check passed

  • Assistant UI Streaming

    compozy/compozy

    Guide for assistant-stream package and streaming protocols. An agent skill from compozy/compozy.

    2.8k GitHub stars~813 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Cy Issue To Spec

What does Cy Issue To Spec do?

Publishes a Compozy spec set to compozy-specs and mirrors it into a GitHub + Linear issue pair — or starts from a bare issue and authors the spec first. Cy Issue To Spec is an agent skill from compozy/compozy. Publishes a Compozy spec set to compozy-specs and mirrors it into a GitHub + Linear issue pair — or starts from a bare issue and authors the spec first.

When should I use Cy Issue To Spec?

Cy Issue To Spec fits situations like: tasks that involve Spec-driven development.

How do I install Cy Issue To Spec in Claude Code?

Run `npx skills add compozy/compozy --skill cy-issue-to-spec -a claude-code`. Or copy the skill folder (.agents/skills/cy-issue-to-spec in compozy/compozy) into .claude/skills/cy-issue-to-spec in your project. Claude Code loads it when a task matches its description.

How do I install Cy Issue To Spec in Codex?

Run `npx skills add compozy/compozy --skill cy-issue-to-spec -a codex`. Or copy the skill folder (.agents/skills/cy-issue-to-spec in compozy/compozy) into .agents/skills/cy-issue-to-spec in your project. Codex loads it when a task matches its description.

Can I use Cy Issue To Spec in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add compozy/compozy --skill cy-issue-to-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cy-issue-to-spec, .gemini/skills/cy-issue-to-spec, .github/skills/cy-issue-to-spec and .opencode/skills/cy-issue-to-spec in your project.

What does Cy Issue To Spec need to run?

Going by SKILL.md and its folder, Cy Issue To Spec needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Cy Issue To Spec access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cy Issue To Spec safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Cy Issue To Spec use?

Cy Issue To Spec is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cy Issue To Spec use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 843 tokens, read only when the agent opens those files.

What are the alternatives to Cy Issue To Spec?

Skills that share tags, products or a category with Cy Issue To Spec: Draft Pull Request Creator (wordpress-mobile/WordPress-Android, 3.2k stars), Review Spd (zhu1090093659/spec_driven_develop, 985 stars), React Router RFC Implementer (remix-run/react-router, 57k stars) and Spec Driven Develop (zhu1090093659/spec_driven_develop, 985 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cy Issue To Spec?

compozy (a GitHub organization) maintains it in compozy/compozy, which has 2,791 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on October 8, 2026.

Source: compozy/compozy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.