Acceptance Test Authoring

When spec-as-source is active, the acceptance suite executes the Gherkin specs that live under openspec/ against the running application. Specs are Markdown files named spec.md: Markdown headings carry the capability, requirement, and scenario structure, while column-0 gherkin fences contain only Given/When/Then steps. The runner extracts them into real .feature files on every run, synthesizing Feature:/Rule:/Scenario: from the headings.

This format is opt-in. Loading this skill without spec-as-source does not override the configured OpenSpec schema templates.

Everything in this file is stack-agnostic. Tool-specific filenames, dependencies, commands, and examples live in the stack packs.

Choosing The Stack

The project's acceptance stack is declared as stack: in openspec/config.yaml:

schema: intent-driven
stack: javascript      # javascript | python

Resolve it in this order: