agentleFS
Sign inStart free
kyoo-147kyoo-147/MinimalShip/skills/engineering/to-spec/SKILL.md

to-spec

Skill0 starsChanged 24 days agoMITView on GitHub

Turn an already-discussed product request into a compact, testable specification without restarting discovery.

195 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-ts-deep-modules, loop-me and 6 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 43 projects that use this

  • RoentekSkill

    loop-me

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

    Also in 49 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 39 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 51 projects that use this

  • LesaniSkill

    writing-shape

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

    Also in 49 projects that use this

  • simo97Skill

    migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    Also in 46 projects that use this

  • +1 more from Lesani

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the current conversation, repository rules, existing work records, and relevant code.

    line 9
  2. Distinctive:

    Write one primary outcome and a short MUST / NOT NOW boundary.

    line 11
  3. Distinctive:

    Add three to seven acceptance cases in input -> action -> expected result form.

    line 12
  4. Distinctive:

    Add failure behavior, permissions, and a real demo or smoke command.

    line 13
  5. Very specific:

    Update FEATURES.md for the requested feature or the existing verified capability it changes, keeping origin and status distinct.

    line 14
  6. Very specific:

    Update RUN.md with the current objective, scope, acceptance evidence and open decisions.

    line 15
  7. Distinctive:

    Write the result to the repository's chosen work record or configured tracker.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 183 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

To Spec

  1. Read the current conversation, repository rules, existing work records, and relevant code.
  2. Extract the user, problem, desired outcome, constraints, and evidence already agreed.
  3. Write one primary outcome and a short MUST / NOT NOW boundary.
  4. Add three to seven acceptance cases in input -> action -> expected result form.
  5. Add failure behavior, permissions, and a real demo or smoke command.
  6. Update FEATURES.md for the requested feature or the existing verified capability it changes, keeping origin and status distinct.
  7. Update RUN.md with the current objective, scope, acceptance evidence and open decisions.
  8. List assumptions explicitly. If one changes the design materially, stop and ask rather than guessing.

Write the result to the repository's chosen work record or configured tracker. Keep the spec implementation-neutral but executable.

Download now (ZIP)

Does it work?

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

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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