plan-review-implementation

Automated code review for implementation iterations scans finished plans to surface bugs, edge cases, and security concerns. It logs findings in PLANS.md documentation and creates Linear Todo issues for any detected remediation tasks before determining merge readiness.

Moving Linear issues from review to merge requires evaluating completed implementation iterations for readiness. The review process checks for type-safety gaps, resource leaks, and async issues, advancing eligible Linear tasks to the merge phase only when all criteria are satisfied.

Detecting security vulnerabilities and edge cases during post-implementation review involves OWASP-based analysis of finished code iterations. The review identifies type-safety gaps, resource leaks, and async issues, automatically generating fix plans or new Linear issues for tracked remediation.

PR creation can be triggered automatically once all Linear review tasks are resolved. The workflow ensures proper labeling and status transitions are complete, documentation is updated in PLANS.md, and all Todo remediation items are closed before initiating the pull request.

A PLANS.md file is required to run the automated post-implementation workflow. The review process enforces logging review findings and documentation updates within this file, ensuring structured tracking of bugs, edge cases, and fix plans before advancing any Linear issues.

Managing bug tracking and fix plans after a code iteration is best handled by integrating automated review with Linear issue tracking. The workflow detects bugs and edge cases, creates Todo items for remediation, logs findings in PLANS.md, and advances tasks to merge once resolved.