Test Driven Development
Skill ActiveUse 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
To enforce Test-Driven Development by ensuring tests are written first, verified to fail, and then minimal code is written to pass them, guaranteeing behavioral verification.
Features
- Enforces Test-Driven Development methodology
- Requires tests to fail before implementation code is written
- Provides step-by-step guidance for the Red-Green-Refactor cycle
- Details common TDD anti-patterns and rationalizations
- Ensures tests verify behavior, not just implementation
Use Cases
- Implementing new features using TDD
- Fixing bugs with a test-first approach
- Refactoring code while maintaining test coverage
- Ensuring code quality through rigorous testing practices
Non-Goals
- Writing tests after implementation code
- Skipping TDD for perceived simple code or prototypes
- Accepting tests that pass immediately without prior failure
- Treating testing as an optional afterthought
Workflow
- Write a failing test for the desired behavior (RED).
- Verify that the test fails correctly.
- Write the minimal amount of code to make the test pass (GREEN).
- Verify that the test passes and all other tests still pass.
- Refactor the code while keeping tests green.
- Repeat the cycle for the next piece of behavior.
Practices
- Test-Driven Development
Maintenance
- warning:Commit recencyThe last commit was over 90 days ago, indicating potential lack of recent maintenance.
Trust
- warning:Issues AttentionThere are 6 open issues and 8 closed issues in the last 90 days, indicating a low closure rate and potentially slow maintainer response.
Versioning
- warning:Release ManagementThere is no explicit versioning system (like semver in frontmatter or CHANGELOG) and installation instructions reference `main`, making it difficult to pin a specific version.
Installation
First, add the marketplace
/plugin marketplace add NeoLabHQ/context-engineering-kit/plugin install tdd@context-engineering-kitQuality Score
Trust Signals
Similar Extensions
Dart Matcher Best Practices
100Best practices for using `expect` and `package:matcher`. Focuses on readable assertions, proper matcher selection, and avoiding common pitfalls.
Coding Standards
100Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
Definition Of Done
100Mandatory checks to run before completing any task that touches md files or dart code in this repository.
Agent Coder
99Agent skill for coder - invoke with $agent-coder
Writing Skills
99Use when creating new skills, editing existing skills, or verifying skills work before deployment
Workflow Patterns
99Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.