agentleFS
Sign inStart free
Atiqul-IslamAtiqul-Islam/graphcrew/.claude/skills/spec-compile/SKILL.md

spec-compile

Skill0 starsChanged 8 months agoMITView on GitHub

Compile a spec into pytest-bdd .feature file and step stubs

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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:

    Use Given/When/Then with concrete values

    line 19
  2. Very specific:

    Create step functions with raise NotImplementedError("Step not yet implemented")

    line 22
  3. Very specific:

    Import shared helpers from tests/steps/helpers.py

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

spec-compile

Compile a plain-English API spec into pytest-bdd feature files and step definition stubs.

Usage

/spec-compile <module-name>

Process

  1. Read the spec — tests/specs/<module-name>.md
  2. Generate feature file — tests/features/<module-name>.feature
    • Map each API contract section to a Feature
    • Map each behavior/constraint to a Scenario
    • Use Given/When/Then with concrete values
  3. Generate step stubs — tests/steps/test_<module-name>_steps.py
    • Import from pytest_bdd
    • Create step functions with raise NotImplementedError("Step not yet implemented")
    • Import shared helpers from tests/steps/helpers.py
  4. Report what was generated

Feature File Format

Feature: <Module> API Contract
  As a developer using graphcrew
  I want <module> to behave according to its spec
  So that I can build reliable multi-agent systems

  Scenario: <behavior description>
    Given <precondition>
    When <action>
    Then <expected outcome>

Rules

  • One .feature file per spec
  • One step file per spec
  • Step stubs raise NotImplementedError — implementation comes during the IMPLEMENT phase
  • Reuse common steps from tests/steps/common/ where applicable
  • Feature files go in tests/features/ (gitignored — generated artifacts)

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.

Check your setup, free