moonspec-implement

Test-driven development automation starts with a Moon Spec story defined by spec.md, plan.md, and tasks.md files. The workflow enforces writing unit and integration tests before production code, providing a structured path from specification to verified implementation.

Starting a Moon Spec implementation workflow requires a feature directory containing spec.md, plan.md, and tasks.md files. These files define the Moon Spec story, establish the design mappings, and enforce a strict one-story scope before prerequisite checks run.

The Moon Spec workflow enforces a strict one-story scope by aligning the implementation exclusively with the active feature directory and its defined spec.md, plan.md, and tasks.md files. This keeps the test-driven development process focused without scope creep.

Yes, generating unit and integration tests before production code is the core feature of this test-driven development workflow. It orchestrates prerequisite checks and hooks to ensure tests are produced first, followed by an optional final verification step.

Turning a Moon Spec plan into verified production code is best done by automating the implementation workflow against the active feature directory. This reduces manual toil by guiding prerequisite checks, test-driven development, and source design mappings to completion.

A specification-driven workflow streamlines your test automation process by reducing manual toil and errors. It uses your plan.md and tasks.md to guide the generation of unit and integration tests before production code, ensuring verified implementation.