Continue Claude Code Work

Continue means execute the still-unfinished business task. It does not mean summarize the transcript, perfect the history tool, or start a new experiment.

Step 1: Obtain a verified read receipt

Invoke daymade-claude-code:read-claude-code-history for the exact Session. Ask that Skill for a chronological evidence briefing, not separate “last user” and “last assistant” buckets. If the Session ID is unknown, use its search/inventory route first.

Do not act until the receipt states:

• exact Session ID and project;
• sources and time coverage;
• compaction and raw-chronology boundaries;
• every retained human request, including queued prompts;
• end reason, unresolved calls, files touched, and explicit gaps.

If a clipped section could contain the objective or a correction, re-read it with the reader's full mode. If identity, ancestry, or authorship is unresolved, stop; continuing from a guessed Session is worse than asking for the missing evidence.

Step 2: Rebuild the continuation contract

Before the first project-changing tool call, write this compact internal contract from evidence. Do not invent a value to fill a blank.

Field	Evidence required
Original business outcome	Earliest still-governing human request, not a later implementation detail
Current explicit request	Latest human request that is not merely “继续”
Already completed	Independent current-state verification, not the old Agent's claim
Still unfulfilled	Requested result with no completion evidence
User corrections / do-not-repeat	Human messages that rejected a route, output, or assumption
Proven assets and successful routes	Existing code, docs, Skills, outputs, or commands that previously worked
Next direct action	One action whose success visibly reduces the unfulfilled business result