review

To generate a structured code review, issue a wave or task review command like "review wave N" or "review task X.Y". This analyzes completed development work and produces a comprehensive review with acceptance criteria, spec alignment, and issue prioritization.

Yes, you can run a security review using STRIDE and OWASP checks. The review process supports optional security analysis with cross-cutting considerations to identify vulnerabilities and ensure traceability across your development sessions.

Wave-level reviews analyze broader development phases, while task-level reviews focus on specific individual tasks. Both scopes generate persistent review artifacts with defined file formats and section headings to ensure formal, traceable context across sessions.

Fix plan analysis and verification are orchestrated using independent subagents. This enforces a formal review lifecycle with status updates, ensuring that proposed fixes are thoroughly analyzed and verified against the original specifications.

Yes, the code review process enforces a formal review lifecycle with defined file formats, section headings, and status updates. This structure ensures consistent quality and traceability across sessions for codework, security checks, and verification.

The best way to ensure spec alignment and traceable insights is to use a structured review process that prioritizes issues and maintains persistent review artifacts. This enforces formal lifecycles and generates comprehensive, ready-to-use reviews.