CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Synthesize an implementation-ready spec from the current conversation and relevant repository context.
Install To Spec
$ npx skills add stevesolun/ctx --skill to-spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install stevesolun/ctx to-spec --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/stevesolun/ctx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/to-spec .claude/skills/to-spec && rm -rf skills-srcUse ~/.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/
Install the "to-spec" agent skill from https://github.com/stevesolun/ctx/tree/main/.agents/skills/to-spec into .claude/skills/to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-spec", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/stevesolun/ctx/tree/main/.agents/skills/to-specType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add stevesolun/ctx --skill to-spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install stevesolun/ctx to-spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stevesolun/ctx.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/to-spec .agents/skills/to-spec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "to-spec" agent skill from https://github.com/stevesolun/ctx/tree/main/.agents/skills/to-spec into .agents/skills/to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-spec", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add stevesolun/ctx --skill to-spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install stevesolun/ctx to-spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stevesolun/ctx.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/to-spec .cursor/skills/to-spec && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "to-spec" agent skill from https://github.com/stevesolun/ctx/tree/main/.agents/skills/to-spec into .cursor/skills/to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-spec", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/stevesolun/ctx.git --path .agents/skills/to-spec--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add stevesolun/ctx --skill to-spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install stevesolun/ctx to-spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stevesolun/ctx.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/to-spec .gemini/skills/to-spec && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "to-spec" agent skill from https://github.com/stevesolun/ctx/tree/main/.agents/skills/to-spec into .gemini/skills/to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-spec", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install stevesolun/ctx to-specInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add stevesolun/ctx --skill to-spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/stevesolun/ctx.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/to-spec .github/skills/to-spec && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "to-spec" agent skill from https://github.com/stevesolun/ctx/tree/main/.agents/skills/to-spec into .github/skills/to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-spec", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add stevesolun/ctx --skill to-spec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install stevesolun/ctx to-spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stevesolun/ctx.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/to-spec .opencode/skills/to-spec && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "to-spec" agent skill from https://github.com/stevesolun/ctx/tree/main/.agents/skills/to-spec into .opencode/skills/to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-spec", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
to-spec- GitHub stars
- 588
- Token cost
- ~334 tokens
- SKILL.md length
- 155 words
- Files
- 3
- Skills in repo
- 26
- Repo updated
- First seen
- Licence
- MIT
At a glance
Synthesize an implementation-ready spec from the current conversation and relevant repository context.
- Wants agreed work captured as a spec
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Codebase knowledge for agents
- Tasks that involve PRD writing
What it does
To Spec is an agent skill from stevesolun/ctx. Synthesize an implementation-ready spec from the current conversation and relevant repository context. Use explicitly when the user wants agreed work captured as a spec or PRD.
Its SKILL.md is about 330 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `SPEC-FORMAT.md` and `agents/openai.yaml`).
It sits in Product & Project Management, covering Codebase knowledge for agents and PRD writing. The repository describes itself as: CTX Fit finds the cheapest AI coding setup that reliably works on your repository, then applies the winner as a reviewable change. The licence is MIT.
When your agent uses it
- Wants agreed work captured as a spec
- Tasks that involve Codebase knowledge for agents
- Tasks that involve PRD writing
Example prompts
- “/to-spec”
What it can do on your machine
Read from SKILL.md and the folder at commit 11b582a. 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
No scripts in the folder and no shell commands in SKILL.md.
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
To Spec loads about 334 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 155 words of instructions outside code blocks.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from stevesolun/ctx at commit 11b582a, republished under its MIT licence (© stevesolun). 155 words, ~334 tokens.
Download SKILL.mdSave it as
.claude/skills/to-spec/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- to-spec
- description
- Synthesize an implementation-ready spec from the current conversation and relevant repository context. Use explicitly when the user wants agreed work captured as a spec or PRD.
Create a spec
Capture the decisions already made. Resolve only gaps that would materially change the intended behavior, scope, or feasibility; do not reopen settled questions for the sake of completing a template.
Inspect the relevant implementation, tests, domain language, and architectural decisions when they improve fidelity. Keep facts observed in the repository distinct from decisions inferred from the conversation.
Describe:
- the user-visible problem and desired outcome;
- behavior, edge cases, and acceptance criteria;
- constraints and decisions that implementation must preserve;
- relevant interfaces or test seams when they are already known; and
- explicit exclusions and unresolved questions.
Prefer durable behavioral contracts over file paths and implementation recipes. Include code or a type shape only when it records a decision more precisely than prose.
Use the spec format when a structured document helps. Return, save, or publish the spec in the destination the user requested. Treat tracker publication and label changes as separate mutations requiring clear scope.
© stevesolun, 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 2 other files in .agents/skills/to-spec of stevesolun/ctx.
- SKILL.md
- SPEC-FORMAT.md
- agents/openai.yaml
Open the folder on GitHubat commit 11b582a
Compare with similar skills
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| To Spec this skillstevesolun/ctx | 588 | — | ~334 | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Trellis Brainstormanjiemo/SunnyBeach | 178 | 7 repos | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Ouroboros PM InterviewQ00/ouroboros | 6.2k | — | ~5.7k | Automated safety check: Pass | MIT | |
| Project Planneradrianpuiu/claude-skills-marketplace | 100 | 1 repos | ~6k | Automated safety check: Pass | None | |
| Reviewfossasia/eventyay-interpretation | 1.6k | 35 repos | ~996 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Trellis Brainstorm
anjiemo/SunnyBeach
Guides collaborative requirements discovery before implementation.
Ouroboros PM Interview
Q00/ouroboros
Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.
Project Planner
adrianpuiu/claude-skills-marketplace
Comprehensive project planning and documentation generator for software projects.
Review
fossasia/eventyay-interpretation
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match…
User Alignment and Agent-Ready PRDs
tryproduck/produck-skills
Turns a vague feature request into a written spec with scope, phases, acceptance criteria and do-not-do limits that a coding agent can follow without guessing.
More from stevesolun/ctx
All 26 skills in this repoDiagnosing Bugs
stevesolun/ctx
Diagnose hard bugs and performance regressions with reproducible evidence, focused hypotheses, and proportional instrumentation.
Repo Stats Autoupdate
stevesolun/ctx
Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory.
Code Review
stevesolun/ctx
Review a Git diff against repository standards and its originating requirements.
No Mistakes
stevesolun/ctx
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI.
Skill Router
stevesolun/ctx
Repo-aware recommendation manager for ctx. An agent skill from stevesolun/ctx.
Codebase Design
stevesolun/ctx
Design or improve module interfaces using deep-module heuristics.
Related
Questions about To Spec
What does To Spec do?
Synthesize an implementation-ready spec from the current conversation and relevant repository context. To Spec is an agent skill from stevesolun/ctx. Synthesize an implementation-ready spec from the current conversation and relevant repository context.
When should I use To Spec?
To Spec fits situations like: wants agreed work captured as a spec; tasks that involve Codebase knowledge for agents; tasks that involve PRD writing.
How do I install To Spec in Claude Code?
Run `npx skills add stevesolun/ctx --skill to-spec -a claude-code`. Or copy the skill folder (.agents/skills/to-spec in stevesolun/ctx) into .claude/skills/to-spec in your project. Claude Code loads it when a task matches its description.
How do I install To Spec in Codex?
Run `npx skills add stevesolun/ctx --skill to-spec -a codex`. Or copy the skill folder (.agents/skills/to-spec in stevesolun/ctx) into .agents/skills/to-spec in your project. Codex loads it when a task matches its description.
Can I use 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 stevesolun/ctx --skill 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/to-spec, .gemini/skills/to-spec, .github/skills/to-spec and .opencode/skills/to-spec in your project.
What does To Spec need to run?
SKILL.md names no scripts, command-line tools or credentials: To Spec is instructions for the agent only.
Does 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 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. Review the folder before installing.
What licence does To Spec use?
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 To Spec use?
About 334 tokens (SKILL.md is roughly 1.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to To Spec?
Skills that share tags, products or a category with To Spec: CCPM Project Management (automazeio/ccpm, 8.4k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars), Ouroboros PM Interview (Q00/ouroboros, 6.2k stars) and Project Planner (adrianpuiu/claude-skills-marketplace, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains To Spec?
stevesolun (a GitHub user) maintains it in stevesolun/ctx, which has 588 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 4, 2026.
Source: stevesolun/ctx on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.