agentic-framework/agent-ops/skills/common/code-review/templates/user-review-template.md

User Review Required - {task_name}

Requested At

{YYYY-MM-DD or ISO-8601}

Status

USER_REVIEW

Reason

• Type: {milestone-lock | external-execution}
• Target: {agent-roadmap/phase//milestones/.md | exact runner/device/service/access target}
• Current review number: {review-number}
• Final verdict: {WARN or FAIL}
• Summary: {why the Milestone decision or user-controlled external execution blocks the next safe step}

Loop History

Plan	Review	Verdict	Note
{plan-log-0}	{code-review-log-0}	{PASS/WARN/FAIL/unknown}	{main issue or blocking reason}
{current-archived-plan-log}	{current-archived-review-log}	{WARN/FAIL}	{main issue or blocking reason}

Blocking Evidence

• Problem: {review finding summary}
• Current archived plan: {current-archived-plan-log}
• Current archived review: {current-archived-review-log}
• Verification command: {command or none}
• Actual output: {stdout/stderr excerpt or saved output path}
• Blocking rationale: {evidence matching the Milestone decision | evidence that the declared runner/transport was checked but automatic execution remains unsafe without user action}

Required User Action

• {Milestone 구현 잠금 > 결정 필요 item | exact access/authorization/environment/evidence action}

Resume Condition

• {concrete evidence proving the required action or decision is resolved, plus the next review/plan entry condition}

Next Execution Hint

• {the correct resolve-review, update-roadmap, or external-verification replan entry point and target path}

Closure Rules

• If the recorded user action and evidence resolve this stop as complete/PASS, update USER_REVIEW.md to the resolved state, write complete.log from agent-ops/skills/common/code-review/templates/complete-log-template.md, and move the task directory to the archive.
• If new implementation is required, the plan skill archives USER_REVIEW.md as user_review_N.log before writing a new PLAN-*-G??.md / CODE_REVIEW-*-G??.md pair.