planifest Testing TDD
Overview
Use this skill to drive implementation through fast red-green-refactor cycles with explicit design feedback.
Scope Boundaries
- Use when implementation should be guided by failing tests first.
- Typical requests:
Develop a new feature with strict red-green-refactor discipline.Reduce refactor risk with micro-cycle verification.Use tests to shape API and domain design incrementally.
- Do not use when:
- Tests are added only after full implementation.
- The primary goal is performance/load experimentation.
Inputs
- Target behavior and constraints
- Existing test harness and coding standards
- Cycle-time and commit-granularity expectations
Outputs
- Red-green-refactor evidence at incremental steps
- Decision record for cycle design and test scope
- Verification checklist for regression safety
Workflow
- Write a failing test for the smallest next behavior.
- Implement the minimal change to pass.
- Refactor while keeping tests green.
- Repeat in small increments with explicit intent.
- Publish residual risks and uncovered behaviors.
Quality Gates
- Every implementation step is preceded by a failing test.
- Steps remain small enough for quick diagnosis and rollback.
- Refactoring preserves behavior with green evidence.
- Assumptions and unresolved risks are explicit.
Failure Handling
- Stop when implementation proceeds without prior failing tests.
- Escalate when cycle size becomes too large for reliable feedback.
Bundled Resources
references/trigger-and-examples.md: trigger patterns, anti-patterns, and deliverable expectations.