test-driven-development

To generate Rust test stubs from a spec file, you provide the .spec.md file as input to trigger automatic Given/When/Then criteria scaffolding. This creates concrete test structures aligned to repository patterns, enabling immediate iteration on the RED -> GREEN -> REFACTOR cycle.

Enforcing test-first development in Rust requires generating concrete test scaffolds from specs, tasks, or descriptions before writing implementation code. This approach validates requirements upfront, enforces cargo test preflight checks, and reduces downstream rework by ensuring test coverage drives the development cycle.

Yes, you can use TDD with ad-hoc task descriptions instead of formal specs. The skill supports three input modes: spec-based files, task-driven .code-task.md requirements, and description-driven scenarios, allowing flexible test stub generation regardless of your documentation format.

Yes, this TDD workflow integrates proptest guidance and enforces cargo test preflight checks. It compiles generated test stubs automatically and incorporates backpressure concepts to track coverage and iteration speed during the test-first development cycle.

Generating test stubs before implementation code ensures test-first development by validating requirements prior to coding. This unified TDD workflow reduces downstream rework, provides immediate guidance for the RED -> GREEN -> REFACTOR cycle, and helps teams catch specification gaps early.