Loading...
Loading...
Found 32 Skills
Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.
Use when implementing a Beat change — requires gherkin or proposal artifact to be done first
Cucumber best practices, patterns, and anti-patterns
This skill should be used when a designer is picking up a Task issue to add design coverage. Triggers on phrases like "I want to design task
This skill should be used when a developer or QA engineer wants to report a bug, create a bug ticket, document a test failure, log a defect, file an issue found during a QA session, or report something that is broken — for example "report a bug", "create a bug ticket", "I found a defect", "something is broken in task
Validate Behavior-Driven Development (BDD) documents against Layer 4 schema standards
[UDS] Guide through Behavior-Driven Development workflow
Use when starting a Beat change to create spec artifacts — not for task breakdown, implementation, or exploration