test-driven-development Skill
Use when implementing any feature or bugfix, before writing implementation code Published by openai in plugins.
What is test-driven-development Skill?
Use when implementing any feature or bugfix, before writing implementation code Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Writing
- Testing use cases
- Writing use cases
Technical details
- Install or run with Copy skill directory
When to use test-driven-development Skill
- Use it for testing.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/superpowers/skills/test-driven-development/SKILL.md
What it does
Use when implementing any feature or bugfix, before writing implementation code
Skill instructions
Test-Driven Development (TDD) Overview Write the test first. Watch it fail. Write minimal code to pass. Core principle: If you didn't watch the test fail, you don't know if it tests the right thing. Violating the letter of the rules is violating the spirit of the rules. When to Use Always: - New features - Bug fixes - Refactoring - Behavior changes Exceptions (ask your human partner): - Throwaway prototypes - Generated code - Configuration files Thinking "skip TDD just this once"? Stop. That's rationalization. The Iron Law NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST Write code before the test? Delete it. Start over. No exceptions: - Don't keep it as "reference" - Don't "adapt" it while writing tests - Don't look at it - Delete means delete Implement fresh from tests. Period. Red-Green-Refactor dot digraph tddcycle { rankdir=LR; red [label="RED\nWrite failing test", shape=box, style=filled, fillcolor="ffcccc"]; verifyred [label="Verify fails\ncorrectly", shape=diamond]; green [label
Explore related resources
Frequently asked questions
What is test-driven-development?
test-driven-development is a open-source AI agent skill with Copy skill directory. Use when implementing any feature or bugfix, before writing implementation code
Who is test-driven-development best for?
test-driven-development is best for reusing agent instructions, scripts, and references, testing workflows, writing workflows.
How do I install test-driven-development?
Install or run test-driven-development using Copy skill directory. Check test-driven-development for the latest setup command.
Is test-driven-development actively maintained?
test-driven-development may need a closer maintenance check before production use.
