test-driven-development Skill
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first Published by microsoft in FluidFramework.
What is test-driven-development Skill?
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first Published by microsoft in FluidFramework. 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
- Data analysis
- Writing
- Testing use cases
- Data analysis 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 data analysis.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/FluidFramework
- Skill file: .agency/plugins/nori/skills/test-driven-development/SKILL.md
What it does
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Skill instructions
<required CRITICAL Add the following steps to your Todo list using TodoWrite: 1. Write failing tests (RED phase) 2. Create a subagent using the nori-task-runner to evaluate test quality. - Ensure that each test does not just test mocks. If it does, remove the test and try again. - Ensure each test does not test implementation detail. If it does, rewrite the test so that it tests boundary behavior. - Ensure each test does not test data structure format or types. If it does, remove the test and try again. - Ensure each test does not test for removed behavior. For example, if some behavior has been deprecated, do not write a test that simply confirms the behavior no longer works. - Evaluate if the test treats the interior of the test boundary as a blackbox. You should not know anything about interior variables, function calls, or control flow. 3. Verify the test fails due to the behavior of the application, and NOT due to the test. <system-reminderIf you have more than one test that you n
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 - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by.
Who is test-driven-development best for?
test-driven-development is best for reusing agent instructions, scripts, and references, testing workflows, data analysis 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.
Auto-fetched from GitHub.
