Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub varaku1012/aditi.code --plugin steering-context-generatorHow this command is triggered — by the user, by Claude, or both
Slash command
/steering-context-generator:steering-resumeThe summary Claude sees in its command listing — used to decide when to auto-load this command
--- description: Resume an interrupted generation from the last checkpoint --- # Steering Context Generator - Resume Continue a generation that was interrupted or failed. ## Quick Start ## When to Use - ⚠ Generation was interrupted (Ctrl+C, timeout, crash) - ⚠ Agent execution failed mid-way - ⚠ System resources exhausted - ⚠ Network connectivity issues ## How It Works ### Checkpoint System The system automatically saves checkpoints: ### Resume Logic ## Expected Output ## Manual Resume If automatic resume fails: ## Clearing Fail...
/resumeResumes a previously-running Claude agent by ID, picking up its transcript and continuing the interrupted task.
/context-managerSaves and restores full task context across sessions, enabling pause-and-resume for any sprint. Supports save, restore, handoff, pause, resume, and snapshot subcommands.
/fire-6-resumeResumes project from most recent handoff file with full context restoration, displays status summary, checks incomplete work, and routes to next action. Supports --handoff, --list, --diff flags.
/resumeResumes a paused orchestrator session: checks/removes .claude/orchestrator/.pause flag, updates history state, displays pause duration/progress/status, then triggers /orchestrator:continue. Informs if not paused.
/resumeResumes an interrupted HOTL workflow run by invoking the hotl:resuming skill and following its instructions exactly.
Share bugs, ideas, or general feedback.
Continue a generation that was interrupted or failed.
/steering-resume
The system automatically saves checkpoints:
.claude/memory/orchestration/
├── current_session.json # Current execution state
├── checkpoint_group1.json # After Group 1 completes
├── checkpoint_group2.json # After Group 2 completes
└── checkpoint_group3.json # After Group 3 completes
# Check for checkpoint
if [ -f ".claude/memory/orchestration/current_session.json" ]; then
PHASE=$(jq -r '.phase' .claude/memory/orchestration/current_session.json)
STATUS=$(jq -r '.status' .claude/memory/orchestration/current_session.json)
if [ "$STATUS" == "running" ] || [ "$STATUS" == "failed" ]; then
echo "Found interrupted session at phase: $PHASE"
echo "Resuming from checkpoint..."
# Resume from last completed phase
case $PHASE in
"group1")
# Restart Group 1 or skip if completed
;;
"group2")
# Skip Group 1, resume Group 2
;;
"group3")
# Skip Groups 1 & 2, resume Group 3
;;
"synthesis")
# Run final synthesis only
;;
esac
fi
fi
🔄 Checking for interrupted session...
Found Session: gen_20251102_120000
Status: interrupted
Phase: group2 (60% complete)
Last Activity: 2025-11-02 12:45:00
Agents Completed:
✓ structure-analyst (Group 1)
✓ integration-mapper (Group 1)
✓ ui-specialist (Group 1)
✓ domain-expert (Group 2)
⏳ pattern-detective (Group 2) - INTERRUPTED
Resuming from Group 2...
────────────────────────────────────────
Phase 2/3: Deep Analysis (Resumed)
✓ domain-expert: Already complete
⏳ pattern-detective: Resuming analysis...
⏳ test-strategist: Starting fresh...
⏳ database-analyst: Starting fresh...
[Continue with normal execution...]
If automatic resume fails:
# Check what's completed
ls .claude/memory/*/
# Manually continue with remaining agents
# Use Task tool to invoke specific agents that didn't complete
To start fresh (discard interrupted session):
# Remove checkpoint
rm .claude/memory/orchestration/current_session.json
# Run full generation
/steering-generate
The session completed or never started. Run /steering-generate.
Clear state and start fresh:
rm .claude/memory/orchestration/*.json
/steering-setup
/steering-generate
Recover from interruptions: Run /steering-resume