agentleFS
Sign inStart free
dabodamjandabodamjan/app-idea-to-spec/skills/refine-spec/SKILL.md

refine-spec

Skill0 starsChanged 5 months agoMITView on GitHub

Iterate on an existing app spec. Challenges scope, fills gaps, and tightens weak sections. Use when the user already has an app-spec.md from app-idea-to-spec and wants to improve it.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. tomharris/engineer-agent★ 0same name

    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.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the spec: Default to app-spec.md in the current project unless the user points you elsewhere.

    line 14
  2. Distinctive:

    Ask only the questions that matter: Do not re-interview them on what is already decided.

    line 22
  3. Distinctive:

    Rewrite the spec in place: Update the file, preserving the structure.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

app-idea-to-spec: refine-spec

You are refining an existing app-idea-to-spec spec. The goal is a tighter, more buildable spec, not a longer one.

How to run this

  1. Read the spec. Default to app-spec.md in the current project unless the user points you elsewhere. If there is no spec yet, tell them to run /app-idea-to-spec:new-spec first.
  2. Audit it against the template at ${CLAUDE_PLUGIN_ROOT}/templates/spec-template.md. For each section, decide: is it concrete and decided, or vague and hand-wavy? Flag the vague ones. A spec that says "some kind of sync" or "freemium probably" is not buildable yet.
  3. Hunt for the two failure modes, in this order:
    • Over-scope. This is the common one. Re-sort MVP features against the core loop. Anything that does not serve the loop moves to "Explicitly cut for later." Be willing to argue for cutting. Read ${CLAUDE_PLUGIN_ROOT}/knowledge/mvp-scope.md.
    • Under-specified. Missing data model, no screen list, no decision on platform or storage, monetization left as a shrug. These block code generation. Read the matching knowledge doc before you ask: platform ${CLAUDE_PLUGIN_ROOT}/knowledge/platform-choice.md, data ${CLAUDE_PLUGIN_ROOT}/knowledge/data-and-sync.md, money ${CLAUDE_PLUGIN_ROOT}/knowledge/monetization.md.
  4. Ask only the questions that matter. Do not re-interview them on what is already decided. Surface the specific gaps and weak spots, one at a time, and propose a concrete default for each so they can accept or adjust rather than start from blank.
  5. Rewrite the spec in place. Update the file, preserving the structure. Keep a short note at the bottom of any section you changed substantially so the user can see what moved.
  6. Close by pointing at /app-idea-to-spec:reality-check (if they have not run it) and /app-idea-to-spec:build-plan (when the spec is solid).

Tone

Constructive and direct. Your job is to make the spec sharper and smaller, not to validate it. If a section is weak, say so plainly and offer the fix.

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