mspec-implement

You can automate TDD red→green test execution for mspec by running the implementation workflow, which guides you through writing failing tests and then writing code to pass them. This streamlines development by automating the mspec implementation steps.

Anchors in mspec are traceability markers that link each code change directly to its corresponding specification. By using anchors during implementation, you ensure that code modifications remain properly synchronized and traceable to their originating requirements.

To start the implementation workflow for a new mspec change request, you run the `/mspec:implement` command. This initiates the automated process of writing initial tests and implementing the required code changes using TDD and anchors.

The mspec implementation workflow automates the test-driven development process, guiding you through the red→green cycle and anchor usage. While it streamlines TDD practices, understanding basic TDD concepts will help you effectively manage spec-code synchronization.

The mspec implementation workflow operates without external dependencies, using internal scripts to automate the red→green test execution and anchor-based traceability. You only need the mspec framework environment setup to begin writing tests and implementing code changes.

You should use the mspec implementation workflow when starting a new change request in mspec to maintain spec-code synchronization. It is ideal for reducing manual effort in TDD practices, ensuring every code change is anchored to its corresponding spec.