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
- intent-driven-dev/skillsedited, first seen Aug 22, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- intent-driven-dev/skills★ 987% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- acceptance-test-authoringSkill
- architectural-decision-recordsSkill
- c4-diagramsSkill
- gherkin-authoringSkill
- glossarySkill
- grill-meSkill
- openspec-git-disciplineSkill
- test-driven-developmentSkill
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
- Very specific: line 10
Use OpenSpec spec.md files as the executable source of truth.
- Very specific: line 12
REQUIRED SUB-SKILL: Use gherkin-authoring when drafting or modifying fenced Gherkin.
- Very specific: line 14
REQUIRED SUB-SKILL: Use acceptance-test-authoring when configuring or modifying the acceptance runner, extractor, linting, step …
- Distinctive: line 24
When this skill is active, its artifact references override the corresponding templates from the configured OpenSpec schema.
- Distinctive: line 35
Before crossing zones, finish and commit or stash the current zone.
- Distinctive: line 36
Never commit specs-zone files and code-zone files together.
- Distinctive: line 38
Never revert or discard user-owned changes without explicit permission.
- Very specific: line 40
Use git status --porcelain before editing.
- Distinctive: line 45
Commit or stash specs-zone work before touching code.
- Distinctive: line 48
Keep the effective acceptance suite green with no pending or undefined steps.
- Distinctive: line 49
Commit or stash code-zone work before returning to specifications for sync or archive.
- Distinctive: line 59
Stop and restore the workflow boundary when any red flag occurs.
≈ “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.
Files
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.mdfrom references/spec.md, not fromopenspec/schemas/intent-driven/templates/spec.md. - Draft
tasks.mdfrom references/tasks.md, not from the schema task template, preserving acceptance-test-first ordering.
BDD Zone Rules
- Code is written only for an active change under
openspec/changes/whose scenarios describe the behavior. - A unit of work edits either the specs zone (non-
tasks.mdfiles underopenspec/) or the code zone (non-tasks.mdfiles outsideopenspec/), never both while changes are uncommitted. - Before crossing zones, finish and commit or stash the current zone.
- Never commit specs-zone files and code-zone files together.
- Any file named
tasks.mdis 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. - 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
- Draft and validate the proposal and fenced-Gherkin delta specs.
- Commit or stash specs-zone work before touching code.
- Establish the failing acceptance scenario or pending step before implementation.
- Implement the smallest change that makes the scenario pass. During OpenSpec apply, keep the active change's
tasks.mdupdated as work completes, marking each completed task immediately. These progress updates may accompany implementation edits and commits. - Keep the effective acceptance suite green with no pending or undefined steps.
- 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.mdis zone-neutral). - Writing implementation tasks before acceptance-test tasks.
- Treating generated
.featurefiles as the source instead ofspec.md. - Running source-of-truth specs without active deltas when validating a change.
Stop and restore the workflow boundary when any red flag occurs.
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
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.

