perfectcode-zen-evaluation

Plan-driven code evaluation requires a written plan document stored in .opencode/plans/ and a completed software implementation to survey. The evaluation workflow uses these inputs to apply domain-specific criteria and produce a scored, multi-dimension report highlighting gaps and deviations.

Evaluating a Zen build compares the completed implementation against its written plan in .opencode/plans/ to validate alignment. It orchestrates multiple evaluators to score code quality and test coverage, producing actionable feedback for PR reviews or post-build validation.

Automated code review handles plan fidelity and test coverage by applying an evaluation workflow that loads the plan and surveys the actual implementation. It uses domain-specific criteria to score multi-dimension results and surface gaps, deviations, and concrete improvement actions.

Yes, you can generate a scored evaluation report for a software engineering project by triggering a structured evaluation workflow. It requires plan content and an implementation survey to assess architectural integrity and produce actionable, multi-dimension results with improvement suggestions.