spec-review

Automate spec-compliance review by spawning subagents to compare your implementation against provided specifications. The loop iteratively identifies gaps and applies fixes until compliance or the iteration limit is reached.

Yes, you can use a GitHub issue URL as a spec source for automated code review. The review loop also accepts design documents or inline text, and targets specific file paths or diffs to scope the verification.

The iteration loop verifies code against a design document by using a dedicated spec-review subagent to find gaps and a fix subagent to resolve them. It repeats until all issues are resolved or a maximum iteration count is hit.

The best way to scope an automated spec review to a specific code diff is to provide the diff as the target alongside your spec source. This focuses the subagents' comparison and compliance verification strictly on the changed files.

When the maximum iteration limit is reached during spec compliance verification, the loop stops and generates a final compliant report. This bounded loop ensures the process terminates with explicit exit criteria.

No, you do not need to provide explicit exit criteria manually. The automated spec-compliance loop enforces bounded iterations internally, stopping when all issues are resolved or the maximum number of iterations is reached.