Task Resume Skill

Project Root Guard (Must Confirm First)

• Must be executed in the project root directory (

  .webnovel/state.json

  must exist)
• If the file does not exist in the current directory, first ask the user for the project path and

  cd

  into it
• After entering, set the variable:

  $PROJECT_ROOT = (Resolve-Path ".").Path

Workflow Checklist

Task Recovery Progress:
- [ ] Step 1: Load Recovery Protocol (cat "${CLAUDE_PLUGIN_ROOT}/skills/webnovel-resume/references/workflow-resume.md")
- [ ] Step 2: Load Data Specification (cat "${CLAUDE_PLUGIN_ROOT}/skills/webnovel-resume/references/system-data-flow.md")
- [ ] Step 3: Confirm Sufficient Context
- [ ] Step 4: Detect Interruption State
- [ ] Step 5: Display Recovery Options (AskUserQuestion)
- [ ] Step 6: Execute Recovery
- [ ] Step 7: Continue Task (Optional)

Reference Loading Levels (strict, lazy)

• L0: Do not load any references until interruption recovery needs are confirmed.
• L1: Only load the main recovery protocol file.
• L2: Load data specifications only during data consistency checks.

L1 (minimum)

• references/workflow-resume.md

L2 (conditional)

• references/system-data-flow.md

  (Only when verifying state fields/recovery strategies is required)

Step 1: Load Recovery Protocol (Mandatory Execution)

cat "${CLAUDE_PLUGIN_ROOT}/skills/webnovel-resume/references/workflow-resume.md"

• Prohibit Intelligent Continuation: High risk of context loss
• Recover Only After Detection: Do not guess the interruption point
• Must Confirm with User: Do not recover automatically

Step 2: Load Data Specification

cat "${CLAUDE_PLUGIN_ROOT}/skills/webnovel-resume/references/system-data-flow.md"

Step 3: Confirm Sufficient Context

• Recovery protocol is understood
• Step difficulty levels are known
• State structure is understood
• Principles of "Restart from Scratch" vs "Intelligent Continuation" are clear

Step Difficulty Levels (from workflow-resume.md)

Step 4: Detect Interruption State

python "${CLAUDE_PLUGIN_ROOT}/scripts/workflow_manager.py" detect

• No interruption → End the process and notify the user
• Interruption detected → Proceed to Step 5

Step 5: Display Recovery Options (Mandatory Execution)

• Task command and parameters
• Interruption time and elapsed duration
• Completed steps
• Current (interrupted) step
• Remaining steps
• Recovery options and risk levels

🔴 Interrupted Task Detected:

Task: /webnovel-write 7
Interruption Location: Step 2 - In the middle of chapter content generation

Completed:
  ✅ Step 1: Context Loading

Incomplete:
  ⏸️ Step 2: Chapter Content (1500 words written)
  ⏹️ Step 3-7: Not started

Recovery Options:
A) Delete semi-finished products and restart from Step 1 (Recommended)
B) Roll back to Ch6 and discard all progress of Ch7

Please select (A/B):

Step 6: Execute Recovery

python "${CLAUDE_PLUGIN_ROOT}/scripts/workflow_manager.py" cleanup --chapter {N} --confirm
python "${CLAUDE_PLUGIN_ROOT}/scripts/workflow_manager.py" clear

git -C "$PROJECT_ROOT" reset --hard ch{N-1:04d}
python "${CLAUDE_PLUGIN_ROOT}/scripts/workflow_manager.py" clear

Step 7: Continue Task (Optional)

/{original_command} {original_args}

Special Scenarios

Step 6 Interruption (High Cost)

Recovery Options:
A) Re-execute dual-chapter review (Cost: ~$0.15) ⚠️
B) Skip review and proceed to the next chapter (Can be reviewed later)

Step 4 Interruption (Partial State)

⚠️ state.json may be partially updated

A) Check and repair state.json
B) Roll back to the previous chapter (Safe)

Long Interruption (>1 Hour)

⚠️ Interruption has lasted over 1 hour

High risk of context loss
It is recommended to restart instead of continuing the unfinished content

Prohibited Actions

• ❌ Intelligently continue semi-finished content
• ❌ Automatically select recovery strategies
• ❌ Skip interruption detection
• ❌ Repair state.json without verification