tdd-guide

To prioritize your next TDD move, this tool reads project documentation and design artifacts to score work candidates by vision alignment and criticality, outputting a recommendation with an exact command.

Analyzing design artifacts for TDD workflows involves scanning active designs under docs/tdd-designs/ and completed designs under docs/completed-tdd-designs/ to assess progress, surface blockers, and determine alignment with the project roadmap.

Project documentation scanning for TDD roadmap alignment works by reading docs/vision.md to understand the project purpose, then cross-referencing it with design artifacts to surface the highest-impact next work and known issues.

Yes, you need a specific project docs structure to get TDD design recommendations, specifically a docs/vision.md file and directories for active designs and completed designs to analyze progress and blockers effectively.

Yes, you can use intent context to guide TDD project prioritization. The Skill respects the intent provided when scoring candidates, generating a tailored recommendation with optional alternatives and the exact command to run.

A limitation of automated TDD design review is that it relies entirely on the presence and accuracy of your project documentation, design artifacts, and intent context to generate a recommendation, without executing or validating the actual code.