A skill that turns the current conversation and understanding of the codebase into a written software specification, also called a product requirements document.

Use it to explore the repository, identify where behavior can be tested, and save a specification under .plan/.

It captures decisions and testable behavior in one document without starting a new interview.

to-spec — Skill for Claude Code by rengwu

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add rengwu/wayfinder-maps --skill to-spec

Clone the repo

git clone --depth 1 https://github.com/rengwu/wayfinder-maps

Made for: Claude Code.

Or install wayfinder-maps, the plugin that ships this one along with the rest of its 14 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/rengwu/wayfinder-maps/to-spec/github.svg)](https://agentmods.dev/skills/rengwu/wayfinder-maps/to-spec)

Your own site

<a href="https://agentmods.dev/skills/rengwu/wayfinder-maps/to-spec"><img src="https://agentmods.dev/badge/skills/rengwu/wayfinder-maps/to-spec/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/rengwu/wayfinder-maps/to-spec"><img src="https://agentmods.dev/badge/skills/rengwu/wayfinder-maps/to-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 684 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00029	$0.00684
Opus 5	$0.00015	$0.00342
Sonnet 5	$0.00006	$0.00137
Haiku 4.5	$0.00003	$0.00068

Measured 12d ago against content hash d854c81cc8a7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

to-spec scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/.optional/to-spec/SKILL.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

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

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.

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

Read the full file on GitHub · 74 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 74 lines · 29 tokens per session scan A d854c81cc8a7

Subscribe to this mod's changes

to-spec is a skill published in the GitHub repository rengwu/wayfinder-maps (123 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 684 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning agent-skills go

dd-code-generation

Use pup CLI for immediate Datadog operations or generate code for integration into applications.

DataDog/pup · 16 tokens

redux-to-swr

Migrate React components from Redux + Saga to SWR hooks. Use when converting data fetching from Redux store (reducers, sagas, selectors, connect HOC) to SWR-based hooks in CockroachDB DB Console or cluster-ui.

cockroachdb/cockroach · 53 tokens

mma-investigator

Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.

cockroachdb/cockroach · 47 tokens

migrate-state-management

Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use when refactoring away from Redux/Context, moving state to the right store, or when the user asks to migrate state management.

SigNoz/signoz · 64 tokens

ast-introspection

Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).

pilinux/gorest · 28 tokens

build-run

Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.

pilinux/gorest · 22 tokens