agentleFS
caterpi11arcaterpi11ar/giclaw/.agents/skills/to-spec/SKILL.md

to-spec

Skill9 starsChanged 29 days agoNo licenceView on GitHub

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

223 other projects use a version of this, 102 of them edited; 46 of 99 edited versions we compared changed its rules; 10 new projects in the last 4 weeks, against 9 the 4 before.

How people change it

46 of 99 edited versions changed its rules, and some changes recur.

Of the 99 edited versions we compared: 52 keep every rule, 1 is an older text, 46 made changes of their own.

Not in older versions

  1. Write the spec using the template below, then publish it to the project issue tracker. Apply the ready-for-agent triage label - no need for additional triage.missing from 1 of 1

Rules people drop

  1. Write the spec using the template below, then publish it to the project issue tracker. Apply the ready-for-agent triage label - no need for additional triage.dropped by 36 of 46
  2. Check with the user that these seams match their expectations.dropped by 18 of 46
  3. Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.dropped by 9 of 46

Rules people add

  1. A rule we can't quote: its licence doesn't allow itadded by 4 of 46
  2. A rule we can't quote: its licence doesn't allow itadded by 2 of 46
  3. A rule we can't quote: its licence doesn't allow itadded by 2 of 46
  4. Write the spec using the template below, then publish it to the project issue tracker.added by 2 of 46
  5. A rule we can't quote: its licence doesn't allow itadded by 2 of 46
  6. No tracker configured (no MCP server, or the IDs are blank): write the spec to docs/plans/<feature-slug>/spec.md instead, creating the directory if needed. docs/plans/ is local-only; scripts/pre-commit refuses to commit it.added by 2 of 46
  7. Write the spec using the template below, then publish it: on a tracker, mcp__linear-server__save_issue with the spec as the markdown body and the spec label applied; otherwise the local file above.added by 2 of 46
  8. A rule we can't quote: its licence doesn't allow itadded by 2 of 46

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Steady: 10 new projects took it in the last 4 weeks, 1.1× the 4 weeks before.

Week of Sep 20: 1 new projectWeek of Sep 27: 2 new projectsWeek of Oct 4: 1 new projectWeek of Oct 11: 5 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 1 new projectWeek of Nov 1: 2 new projectsWeek of Nov 8: 6 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 2

    Common

    Most of the 127 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.