You MUST use this when implementing any feature or bugfix where tests are practical — before writing implementation code. Enforces red-green-refactor with verification at each step. Do not use for docs-only or config-only changes with no testable behavior.
How to install test-driven-development?
felipemelendez/llm-orchestrator/test-driven-development
$npx -y skills add felipemelendez/llm-orchestrator --skill test-driven-developmentInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/felipemelendez/llm-orchestrator" --skill "felipemelendez/llm-orchestrator/test-driven-development"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/felipemelendez/llm-orchestrator" that are relevant to the current task. Run `npx skills add "https://github.com/felipemelendez/llm-orchestrator"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- tddTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.Jul 2026
- test-driven-developmentUse when implementing any feature or bugfix, before writing implementation codeJul 2026
- qaInteractive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues.Jul 2026
- verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output…Jul 2026
- webapp-testingToolkit for interacting with and testing local web applications using Playwright.Jul 2026
- playwright-best-practicesUse when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking…Jul 2026
