How this skill is triggered — by the user, by Claude, or both
Slash command
/kenken:iterate-resumeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **For Claude:** Resume an interrupted kenken iteration from saved state.
For Claude: Resume an interrupted kenken iteration from saved state.
Read .agents/kenken-state.json
If no state found:
/kenken:iterate to start."If state found:
/kenken:iterate-status)Based on user choice:
User: /kenken:iterate-resume
Claude:
kenken Status
Task: Add user authentication
Stage: TEST (3/4)
Phase: 3.4 Run Tests [blocked - code logic error]
...
Resume iteration from Phase 3.4 (Run Tests)?
[Yes, resume]
[Restart current stage]
[Start fresh]
User selects: Restart current stage
Claude:
Restarting TEST stage. Note: Previous error was a code logic error.
Recommend restarting from IMPLEMENT stage to fix the underlying issue.
Proceed with TEST stage anyway, or restart from IMPLEMENT?
[Restart from IMPLEMENT (recommended)]
[Proceed with TEST]
npx claudepluginhub kenkenmain/ken-cc-plugins --plugin kenkenResumes coding sessions by detecting blockers, reconciling STATE.md with filesystem, and suggesting next actions from checkpoints or plans.
Resumes a saved Hypo-Workflow pipeline from `.pipeline/state.yaml`, continuing from the next uncompleted step without replaying finished work. Handles lock files, worker separation, and subagent authorization.
Resumes a paused campaign at its last completed phase. Use when returning to a campaign after a session break.