testing-tdd
Testing TDD
Overview
Use this skill to drive implementation through fast red-green-refactor cycles with explicit design feedback.
Scope Boundaries
- Use when implementation should be guided by failing tests first.
- Typical requests:
Develop a new feature with strict red-green-refactor discipline.Reduce refactor risk with micro-cycle verification.Use tests to shape API and domain design incrementally.
- Do not use when:
- Tests are added only after full implementation.
- The primary goal is performance/load experimentation.
Inputs
- Target behavior and constraints
- Existing test harness and coding standards
- Cycle-time and commit-granularity expectations
Outputs
- Red-green-refactor evidence at incremental steps
- Decision record for cycle design and test scope
- Verification checklist for regression safety
Workflow
- Write a failing test for the smallest next behavior.
- Implement the minimal change to pass.
- Refactor while keeping tests green.
- Repeat in small increments with explicit intent.
- Publish residual risks and uncovered behaviors.
Quality Gates
- Every implementation step is preceded by a failing test.
- Steps remain small enough for quick diagnosis and rollback.
- Refactoring preserves behavior with green evidence.
- Assumptions and unresolved risks are explicit.
Failure Handling
- Stop when implementation proceeds without prior failing tests.
- Escalate when cycle size becomes too large for reliable feedback.
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