agentleFS
intent-driven-devintent-driven-dev/intent-driven-template/.agents/skills/spec-as-source/SKILL.md

spec-as-source

Skill185 starsChanged 32 days agoMITView on GitHub

Use when a user or project explicitly adopts OpenSpec spec-as-source, fenced Gherkin specifications as executable acceptance tests, or acceptance-test-first OpenSpec tasks.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 8 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use OpenSpec spec.md files as the executable source of truth.

    line 10
  2. Very specific:

    REQUIRED SUB-SKILL: Use gherkin-authoring when drafting or modifying fenced Gherkin.

    line 12
  3. Very specific:

    REQUIRED SUB-SKILL: Use acceptance-test-authoring when configuring or modifying the acceptance runner, extractor, linting, step …

    line 14
  4. Distinctive:

    When this skill is active, its artifact references override the corresponding templates from the configured OpenSpec schema.

    line 24
  5. Distinctive:

    Before crossing zones, finish and commit or stash the current zone.

    line 35
  6. Distinctive:

    Never commit specs-zone files and code-zone files together.

    line 36
  7. Distinctive:

    Never revert or discard user-owned changes without explicit permission.

    line 38
  8. Very specific:

    Use git status --porcelain before editing.

    line 40
  9. Distinctive:

    Commit or stash specs-zone work before touching code.

    line 45
  10. Distinctive:

    Keep the effective acceptance suite green with no pending or undefined steps.

    line 48
  11. Distinctive:

    Commit or stash code-zone work before returning to specifications for sync or archive.

    line 49
  12. Distinctive:

    Stop and restore the workflow boundary when any red flag occurs.

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 As Source

Overview

Use OpenSpec spec.md files as the executable source of truth. When this skill is active, fenced-Gherkin authoring, acceptance-first task ordering, spec-first implementation, and BDD zone isolation are one workflow.

REQUIRED SUB-SKILL: Use gherkin-authoring when drafting or modifying fenced Gherkin.

REQUIRED SUB-SKILL: Use acceptance-test-authoring when configuring or modifying the acceptance runner, extractor, linting, step definitions, or page objects.

Activation

This workflow is opt-in. Apply it only when the user or project instructions explicitly require spec-as-source.

Once active, the BDD zone rules below are mandatory. Do not activate or disable zone isolation separately.

Artifact References

  • When this skill is active, its artifact references override the corresponding templates from the configured OpenSpec schema.
  • Draft each spec.md from references/spec.md, not from openspec/schemas/intent-driven/templates/spec.md.
  • Draft tasks.md from references/tasks.md, not from the schema task template, preserving acceptance-test-first ordering.

BDD Zone Rules

  1. Code is written only for an active change under openspec/changes/ whose scenarios describe the behavior.
  2. A unit of work edits either the specs zone (non-tasks.md files under openspec/) or the code zone (non-tasks.md files outside openspec/), never both while changes are uncommitted.
  3. Before crossing zones, finish and commit or stash the current zone.
  4. Never commit specs-zone files and code-zone files together.
  5. Any file named tasks.md is zone-neutral: it may be edited alongside and committed with either zone. Task updates do not select or cross a zone and do not require a separate commit or stash.
  6. Never revert or discard user-owned changes without explicit permission.

Use git status --porcelain before editing. Ignore files named tasks.md when selecting the zone. Of the remaining changed paths, those under openspec/ select the specs zone; those outside it select the code zone. If only tasks.md files are changed, no zone is selected.

Workflow

  1. Draft and validate the proposal and fenced-Gherkin delta specs.
  2. Commit or stash specs-zone work before touching code.
  3. Establish the failing acceptance scenario or pending step before implementation.
  4. Implement the smallest change that makes the scenario pass. During OpenSpec apply, keep the active change's tasks.md updated as work completes, marking each completed task immediately. These progress updates may accompany implementation edits and commits.
  5. Keep the effective acceptance suite green with no pending or undefined steps.
  6. Commit or stash code-zone work before returning to specifications for sync or archive.

Red Flags

  • Implementing behavior with no active spec change.
  • Editing specs-zone and code-zone files in the same uncommitted unit of work (tasks.md is zone-neutral).
  • Writing implementation tasks before acceptance-test tasks.
  • Treating generated .feature files as the source instead of spec.md.
  • Running source-of-truth specs without active deltas when validating a change.

Stop and restore the workflow boundary when any red flag occurs.

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.