review-with-subagent

Automating code review against a project plan involves spawning a subagent to check changes for plan alignment, code quality, and bug detection. This ensures post-implementation validation and documentation consistency without manual effort.

A subagent workflow for quality assurance spawns a dedicated agent to review changes against quality standards, enforcing architecture decisions and security considerations while providing prioritized feedback to guide fixes.

To enforce plan alignment and code quality checks automatically, orchestrate a subagent during your post-implementation workflow to detect bugs, validate architecture decisions, and ensure documentation consistency.

Yes, you can prioritize code review feedback using P1, P2, and P3 categories to guide fixes and improvements, ensuring critical issues are addressed first during the subagent review process.

You need to spawn a subagent for documentation consistency checks during post-implementation workflows where deep code quality checks are required to align changes with the project plan and quality standards.