owainlewis/tdd
skills/tdd/SKILL.md
Test-first variant of implement: understand the desired behavior, write a failing test, make it pass, then simplify.
$ install --global
skillsauthnpx skillsauth add owainlewis/blueprint tddInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 12, 2026, 6:31 AM143.3s1 file scanned
SKILL.md
- name:
- tdd
- description:
- Test-first variant of implement: understand the desired behavior, write a failing test, make it pass, then simplify.
- user-invocable:
- true
- argument-hint:
- <task reference or behavior> e.g. 'LIN-123' or 'retry logic for API client'
Test-Driven Development
Use this for behavioral changes where a failing test can describe the desired outcome before implementation.
Workflow
1. Understand
- Read the request, task, issue tracker item, plan, spec, and relevant code as available.
- Identify the desired behavior, existing contracts, failure paths, and verification.
- If a spec exists, note its invariants, decisions, and testing strategy.
- Ask before writing tests when missing information would materially change behavior, scope, safety, contracts, data shape, or verification.
2. Red
- Write the smallest failing test that proves the desired behavior or reproduces the bug.
- Run it and confirm it fails for the expected reason.
3. Green
- Write the minimum implementation needed to pass the test.
- Preserve existing contracts unless the task explicitly changes them.
- Add failure-path tests where they matter.
4. Refine
- Simplify code and tests while they stay green.
- Run the focused checks first, then the project's wider checks, before finishing.
- Report the failing-then-passing test and final verification.
Rules
- Do not write implementation code before a failing test for the behavior.
- If an assumption is low-risk, make it explicit and keep moving.
- Tests describe behavior, not implementation details.
- Prefer real boundaries over mocks when practical.
- Skip TDD for documentation, formatting, or non-behavioral scaffolding work.
Related Skills
owainlewis/pr
tools
VerifiedTrustedCommunity
Commit, push, and open a pull request with a clear description. Use when finished work on the current branch needs to become a PR.
143SKILL.mdUpdated Jun 12, 2026
owainlewis/multitask
development
VerifiedTrustedCommunity
Run several tickets to draft PRs at the same time, one isolated worker per ticket. Use when the user passes multiple tickets and wants them worked in parallel. Composes task-to-pr per ticket; never writes code itself.
143SKILL.mdUpdated Jun 12, 2026
owainlewis/task-to-pr
development
VerifiedTrustedCommunity
Turn one ticket into a draft PR. Use when the user passes a ticket reference (JIRA-123, LIN-123, github#456, an issue URL) and expects code, tests, review, and a PR. Use implement when no PR is expected; use multitask for several tickets at once.
143SKILL.mdUpdated Jun 11, 2026
owainlewis/implement
development
VerifiedTrustedCommunity
Turn one scoped task into a verified diff: code, tests, verification, report. The inner build step of the delivery flow. Use directly when the workspace is prepared and no PR is expected; use task-to-pr when a ticket should become a PR.
143SKILL.mdUpdated May 10, 2026