testing-bdd
Testing BDD
Overview
Use this skill to encode requirement intent as executable behavior scenarios that product, QA, and engineering can all review.
Scope Boundaries
- Use when behavior semantics need alignment across stakeholders before or during implementation.
- Typical requests:
Turn ambiguous requirements into Given-When-Then scenarios.Align PO, QA, and engineering on acceptance behavior.Define executable acceptance evidence before release.
- Do not use when:
- The primary task is load/performance benchmark design (
performance-*). - The task is operational monitoring/alert policy (
observability-*).
- The primary task is load/performance benchmark design (
Inputs
- Requirement candidates and acceptance concerns
- Domain language and business rules
- Existing test policy and release constraints
Outputs
- Scenario suite in Given-When-Then format with requirement mapping
- Decision record describing scenario strategy and assumptions
- Verification checklist with pass/fail signals
Workflow
- Clarify behavior decisions and non-negotiable constraints.
- Model happy-path, alternate, and failure behavior in ubiquitous language.
- Compare scenario granularity options and choose one with rationale.
- Make scenarios executable and traceable to acceptance decisions.
- Publish residual risks and unresolved semantic disputes.
Quality Gates
- Scenarios are understandable by non-engineering stakeholders.
- Acceptance semantics are explicit and testable.
- Assumptions and confidence are documented.
- Evidence is reproducible and linked to requirements.
Failure Handling
- Stop when critical behavior cannot be expressed unambiguously.
- Escalate when stakeholder interpretations remain incompatible.
Bundled Resources
references/trigger-and-examples.md: trigger patterns, anti-patterns, and deliverable expectations.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9