agentleFS
NoatToanNoatToan/claude-code-plugins/skills/spec-driven/SKILL.md

spec-driven

Skill1 starsChanged 24 days agoNo licenceView on GitHub

Run a feature spec-first using OpenSpec — agree on the spec before writing code. Bootstraps OpenSpec into the repo (npx openspec init --tools claude), then drives its propose → apply → archive loop, enriching each change's design.md to map onto this plugin's _modules/ architecture and unifying the change id with the ticket tracker. TRIGGER when the user says "spec-driven", "openspec", "propose a change", "write a spec first", "spec trước khi code", "làm theo spec", "opsx", pastes an /opsx:* command, or asks to set up OpenSpec in a project. When the SessionStart hook detects an openspec/ directory, offer OpenSpec per ticket/feature — apply it only if the user agrees, otherwise run the normal rules skills — and announce each CLI command it triggers so the user stays aware.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use implement.

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.
  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 5

    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 12 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.