Agent skill

To Spec

by rengwu in rengwu/wayfinder-maps

Turn the current conversation into a spec, saved to .plan/ — no interview, just synthesis of what you've already discussed.

MITAuto-check passedProduct & Project Management

Install To Spec

skills CLI
$ npx skills add rengwu/wayfinder-maps --skill to-spec -a claude-code

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

GitHub CLI
$ gh skill install rengwu/wayfinder-maps 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/rengwu/wayfinder-maps.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.optional/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
137
Token cost
~813 tokens
SKILL.md length
482 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Turn the current conversation into a spec, saved to .plan/ — 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 User stories
  • 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 rengwu/wayfinder-maps. Turn the current conversation into a spec, saved to .plan/ — no interview, just synthesis of what you've already discussed.

Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering User stories. The repository describes itself as: Planetary visualization tool for /wayfinder maps. The licence is MIT.

When your agent uses it

  • 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. If a CONTEXT.md glossary exists at the repo…
  2. Sketch out the seams at which you're going to test the feature — the public interfaces where behaviour can be observed without reaching…

What it can do on your machine

Read from SKILL.md and the folder at commit c252110. 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 813 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 482 words of instructions outside code blocks.

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

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 rengwu/wayfinder-maps at commit c252110, republished under its MIT licence (© rengwu). 482 words, ~813 tokens.

Download SKILL.mdSave it as .claude/skills/to-spec/SKILL.md (or your agent's skills folder).
name
to-spec
description
Turn the current conversation into a spec, saved to `.plan/` — 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 (you may know this document as a PRD). Do NOT interview the user — just synthesize what you already know.

Process

  1. Explore the repo to understand the current state of the codebase, if you haven't already. If a CONTEXT.md glossary exists at the repo root, use its vocabulary throughout the spec; respect any ADRs in docs/adr/ in the area you're touching. If neither exists, proceed silently.

  2. Sketch out the seams at which you're going to test the feature — the public interfaces where behaviour can be observed without reaching inside. 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 save it to .plan/<slug>/spec.md, where <slug> is a short kebab-case name for the work (reuse the directory if one already exists for this effort). Create the directory if needed — .plan/ is committed to version control; it is the project's shared planning memory. Tell the user the path.
<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>

© rengwu, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/.optional/to-spec of rengwu/wayfinder-maps.

Open the folder on GitHubat commit c252110

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 skillrengwu/wayfinder-maps137—~813Automated safety check: PassMIT
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
Ralph Tui Create Beadssubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT
Agile Product Owneralirezarezvani/claude-skills28k3 repos~3.2kAutomated safety check: PassMIT
Ralph Tui Create Beads Rustsubsy/ralph-tui2.5k1 repos~2.8kAutomated safety check: PassMIT
To Specbestofjs/bestofjs3.1k21 repos~757Automated safety check: PassMIT

Similar skills

  • 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
  • Ralph Tui Create Beads

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed
  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Product & Project ManagementAuto-check passed
  • Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).

    2.5k GitHub starsUsed in 1 repo~2.8k tokens
    Product & Project ManagementAuto-check passed
  • To Spec

    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.

    3.1k GitHub starsUsed in 21 repos~757 tokens
    Product & Project ManagementAuto-check passed
  • Ralph Tui Create JSON

    subsy/ralph-tui

    Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed

More from rengwu/wayfinder-maps

All 9 skills in this repo
  • Two-Axis Code Review

    rengwu/wayfinder-maps

    Reviews the changes since a commit, branch or tag along two separate axes: the repo's documented coding standards and fidelity to the originating spec or PRD.

    137 GitHub stars~1.8k tokensUpdated 4 days ago
    Auto-check passed
  • Verify

    rengwu/wayfinder-maps

    Build, launch and drive wayfinder-maps to verify a change end-to-end (server + headless browser).

    137 GitHub stars~738 tokensUpdated 4 days ago
    Auto-check passed
  • Wayfinder Planning Maps

    rengwu/wayfinder-maps

    Plans work too big for one agent session as a shared map of investigation tickets, resolved one at a time until the route to the destination is clear.

    137 GitHub stars~3.5k tokensUpdated 4 days ago
    Auto-check passed
  • To Tickets

    rengwu/wayfinder-maps

    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, saved to .plan/.

    137 GitHub stars~1.3k tokensUpdated 4 days ago
    Auto-check passed
  • Research

    rengwu/wayfinder-maps

    Investigate a question against high-trust primary sources and capture the findings as a cited Markdown file.

    137 GitHub stars~217 tokensUpdated 4 days ago
    Auto-check passed
  • Grill Me

    rengwu/wayfinder-maps

    A relentless interview to sharpen a plan or design — one question at a time until every branch of the decision tree is resolved.

    137 GitHub stars~211 tokensUpdated 4 days ago
    Auto-check passed

Questions about To Spec

What does To Spec do?

Turn the current conversation into a spec, saved to .plan/ — no interview, just synthesis of what you've already discussed. To Spec is an agent skill from rengwu/wayfinder-maps.plan/ — no interview, just synthesis of what you've already discussed.

When should I use To Spec?

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

How do I install To Spec in Claude Code?

Run `npx skills add rengwu/wayfinder-maps --skill to-spec -a claude-code`. Or copy the skill folder (skills/.optional/to-spec in rengwu/wayfinder-maps) 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 rengwu/wayfinder-maps --skill to-spec -a codex`. Or copy the skill folder (skills/.optional/to-spec in rengwu/wayfinder-maps) 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 rengwu/wayfinder-maps --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 813 tokens (SKILL.md is roughly 3.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: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Agile Product Owner (alirezarezvani/claude-skills, 28k stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains To Spec?

rengwu (a GitHub user) maintains it in rengwu/wayfinder-maps, which has 137 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 6, 2026.

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