Files
Claude-Code-Workflow/.claude/commands/workflow/resume.md
catlog22 920b179440 docs: 更新所有命令描述并重新生成索引文件
- 更新所有69个命令文件的description字段,基于实际功能重新生成详细描述
- 重新生成5个索引文件(all-commands, by-category, by-use-case, essential-commands, command-relationships)
- 移动analyze_commands.py到scripts/目录并完善功能
- 移除临时备份文件

命令描述改进示例:
- workflow:plan: 增加了工具和代理的详细说明(Gemini, action-planning-agent)
- cli:execute: 说明了YOLO权限和多种执行模式
- memory:update-related: 详细说明了批处理策略和工具回退链

索引文件改进:
- usage_scenario从2种扩展到10种(更精细分类)
- command-relationships覆盖所有69个命令
- 区分built-in(内置调用)和sequential(用户顺序执行)关系

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-06 15:11:31 +08:00

3.8 KiB

name, description, argument-hint, allowed-tools
name description argument-hint allowed-tools
resume Resume paused workflow session with automatic progress analysis, pending task identification, and conflict detection session-id for workflow session to resume SlashCommand(*), TodoWrite(*), Read(*), Bash(*)

Sequential Workflow Resume Command

Usage

/workflow:resume "<session-id>"

Purpose

Sequential command coordination for workflow resumption by first analyzing current session status, then continuing execution with special resume context. This command orchestrates intelligent session resumption through two-step process.

Command Coordination Workflow

Phase 1: Status Analysis

  1. Call status command: Execute /workflow:status to analyze current session state
  2. Verify session information: Check session ID, progress, and current task status
  3. Identify resume point: Determine where workflow was interrupted

Phase 2: Resume Execution

  1. Call execute with resume flag: Execute /workflow:execute --resume-session="{session-id}"
  2. Pass session context: Provide analyzed session information to execute command
  3. Direct agent execution: Skip discovery phase, directly enter TodoWrite and agent execution

Implementation Protocol

Sequential Command Execution

# Phase 1: Analyze current session status
SlashCommand(command="/workflow:status")

# Phase 2: Resume execution with special flag
SlashCommand(command="/workflow:execute --resume-session=\"{session-id}\"")

Progress Tracking

TodoWrite({
  todos: [
    {
      content: "Analyze current session status and progress",
      status: "in_progress",
      activeForm: "Analyzing session status"
    },
    {
      content: "Resume workflow execution with session context",
      status: "pending",
      activeForm: "Resuming workflow execution"
    }
  ]
});

Resume Information Flow

Status Analysis Results

The /workflow:status command provides:

  • Session ID: Current active session identifier
  • Current Progress: Completed, in-progress, and pending tasks
  • Interruption Point: Last executed task and next pending task
  • Session State: Overall workflow status

Execute Command Context

The special --resume-session flag tells /workflow:execute:

  • Skip Discovery: Don't search for sessions, use provided session ID
  • Direct Execution: Go straight to TodoWrite generation and agent launching
  • Context Restoration: Use existing session state and summaries
  • Resume Point: Continue from identified interruption point

Error Handling

Session Validation Failures

  • Session not found: Report missing session, suggest available sessions
  • Session inactive: Recommend activating session first
  • Status command fails: Retry once, then report analysis failure

Execute Resumption Failures

  • No pending tasks: Report workflow completion status
  • Execute command fails: Report resumption failure, suggest manual intervention

Success Criteria

  1. Status analysis complete: Session state properly analyzed and reported
  2. Execute command launched: Resume execution started with proper context
  3. Agent coordination: TodoWrite and agent execution initiated successfully
  4. Context preservation: Session state and progress properly maintained

Prerequisite Commands:

  • /workflow:plan or /workflow:execute - Workflow must be in progress or paused

Called by This Command (2 phases):

  • /workflow:status - Phase 1: Analyze current session status and identify resume point
  • /workflow:execute - Phase 2: Resume execution with --resume-session flag

Follow-up Commands:

  • None - Workflow continues automatically via /workflow:execute

Sequential command coordination for workflow session resumption