Stats
Actions
Tags
Write BDD Gherkin feature files and fabricate test data from a specification. Use to turn acceptance criteria or an EPIC into business-language `.feature` scenarios — Scenario Outline with Examples, explicit edge cases, no implementation detail. Trigger on "write Gherkin", "write feature files", "BDD scenarios for this acceptance criterion", "fabricate test data".
How this skill is triggered — by the user, by Claude, or both
Slash command
/meaningfy-architecture:bdd-gherkinThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Translate a specification into precise, business-language Gherkin features that define
Translate a specification into precise, business-language Gherkin features that define
what the system should do in observable, testable terms — not how. Bridges the
spec (epic-planning) and the implementation.
.feature files under tests/features/ (or the project's path), named
<capability>.feature, one file per coherent business capability.Scenario Outline + Examples: for data-driven coverage:Scenario Outline: <description>
Given <precondition>
When <action with parameter>
Then <expected outcome>
Examples:
| parameter | expected |
| value1 | result1 |
| value2 | result2 |
Scenario Outline used wherever multiple data variations apply.Owns: feature files + test data. Does NOT write step definitions or production code
(that is the implementer's job, following cosmic-python + superpowers:test-driven-development),
and does NOT plan (epic-planning) or score specs (clarity-gate).
Related: epic-planning, clarity-gate, cosmic-python.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub meaningfy-ws/skillery --plugin meaningfy-architecture