PlugWiki

to-spec Skill for Claude Code: Turn a Conversation Into a Spec

Turns the conversation you already had into a spec and publishes it to your issue tracker, without asking you more questions.

Installs
753.4K
on skills.sh
Stars
309.2K
on GitHub
Files
1
besides SKILL.md
Updated
Nov 2026
last repo commit

to-spec synthesises. It does not interview you. It explores the repo, proposes the test points (it prefers one, at the highest level), checks them with you, then writes the spec and posts it to the tracker with the ready-for-agent label.

The spec follows a fixed template: Problem Statement, Solution, User Stories (a long numbered list), Implementation Decisions, Testing Decisions, Out of Scope and Further Notes. It tells the agent to leave out file paths and code snippets, which go stale. Run /setup-matt-pocock-skills first so it knows your tracker.

Good for

  • Developers who just finished a long design chat and want it written down
  • Teams that hand specs to agents through an issue tracker
  • Anyone who wants a spec without answering another round of questions

Install to-spec

Claude Code

  1. 1

    Copy this prompt.

    Install the to-spec skill in Claude Code. Run this command:

claude plugin install mattpocock-skills@claude-plugins-official

Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Install the whole set with the plugin route. to-spec tells you to run /setup-matt-pocock-skills, a skill in the same repo, so it knows your issue tracker. The README asks you to run it once per repo. Pick one route per agent, or you get every skill twice. Claude Code names plugin skills /plugin-name:skill-name, so the full name is /mattpocock-skills:to-spec if /to-spec is not found.

From the project README. Source.

What's in the skill

When it loads

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

Sections in SKILL.md

  1. Process
  2. Problem Statement
  3. Solution
  4. User Stories
  5. Implementation Decisions
  6. Testing Decisions
  7. Out of Scope
  8. Further Notes

Key facts

Author
Matt Pocock
Repo
mattpocock/skills
Installs on skills.sh
753,358 (Nov 2, 2026)
GitHub stars
309,237 (Nov 2, 2026)
License
MIT
Last repo commit
Nov 1, 2026
Files next to SKILL.md
1 files
skills.sh audits
Gen Agent Trust Hub pass, Socket pass, Snyk pass
Needs
An issue tracker configured by the setup-matt-pocock-skills skill

What it includes

  • Reads the codebase, glossary and ADRs so the spec uses your vocabulary

    Read · Explore the repo

  • Proposes where the feature will be tested and checks with you first

    Sketch test seams

  • Fills the template: problem, solution, user stories, decisions, testing, scope

    Write · Write the spec

  • Posts the spec to your issue tracker with the ready-for-agent label

    Write · Publish

From the official docs

Permissions

Low risk

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It posts an issue to your tracker

    Confirm which repo or project the setup skill points at, then review the spec it publishes. github.com

Technical details
Talks toYour issue tracker
Scopes

  • Your repo and conversation

  • Your issue tracker

Questions

What does to-spec do?

It writes a spec from your current conversation and posts it to your issue tracker. It asks you only to confirm the test points.

How do I install to-spec?

Use the install box at the top and install the whole set. to-spec relies on the tracker settings from the setup skill.

Will it interview me first?

No. The SKILL.md says not to interview you and to use what it already knows. If you want questions first, run a grilling skill before to-spec.

Where does the spec go?

To your project's issue tracker with the ready-for-agent triage label. The setup skill decides which tracker that is.

What comes after to-spec?

The ask-matt router sends a multi-session build to to-tickets, which splits the spec into tickets.

Is it safe?

It reads your repo and posts one issue under your account. Check the tracker target before you run it, and read the spec before others rely on it.

Information

updated Nov 2, 2026

Repository
mattpocock/skills
Folder
skills/engineering/to-spec

mattpocock/skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 4
  1. mattpocock/skills README · github.com
  2. to-spec SKILL.md · github.com
  3. to-spec on skills.sh · skills.sh
  4. ask-matt SKILL.md · github.com

Updated Nov 2, 2026.