specdo-receive-code-review

Automate code-review feedback processing by validating concrete feedback against an active apply payload to determine the next workflow step. The system checks for complete context and routes outcomes to apply, verification, debugging, or rework based on the feedback content.

Code-review feedback is actionable when it names a specific file, behavior, missing evidence, risk, or failing condition. The system validates these elements before gating the workflow to ensure feedback drives meaningful routing decisions.

Validate apply context by requiring task_scope, handoff_payload, gate_history, and invoked_from to be present. If any prerequisite is missing, the system routes to specdo-apply with a needs_apply_context flag to gather the required information.

Code-review feedback triggers routing outcomes including accepted_unapplied, accepted, rejected, failure_exposed, or lifecycle_reassessment_required. Each outcome appends gate_history entries to guide subsequent workflow decisions.

Lifecycle reassessment is needed when review feedback exposes failures or requires rethinking the current approach. The system produces a lifecycle_reassessment_required outcome to signal that the workflow must re-evaluate its direction.

Processing review feedback requires an active apply payload with complete context. Without it, the system cannot validate feedback and will route to specdo-apply to establish the necessary task_scope, handoff_payload, and gate_history.