from claude-workflow11
Generate behavioral Gherkin .feature files from spec acceptance criteria; one feature per demoable unit and optional task-stub creation for downstream testing.
CW-Gherkin reads structured spec documents and translates acceptance criteria into behavioral Gherkin scenarios, producing one .feature file per demoable unit. Its focus is behavioral tests only — scenarios verify observable outcomes (UI text, HTTP responses, exit codes), not source-code structure. It can optionally create cw-testing task stubs to wire scenarios into a test board, but will not create tasks without explicit confirmation.
Use CW-Gherkin when you have a finished spec and need executable behavior descriptions for QA or automation. It's ideal in spec-driven development flows where a spec generator (cw-spec) triggers scenario creation, or when teams want consistent, reviewable feature files next to spec docs. Avoid using it for ad-hoc unit tests or structural checks — it enforces behavioral principles.
Primarily designed for Claude Workflow internal subagents and CI-driven automation; compatible with agent systems that can read/write repo files and create task stubs (e.g., Claude Code, pipeline agents).
This skill has not been reviewed by our automated audit pipeline yet.
