agentleFS
Sign inStart free
rengwurengwu/wayfinder-maps/skills/.optional/to-spec/SKILL.md

to-spec

Skill137 starsChanged 4 months agoMITView on GitHub

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

We split this skill into the rules it gives an agent

2 rules. 2 are common, 0 are distinctive, and 0 are very specific to this project.

  • 2

    Common

    Most of the 180 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Check with the user that these seams match their expectations.

    line 15
  2. Common:

    Do NOT include specific file paths or code snippets.

    line 53

“Common” is measured: kept by at least 6 in 10 of the 180 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

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>

Download now (ZIP)

  • Other versions194 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 152

    1. mattpocock/skills★ 309k82% same
    2. QuivrHQ/quivr★ 40k82% same
    3. formbricks/formbricks★ 13k82% same
    4. ArcReel/ArcReel★ 6k82% same
    5. vinvcn/mattpocock-skills-zh-CN★ 5.5k18% same
    6. withcoral/coral★ 4.9k82% same
    7. bestofjs/bestofjs★ 3.1k82% same
    8. moeru-ai/xsai★ 66482% same
    9. nodetool-ai/nodetool★ 60344% same
    10. aws/graph-explorer★ 48982% same

    142 more not listed

    Wrote their own version · 42

    1. DanMcInerney/architect-loop★ 626same name
    2. stevesolun/ctx★ 583same name
    3. devcxl/mattpocock-skills-zh★ 522same name
    4. blockscout/frontend★ 309same name
    5. Integralist/agent-skills★ 20same name
    6. helderberto/agent-skills★ 19same name
    7. assisjp/specflow★ 17same name
    8. GulajavaMinistudio/polya-sdlc-coder★ 11same name
    9. mhmzdev/hisab-whatsapp★ 9same name
    10. adeonir/agent-skills★ 8same name

    32 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use setup-ts-deep-modules, to-questionnaire and 9 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • liufeng1976Skill

      setup-ts-deep-modules

      Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

      Also in 33 projects that use this

    • AWSSkill

      to-questionnaire

      Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

      Also in 77 projects that use this

    • RoentekSkill

      loop-me

      Grill me about specs for the workflows I want to build, within this workspace.

      Also in 40 projects that use this

    • AWSSkill

      wizard

      Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

      Also in 97 projects that use this

    • ryotaroh180105Skill

      claude-handoff

      Hand the current conversation off to a fresh background agent that picks up the work immediately.

      Also in 31 projects that use this

    • LesaniSkill

      writing-beats

      Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

      Also in 42 projects that use this

    • +2 more from aws
  • In this repository13 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free