implement-spec

Automating specification implementation requires coordinating subagents to handle coding, review, and testing phases sequentially. This approach streamlines the process by using a comprehensive code-review checklist and performing a final verification gate before deployment to ensure quality and compliance.

Subagent coordination for code review works by deploying specialized agents to evaluate code changes against a comprehensive checklist. It ensures every modification adheres to compliance standards, automates unit and integration tests, and updates documentation automatically to maintain overall quality.

Yes, an AGENTS.md file is required to coordinate specification implementation. This file provides the necessary coordination instructions for the subagents, ensuring they can accurately execute the implementation phases, run testing automation, and perform documentation updates.

To run unit and integration tests automatically during spec implementation, you trigger the process using the 'implement spec' command. The coordinated subagents execute the testing automation to verify functionality and integration with existing systems before reaching the final verification gate.

The best way to ensure documentation updates during feature implementation is to integrate them into the automated specification workflow. Coordinated subagents maintain up-to-date documentation for new features and changes automatically as part of the end-to-end implementation process, preventing manual oversight.

Yes, you can implement a specific phase of a specification instead of the entire spec. The implementation process is flexible enough to coordinate subagents for individual phases, applying the same code review, testing, and verification standards to the targeted section.