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

To Spec

by bestofjs in bestofjs/bestofjs

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.

MITAuto-check passedProduct & Project Management

Install To Spec

skills CLI
$ npx skills add bestofjs/bestofjs --skill to-spec -a claude-code

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

GitHub CLI
$ gh skill install bestofjs/bestofjs 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/bestofjs/bestofjs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/to-spec .claude/skills/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
to-spec
GitHub stars
3.1k
Used in
21 other repos
Token cost
~757 tokens
SKILL.md length
438 words
Files
2
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 2 steps: Explore the repo to understand the… → Sketch out the seams at which you're…
  • Tasks that involve Issue triage
  • SKILL.md covers Process, Problem Statement, Solution and User Stories, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

To Spec is an agent skill from bestofjs/bestofjs. 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.

Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Product & Project Management, covering Issue triage and User stories. The repository describes itself as: :star: A place to find the best components to build amazing web applications. The best of JavaScript! The licence is MIT.

When your agent uses it

  • Tasks that involve Issue triage
  • Tasks that involve User stories

Example prompts

  • “/to-spec”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary…
  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…

What it can do on your machine

Read from SKILL.md and the folder at commit 5d82633. 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 757 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 438 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~757

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 bestofjs/bestofjs at commit 5d82633, republished under its MIT licence (© bestofjs). 438 words, ~757 tokens.

Download SKILL.mdSave it as .claude/skills/to-spec/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
to-spec
description
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.
disable-model-invocation
true

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 — run /setup-matt-pocock-skills if not.

Process

  1. 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.

  1. 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 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:

  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.

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

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.

</spec-template>

© bestofjs, 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 1 other file in .agents/skills/to-spec of bestofjs/bestofjs.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 5d82633

Used in 21 other repositories

We found 25 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 21 other GitHub owners. This page covers the copy in bestofjs/bestofjs, which our catalogue first saw on October 7, 2026.

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.

To Spec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
To Spec this skillbestofjs/bestofjs3.1k21 repos~757Automated safety check: PassMIT
To Specvinvcn/mattpocock-skills-zh-CN4.7k—~441Automated safety check: PassMIT
GitHub Issue TriageOpenHands/extensions163—~437Automated safety check: PassMIT
To Prdywwynm/EverythingDone14411 repos~777Automated safety check: PassGPL-3.0
To Prdfossasia/eventyay-interpretation1.6k4 repos~755Automated safety check: PassApache-2.0
Goosetown Researcher Beadsaaif-goose/goosetown155—~4.2kAutomated safety check: PassApache-2.0

Similar skills

  • To Spec

    vinvcn/mattpocock-skills-zh-CN

    把当前对话转成 spec 并发布到项目 issue tracker：不做访谈，只综合已经讨论的内容. An agent skill from vinvcn/mattpocock-skills-zh-CN.

    4.7k GitHub stars~441 tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

  • GitHub Issue Triage

    OpenHands/extensions

    Prioritize open issues and establish acceptance criteria before marking them ready for development.

    163 GitHub stars~437 tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • To Prd

    ywwynm/EverythingDone

    Turn the current conversation context into a PRD and publish it to the project issue tracker.

    144 GitHub starsUsed in 11 repos~777 tokens
    Product & Project ManagementAuto-check passed

  • To Prd

    fossasia/eventyay-interpretation

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

    1.6k GitHub starsUsed in 4 repos~755 tokens
    Product & Project ManagementAuto-check passed

  • Goosetown Researcher Beads

    aaif-goose/goosetown

    Search the local beads (bd) issue tracker for issues, dependencies, epics, blockers, and project status.

    155 GitHub stars~4.2k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed

More from bestofjs/bestofjs

All 13 skills in this repo

  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 26 repos~2.6k tokens
    Auto-check passed

  • Wayfinder

    bestofjs/bestofjs

    Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

    3.1k GitHub starsUsed in 21 repos~2.9k tokens
    Auto-check passed

  • Setup Matt Pocock Skills

    bestofjs/bestofjs

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.

    3.1k GitHub starsUsed in 20 repos~1.7k tokens
    Auto-check passed

  • Writing For Agents

    bestofjs/bestofjs

    Writing documents for agents. An agent skill from bestofjs/bestofjs.

    3.1k GitHub starsUsed in 18 repos~2.7k tokens
    Auto-check passed

  • Wizard

    bestofjs/bestofjs

    Generate an interactive bash wizard that walks a human through steps only they can perform.

    3.1k GitHub starsUsed in 12 repos~1k tokens
    Auto-check: notes

  • To Tickets

    bestofjs/bestofjs

    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket…

    3.1k GitHub starsUsed in 20 repos~1.4k tokens
    Auto-check passed

Categories

Questions about To Spec

What does To Spec do?

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. To Spec is an agent skill from bestofjs/bestofjs. 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.

When should I use To Spec?

To Spec fits situations like: tasks that involve Issue triage; tasks that involve User stories.

How do I install To Spec in Claude Code?

Run `npx skills add bestofjs/bestofjs --skill to-spec -a claude-code`. Or copy the skill folder (.agents/skills/to-spec in bestofjs/bestofjs) 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 bestofjs/bestofjs --skill to-spec -a codex`. Or copy the skill folder (.agents/skills/to-spec in bestofjs/bestofjs) 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 bestofjs/bestofjs --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 757 tokens (SKILL.md is roughly 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: To Spec (vinvcn/mattpocock-skills-zh-CN, 4.7k stars), GitHub Issue Triage (OpenHands/extensions, 163 stars), To Prd (ywwynm/EverythingDone, 144 stars) and To Prd (fossasia/eventyay-interpretation, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains To Spec?

bestofjs (a GitHub organization) maintains it in bestofjs/bestofjs, which has 3,136 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 4, 2026.

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