review-cycle

Automating an end-to-end feature review cycle requires a workflow contract to orchestrate audit, review, fix, verify, documentation-update, and closeout phases. This coordination enforces strict setup validation while producing and validating artifacts like audit-findings.md and fix-plan.md.

Feature lifecycle governance is the end-to-end coordination of audit, review, fix, verify, and closeout phases for a feature. It works by enforcing strict setup validation and maintaining persistent per-feature state under docs/phaseN/feature-slug/ across resumable cycles.

To start a review cycle, provide the phase_number, feature_slug, and task_summary parameters. This initiates the orchestration sequence, which runs route-level audit through closeout and commits the final artifacts under the per-feature docs/phaseN/feature-slug/ directory.

Yes, you can resume an incomplete review cycle. The workflow tracks persistent per-feature cycle state and artifacts under docs/phaseN/feature-slug/, allowing execution to resume from the interrupted phase without losing previous audit or review progress.

Yes, feature lifecycle governance requires a valid setup and a review-cycle workflow contract. It enforces strict setup validation before execution, ensuring the environment meets prerequisites for continuous auditor, reviewer, and implementor tracking across the cycle.

During an automated review cycle, the workflow enables artifacts like audit-findings.md, review-findings.md, fix-plan.md, and fix-report.md to be produced and validated. These documents track governance progress from audit through final closeout.