diff --git a/PROCESS.md b/PROCESS.md
index c27b7bb..88f674f 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -11,7 +11,9 @@ UR acceptance scenario -- may require --> SR
 SR -> CODE -> TEST_CASE -> TEST_RESULT
 
 EPIC: PROPOSED -> IN_PROGRESS -> IN_REVIEW -> DONE
+      IN_REVIEW -> IN_PROGRESS (a human's not-yet at completion review)
 UR/SR: PROPOSED -> IN_PROGRESS -> IN_REVIEW -> DONE
+      IN_REVIEW -> IN_PROGRESS (returned with their Epic)
       PROPOSED -> DONE (verified existing behavior, explicit acceptance)
         BLOCKED | DEFERRED | OBSOLETE when applicable
 
@@ -106,7 +108,11 @@ than revising it in place.
 
 `IN_REVIEW` means implementation is complete and awaits human completion
 approval. The ownership lock, approved proposal and prior published requirement
-content remain unchanged. `DONE` follows human completion approval: atomically
+content remain unchanged. A human's not-yet at completion review returns the
+Epic and its owned requirements to `IN_PROGRESS` with the plan, the
+implementation approval and the ownership kept; record it with the
+presentation the human declined, continue the build and submit for review
+again. `DONE` follows human completion approval: atomically
 publish the approved content, increment each requirement revision once, retain
 an immutable accepted version with criteria and trace meaning, record the
 actor, time, reason and originating Epic, and release ownership. A failed write
diff --git a/skills/rdd-completion-review/SKILL.md b/skills/rdd-completion-review/SKILL.md
index d9eb6a3..ddd9cf0 100644
--- a/skills/rdd-completion-review/SKILL.md
+++ b/skills/rdd-completion-review/SKILL.md
@@ -43,6 +43,11 @@ still-published requirements, ownership, implementation, traces and evidence.
    per requirement, immutable accepted versions with criteria and trace meaning,
    attributable Epic/requirement audit and released ownership. A failed action
    must leave all effects unchanged; a repeated completion must not republish.
+   If the human answers not yet, record that answer with the unchanged
+   retained presentation as a return to implementation through the CLI. Read
+   back the Epic and its owned requirements IN_PROGRESS with the plan, the
+   implementation approval and the ownership unchanged, continue the build,
+   and renew whatever changed before submitting for review again.
 6. After that publication is read back, use the CLI to mark each backlog, gap
    or tooling record routed to the Epic as closed by the Epic, and read each
    record back. If the human wants a record left open, leave it open and add