mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-11 02:33:51 +08:00
新增 Mode 6: 深度命令分析 - 创建 reference 备份目录(80个文档:11 agents + 69 commands) - 支持简单查询(直接文件查找)和复杂查询(CLI 辅助分析) - 集成 gemini/qwen 进行跨命令对比、最佳实践、工作流分析 - 添加查询复杂度自动分类和降级策略 更新文档 - SKILL.md: 添加 Mode 6 说明和 Reference Documentation 章节 - implementation-details.md: 添加完整的 Mode 6 实现逻辑 - 版本更新至 v1.3.0 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
3.8 KiB
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
- Call status command: Execute
/workflow:statusto analyze current session state - Verify session information: Check session ID, progress, and current task status
- Identify resume point: Determine where workflow was interrupted
Phase 2: Resume Execution
- Call execute with resume flag: Execute
/workflow:execute --resume-session="{session-id}" - Pass session context: Provide analyzed session information to execute command
- 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
- Status analysis complete: Session state properly analyzed and reported
- Execute command launched: Resume execution started with proper context
- Agent coordination: TodoWrite and agent execution initiated successfully
- Context preservation: Session state and progress properly maintained
Related Commands
Prerequisite Commands:
/workflow:planor/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-sessionflag
Follow-up Commands:
- None - Workflow continues automatically via
/workflow:execute
Sequential command coordination for workflow session resumption