How do I install the To Spec skill?

Run npx skillmds@latest add gr8monk3ys/to-spec in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is To Spec safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with To Spec?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is To Spec free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published To Spec?

gr8monk3ys (@gr8monk3ys) published this skill. Their other Agent Skills are listed on their SkillMD profile.

To Spec by gr8monk3ys — Agent Skill

Name: To Spec
Author: gr8monk3ys

File contents

Not shipped in the plugin. Overlaps a superpowers skill (see table in .claude/skills/misc/README.md). To ship it, move it to a promoted bucket and run npm run sync.

This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user — just synthesize what you already know.

The issue tracker and triage label vocabulary should have been provided to you. If not, ask the user whether to use GitHub Issues (via gh) or a local docs/issues/ folder, and which labels they triage with.

Process

Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.
Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.

Check with the user that these seams match their expectations.

Write the spec using the template below, then publish it to the project issue tracker. Apply the ready-for-agent triage label - no need for additional triage.

Problem Statement

The problem that the user is facing, from the user's perspective.

Solution

The solution to the problem, from the user's perspective.

User Stories

A LONG, numbered list of user stories. Each user story should be in the format of:

As an , I want a , so that

This list of user stories should be extremely extensive and cover all aspects of the feature.

Implementation Decisions

A list of implementation decisions that were made. This can include:

The modules that will be built/modified
The interfaces of those modules that will be modified
Technical clarifications from the developer
Architectural decisions
Schema changes
API contracts
Specific interactions

Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.

Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.

Testing Decisions

A list of testing decisions that were made. Include:

A description of what makes a good test (only test external behavior, not implementation details)
Which modules will be tested
Prior art for the tests (i.e. similar types of tests in the codebase)

Out of Scope

A description of the things that are out of scope for this spec.

Further Notes

Any further notes about the feature.

---name: to-specdescription: 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.---> **Not shipped in the plugin.** Overlaps a superpowers skill (see table in `.claude/skills/misc/README.md`). To ship it, move it to a promoted bucket and run `npm run sync`.This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user — just synthesize what you already know.The issue tracker and triage label vocabulary should have been provided to you. If not, ask the user whether to use GitHub Issues (via `gh`) or a local `docs/issues/` folder, and which labels they triage with.## Process1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.Check with the user that these seams match their expectations.3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.<spec-template>## Problem StatementThe problem that the user is facing, from the user's perspective.## SolutionThe solution to the problem, from the user's perspective.## User StoriesA LONG, numbered list of user stories. Each user story should be in the format of:1. As an <actor>, I want a <feature>, so that <benefit><user-story-example>1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending</user-story-example>This list of user stories should be extremely extensive and cover all aspects of the feature.## Implementation DecisionsA list of implementation decisions that were made. This can include:- The modules that will be built/modified- The interfaces of those modules that will be modified- Technical clarifications from the developer- Architectural decisions- Schema changes- API contracts- Specific interactionsDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.## Testing DecisionsA list of testing decisions that were made. Include:- A description of what makes a good test (only test external behavior, not implementation details)- Which modules will be tested- Prior art for the tests (i.e. similar types of tests in the codebase)## Out of ScopeA description of the things that are out of scope for this spec.## Further NotesAny further notes about the feature.</spec-template>

Frequently asked questions

To Spec