spec-test

To automate extracting domain models and unit tests from a specification, provide a Plan file path and specification text. The tool analyzes the spec to identify entities, value objects, and pure functions, then drafts test-driven unit tests and appends them to the Plan.

Spec-driven design analysis for test-driven development is the process of parsing a specification to identify class responsibilities, domain events, and pure functions. It generates test cases and updates an existing Plan file to ensure traceability between the design and the spec.

Yes, you can use this tool to append unit tests to an existing Plan file. By applying a predefined template, it auto-updates the Plan with the extracted domain models, pure functions, and drafted test cases for faster implementation and traceability.

Yes, this works with plan-driven projects that rely on prior conversation context. It is designed for projects with an existing specification or prior conversation, updating the current Plan with a completed design based on that context.

The best way to generate domain events and entities from a project specification is to run an automated code-analysis that extracts domain models, identifies class responsibilities, and drafts unit tests directly into your Plan file.

You should not use automated spec-driven design analysis when your project lacks a formal specification or an existing Plan file. It requires a predefined template and an initial spec to extract domain models and generate test cases.