agentleFS
salvo8519salvo8519/fairmark/.agents/skills/spec-new/SKILL.md

spec-new

Skill1 starsChanged 2 days agoApache-2.0View on GitHub

Start a new feature spec for Fairmark from the templates (spec-driven development). Use when the user asks for a new method, behaviour change or any feature that changes what Fairmark computes or exposes.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Create specs/NNNN-<kebab-name>/ and copy specs/_templates/spec.md into it.

    line 7
  2. Distinctive:

    Ask them to answer the open questions and to approve.

    line 11
  3. Very specific:

    Only when the user explicitly approves: set Status: Approved, then ask spec-writer to produce plan.md and tasks.md.

    line 12
  4. Very specific:

    Add or update the epic in roadmap/roadmap.yaml if the spec introduces new work.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 4 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
  1. Pick the next number: list specs/ and take the highest NNNN + 1.
  2. Create specs/NNNN-<kebab-name>/ and copy specs/_templates/spec.md into it.
  3. Delegate drafting to the spec-writer subagent with the user's request and any material they provided (models, examples, sources).
  4. Show the user: the requirements list, the conventions table and the open questions. Ask them to answer the open questions and to approve.
  5. Only when the user explicitly approves: set Status: Approved, then ask spec-writer to produce plan.md and tasks.md.
  6. Add or update the epic in roadmap/roadmap.yaml if the spec introduces new work.

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.