tdd-analyzing

To determine TDD implementation scope, you analyze SPECS documents and existing code to extract contracts, dependencies, and architectural concerns, producing an ANALYSIS.md file that outlines the scope, priorities, and structure to guide downstream Code phase planning.

Prioritizing TDD tasks involves parsing your SPECS and code structure to identify dependencies, then organizing the implementation work into a clear priority order based on those extracted dependencies to scaffold your Code phase.

You generate an analysis document for TDD planning by running an analysis process during the Code phase that parses your SPECS and existing code, outputting an ANALYSIS.md file at your project root with clearly labeled sections for Scope, Priority, and Structure.

You need to analyze specs before writing tests when you require a structured implementation plan, allowing you to extract contracts and dependencies from SPECS and code to establish a clear scope and priority order for your TDD workflow.

Yes, tdd-analyzing works without external dependencies or plugins, operating directly on your project's SPECS and existing code structure to generate the ANALYSIS.md file at the project root during the Code phase.