agentleFS
TiagoJacintoTiagoJacinto/skills/atdd/SKILL.md

atdd

Skill2 starsChanged 37 days agoMITView on GitHub

ATDD: author or revise .feature scenarios, obtain approval, and hand off implementation to hvtdd. Use when acceptance behavior needs feature-file changes.

6 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

1 rule. 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read Feature authoring to decide scenario coverage and follow the project's feature-file conventions.

    line 8

“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

Acceptance-Test-Driven Development

  1. Read Feature authoring to decide scenario coverage and follow the project's feature-file conventions. If existing scenarios already specify the requested behavior accurately, continue to step 3 without changing them.
  2. For new or changed scenarios: Call the Skill tool with "behavior-specification". Propose the exact .feature changes and obtain approval as specified by Feature authoring. Write the approved feature files.
  3. Hand off bindings, implementation, and acceptance verification: Call the Skill tool with "hvtdd".

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.