Handoff
Apply this skill to explicit requests to create or resume a
. Do not auto-apply it to general summaries, status questions, or ordinary “continue” requests.
Keep the roles separate.
- : the task contract defining what must be done, why, and under which conditions
- : the progress recording what has been done and the current state
A
neither replaces nor copies the
.
New handoff
Read the current repository evidence.
- / /
- the exact and of the current , if present
- actual changed files
- commands actually executed
- actual verification results
- completed and remaining work
- current blockers and next action
Mark only observed facts as
and only decisions confirmed with the user as
.
Commands not executed, prior claims, and model inferences are
.
The default path is
. Write to a temporary file in the same directory, atomically replace the target, and read it back.
Creating the artifact itself does not grant permission to change the product, Git, or remote state.
Preserve at least the following meaning in the Handoff.
text
Goal/Seed: <seed path 또는 current goal reference>
Status: pending | in_progress | completed | aborted | Blocked
Repository state: <branch, HEAD, worktree>
Decisions: <confirmed progress-relevant decisions>
Changed files: <observed paths | none>
Commands: <actually executed commands | none>
Verification: <check/result/evidence>
Completed work: <done items | none>
Remaining work: <unfinished items | none>
Open questions: <required decisions | none>
Risks: <remaining failure/regression risk>
Next step: <one executable immediate action>
Resume hints: <environment/order/command hints>
Disposition: reported | applied | pending
Do not copy the
’s
goal/scope/AC/implementation guidance
into the
.
When needed, reference the exact
.
🔴 CHECKPOINT · 🛑 STOP · Write/Resume Boundary
Before writing a new
or continuing a
:
- STOP and report when the current , , branch, , worktree, or required verification cannot be fresh-read.
- STOP and mark when evidence conflicts or the contract has drifted; do not resolve either condition inside the .
- STOP before writing if atomic replacement cannot be completed or readback fails; use by default and honor an explicit exactly.
- STOP at any product, Git, or remote publication approval boundary; the artifact does not grant that permission.
- If none of these conditions applies, continue without asking an extra question for a routine artifact update.
Resume
requests resuming work by comparing the
against the current Git and files.
First, fresh-read:
- the current and
- //
- changed files
- relevant verification evidence
- current remote state, if a exists
Then classify drift.
| Classification | Action |
|---|
| None | Continue from without additional questions |
| Nonessential | Record it and continue |
| Significant progress | Update the from current evidence and confirm only the necessary decisions |
| contract | Do not resolve it in the ; report that re-entering is required |
| Conflict | Show the incompatible evidence and mark |
| unverified | If the required state cannot be confirmed, mark |
may authorize continuing the work, but it does not replace approval to change the
’s
or permission to publish remotely.
Output
After successfully creating a new
, show only the path, current status, and next action briefly in chat.
Do not dump the full
body or evidence ledger.
When resuming, explain completed work, remaining work, blockers, and the immediate next action in a way that is easy for a person to understand.
Do not use
as an archive, current pointer, or global state.
Do not modify
or automatically commit/publish.