agentleFS
Sign inStart free
sunnybharasunnybhara/claude-starter/skills/product-spec/SKILL.md

product-spec

Skill0 starsChanged 3 months agoMITView on GitHub

Use before building anything new of substance, a website, an app, a feature, a tool someone will actually use. Triggers on "build me", "make a website", "create an app", a new project kickoff, or any request where the shape of the thing is not yet pinned down. Turns the idea into a short checkable spec and gets a yes before code is written.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use code-review.

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

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 2

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

    WHEN asked to build something new of substance, spec before code.

    line 8
  2. Distinctive:

    Write the spec as checkable goals, one line each, each provable done or not done ("a visitor can book from a phone", not "great UX").

    line 14

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

product-spec

WHEN asked to build something new of substance, spec before code. The spec is short; the point is agreement, not paperwork:

  • Pin the shape with a few questions before assuming: who it is for, what it must do on day one, what is deliberately out. Stop asking when the answers would no longer change the build.
  • Write the spec as checkable goals, one line each, each provable done or not done ("a visitor can book from a phone", not "great UX"). A goal that cannot fail cannot pass either.
  • Name the smallest version that is genuinely useful and move everything else to a labelled later-list. If the spec could be half the size, halve it.
  • Surface the running costs up front: hosting, domain, paid APIs, anything with a monthly bill. No surprise invoices after launch.
  • Show the spec and get an explicit yes before writing code. A changed mind costs a paragraph at spec stage and the whole build after it.

Skill updated: 2026-08-15

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