Loading...
Loading...
Found 46 Skills
BDD-style behavior specification engine for the skill system. Use when: (1) defining a new skill's behavior before implementation, (2) validating a spec against the schema, (3) generating a behavior contract (Mermaid DAG) from a spec, (4) running structural acceptance tests against a built skill. Workflow: Spec → Test → Develop → Contract.
Build phase of RDD. Turns behavior scenarios into executable BDD specs, then implements via TDD (red/green/refactor). Enforces structure-vs-behavior separation, composable tests, and small reversible steps. Use after /rdd-decide when scenarios and domain model are approved.
QCSD Refinement phase swarm for Sprint Refinement sessions using SFDIPOT product factors, BDD scenario generation, and requirements validation.
Generate runnable Vitest and Playwright test files from BDD test cases and scaffold code. Use when generating test implementations.
Generates high-quality Gherkin (BDD) scenarios from functional requirements using a two-agent iterative cycle: a generator agent that creates/modifies the Gherkin and a reviewer agent that validates it and proposes improvements. The cycle repeats automatically until the Gherkin passes review. Use this skill whenever the user mentions: "generate Gherkin", "BDD scenarios", "Gherkin test cases", "Feature/Scenario/Given/When/Then", "requirements to Gherkin", "BDD specifications", or asks to transform functional requirements into behaviour tests. Also applies when the user brings a requirements document and wants test cases, acceptance criteria, or user stories with executable examples.
Loads orchestrate mode — a disciplined delivery loop that enforces BDD specs in specs/, real integration tests (no mocks), PR CI and CodeRabbit babysitting, and mandatory end-user QA via computer-use or CLI dogfooding before anything is considered done. Use when starting any non-trivial implementation task, feature build, or delivery where you want the work driven from spec to proven-shipped state rather than stopping at "tests pass".
TDD/BDD testing principles, test patterns, and coverage strategies
Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.
Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests', 'integration tests', 'E2E testing', 'test coverage', 'flaky tests', 'mocking', 'test fixtures', 'TDD', 'BDD', 'test automation'. NOT for manual QA processes, load/performance testing (use performance-engineer), or security testing (use security-auditor).
Create comprehensive unit tests, integration tests, and end-to-end tests using pytest for Python projects. Specializes in FastAPI testing with TestClient, async testing with pytest-asyncio, SQLModel/SQLAlchemy database testing, fixture generation, and test configuration setup. Use when you need test coverage, want to implement TDD/BDD, create test suites for functions or API endpoints, add edge case testing, or improve code quality with automated testing. Triggers include requests like "write tests for this module", "create pytest fixtures", "test this FastAPI endpoint", "setup pytest configuration", or "generate test file".
Use this skill when deciding what to test, choosing between test types, designing a testing strategy, or balancing test coverage. Triggers on test pyramid, unit vs integration vs e2e, contract testing, test coverage strategy, TDD, BDD, testing ROI, and any task requiring testing architecture decisions.
Use when choosing a testing strategy, right-sizing test coverage, or understanding test categories. Covers the Test Trophy model, test type tradeoffs, and guidance on balancing static analysis, unit, integration, and end-to-end tests. USE FOR: testing strategy, Test Trophy, test type selection, right-sizing test coverage, balancing test categories, choosing testing tools, test automation architecture DO NOT USE FOR: specific test category implementation (use static-analysis, unit-testing, integration-testing, e2e-testing, etc.), BDD specification authoring (use specs/documentation/gherkin)