agentleFS
finolabsfinolabs/vibebiz/.claude/skills/speckit-converge/SKILL.md

speckit-converge

Skill1 starsChanged 4 days agoLicence not identifiedView on GitHub

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

85 other projects use a version of this, 69 of them edited; 53 of 70 edited versions we compared changed its rules; 7 new projects in the last 4 weeks, against 8 the 4 before.

How people change it

53 of 70 edited versions changed its rules, and some changes recur.

Of the 70 edited versions we compared: 17 keep every rule, 53 made changes of their own.

Rules people drop

  1. If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that .specify/extensions.yml could not be read (include the parser error) and that no hooks were checked, including any mandatory (optional: false) hooks registered there, …dropped by 52 of 53

Rules people add

  1. If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normallyadded by 52 of 53

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: 7 new projects took it in the last 4 weeks, 0.9× the 4 weeks before.

Week of Sep 20: 2 new projectsWeek of Sep 27: 2 new projectsWeek of Oct 4: 1 new projectWeek of Oct 11: 3 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 2 new projectsWeek of Nov 1: 2 new projectsWeek of Nov 8: 2 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

Used with

Projects with it also use speckit-agent-context-update, speckit-git-commit and 4 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.

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. 3 are common, 0 are distinctive, and 14 are very specific to this project.

  • 3

    Common

    Most of the 69 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 14

    Very specific

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

The licence could not be identified — 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 69 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.