workflow

/workflow Command

Workflow control using native Claude Code tasks. No persistent state files.

Subcommands

Command	Action
/workflow	Show current task and phase (status)
/workflow next	Advance to next phase or sub-task
/workflow skip	Skip current phase or sub-task
/workflow done	Mark task complete (with confirmation)
/workflow switch	Switch between multiple active tasks
/workflow expand	Create sub-tasks from phase items

Execution

1. Find Current Task

CALL TaskList tool to find tasks with [claude-evolve] prefix.

If multiple found:

• List them with index numbers
• Let user pick: "[claude-evolve] Multiple workflows found. Which one? (1-N)"
• Or suggest /workflow switch for explicit switching

If none found:

• Show fallback message (see below)

If one found:

• Use that task as current workflow

2. Show Status (default /workflow)

CALL TaskGet(id) to get full task details.

Read metadata to determine state:

• metadata.depth - determines which phase sequence to use
• metadata.phase - identifies current phase
• metadata.phases_done - comma-separated list of completed phases
• metadata.phases_skipped - comma-separated list of skipped phases

Display format:

[claude-evolve] Workflow: {subject}

Phase: {current} | Progress: {visual progress bar}

{Phase-specific guidance based on current phase}

Commands: next | skip | done

Visual progress example for design depth:

Progress: requirements [OK] -> design [OK] -> implement <- testing

The <- indicates current phase.

3. Phase Transitions (/workflow next)

Advance to the next phase based on depth:

For design depth: requirements -> design -> implement -> testing -> done For explore depth: research -> prototype -> evaluate -> decide -> done For plan depth: action -> outcome -> done

Check for phase tasks with blockedBy:

1. CALL TaskList to find [claude-evolve] Phase N: tasks
2. If phase tasks exist with blockedBy, mark current phase task completed
3. The next phase task automatically becomes available (no longer blocked)