To-Spec skill
Record agreed decisions as a project specification and publish it to the configured tracker.
Community · Matt Pocock| Author | Matt Pocock |
|---|---|
| Licence | MIT |
| Source | mattpocock/skills · SKILL.md on GitHub |
| Project website | www.aihero.dev/skills-to-spec |
| Works in | Claude Code · Codex, Gemini CLI, Cursor, Copilot |
| Read from the source on |
The to-spec skill synthesizes an already-decided conversation into a specification. It uses the codebase, project glossary and architectural decisions instead of starting another requirements interview.
It confirms testing seams, records user stories and scope, then publishes one spec through the configured tracker. Local Markdown is supported when the repository uses the local tracker configuration.
From the skill's SKILL.md: ## Out of Scope
What it does
- Read the existing conversation and relevant project decisions.
- Confirm testing seams and synthesize the specification.
- Publish the spec to the configured tracker with the configured triage label.
What you get
- One specification covering the problem, solution, stories, implementation decisions, testing and exclusions.
When to use it
- Preserve settled decisions for work spanning several agent sessions.
When not to use it
- Undecided requirements or a small change that fits one implementation session.
What it needs
- A coding agent with project context and the setup-matt-pocock-skills tracker configuration.
- Remote trackers need authenticated tools and permission to publish; local Markdown avoids a remote service.
Files in the skill
| File or folder | What it is for |
|---|---|
SKILL.md | Specification template, testing-seam confirmation and tracker publication. |
Licence as found in the repository on 2026-11-19: MIT.
Example prompts
Type one of these after installing; naming the skill makes sure it is used.
- /to-spec — synthesize our agreed account-export design without inventing new requirements.
- /to-spec — preserve our out-of-scope decisions and confirm the testing seams first.
- /to-spec #42 — turn this settled decision map into a buildable specification.
How to install to-spec
Installation and permissions
Install the skill and configure the repository’s tracker and triage labels with setup-matt-pocock-skills. Review any resulting project configuration before use.
This is a manually invoked skill: disable-model-invocation is true. Confirm the destination and publication permissions; this website does not create tracker issues.
A skill is a folder with a SKILL.md file. You install it once; the agent reads its short description at the start of each session and loads the full instructions only when a request matches. Pick the place you use:
Claude Code: copy the folder into your skills folder
Put the skill's folder in ~/.claude/skills/ to use it in every project on this computer, or in .claude/skills/ inside a repository to share it with everyone who works there (commit it).
git clone --depth 1 https://github.com/mattpocock/skills.git
mkdir -p ~/.claude/skills
cp -R skills/skills/engineering/to-spec ~/.claude/skills/Claude Code notices new or changed skills in these folders during the session. If the skills folder did not exist when the session started, run /reload-skills once. Then type /to-spec or just describe the task.
On Windows, run the commands in Git Bash or WSL, or copy the folder into the same place with File Explorer.
Codex, Gemini CLI, Cursor and GitHub Copilot
These agents read the same SKILL.md folders. The one folder all four accept inside a project is .agents/skills/, so this copies the skill there:
git clone --depth 1 https://github.com/mattpocock/skills.git
mkdir -p .agents/skills
cp -R skills/skills/engineering/to-spec .agents/skills/| Agent | Project folder | Your user folder | Notes |
|---|---|---|---|
| OpenAI Codex | .agents/skills/ | ~/.agents/skills/ | Type $ or run /skills to pick a skill; Codex also chooses one when your task matches. |
| Gemini CLI | .agents/skills/.gemini/skills/ | ~/.agents/skills/~/.gemini/skills/ | Or install from Git with gemini skills install <git URL> --path <folder> --consent. Google replaced Gemini CLI with Antigravity CLI for free-tier and Google One users on 18 June 2026; Antigravity uses .agents/skills/ in a project and ~/.gemini/config/skills/ for you. |
| Cursor | .agents/skills/.cursor/skills/ | ~/.agents/skills/~/.cursor/skills/ | Type / in Agent chat to pick a skill. Cursor also reads Claude Code's .claude/skills/ folders. |
| GitHub Copilot | .github/skills/.agents/skills/.claude/skills/ | ~/.copilot/skills/~/.agents/skills/ | Works in Copilot CLI, the cloud agent, and agent mode in VS Code, Visual Studio and JetBrains (IDE support depends on the version). Or run gh skill install OWNER/REPOSITORY SKILL (public preview, GitHub CLI 2.90.0 or later). |
Sources for these steps
Checked against each vendor's documentation on 2026-11-14:
A record of decisions already made
The spec should preserve the project’s vocabulary and real exclusions. It should not fill empty sections by inventing decisions.
For multi-session work, pass the spec to to-tickets. Keeping both steps in the same context avoids re-fetching a very large issue body.
Questions about to-spec
Does it interview me?
No new requirements interview is intended. It does check that the proposed testing seams match your expectations.
Is GitHub required?
No. It uses the configured tracker, which can be local Markdown or a supported remote issue tracker.
Is to-prd the same command?
The author renamed that workflow to to-spec. Use the current installed skill name.
Can ready-for-agent trigger unwanted work?
Yes, a polling agent may treat the parent spec as a work item. Explicitly exclude it from that agent’s ticket selection.
More AI skills
Related skills
To-Tickets skill
Community · Matt PocockSplit a specification into demonstrable vertical slices with explicit blocking dependencies.Writing Plans skill
Community · Jesse Vincent / Prime RadiantConvert an approved design into reviewable engineering tasks with interfaces and verification.Brainstorming skill
Community · Jesse Vincent / Prime RadiantTurn an undeveloped idea into an agreed design before writing implementation code.Subagent-Driven Development skill
Community · Jesse Vincent / Prime RadiantExecute an approved plan with fresh implementers, scoped reviews and a recorded task ledger.n8n Self Hosting skill
Community · Romuald CzłonkowskiDeploy and maintain Docker-based n8n with Caddy HTTPS, private services and verified backups.n8n Code JavaScript skill
Community · Romuald CzłonkowskiWrite or debug n8n JavaScript Code nodes with mode-aware data access and returns.