To spec

Skill rengwu/wayfinder-maps/skills/.optional/to-spec

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

Install

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

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

3.2 KB, 652 tokens by cl100k_base, as published. Nobody here has run it

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.

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

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 1 of the 12 instructions most plan spec skills give in 652 tokens

Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06

Ask one question at a timein 73 of 1360
Write the spec using the templatehere, and in 22 of 1360
Ask clarifying questions if neededin 19 of 1360, across 18 files
Wait for user confirmation before proceedingin 19 of 1360
Save plans to the plans directoryin 17 of 1360, across 13 files
Check for product marketing context firstin 16 of 1360, across 5 files
Read the plan file completelyin 16 of 1360
Order tasks by dependencyin 16 of 1360
Gather context from the conversationin 15 of 1360, across 9 files
Explore the codebase instead of askingin 15 of 1360, across 13 files
Wait for explicit user approvalin 14 of 1360, across 13 files
Quiz the user on the breakdownin 13 of 1360, across 7 files

Said here and by no other author read

Use vocabulary from CONTEXT.md if it exists
Respect ADRs in docs/adr/ if they exist
Sketch out test seams at the highest level

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.