Execution Workflow

Use when: User says ct, claim task, or wants to claim and implement the next available task from beads.

Trigger Phrases

ct
claim task
claim next task
work on next issue

Workflow

Phase 1: Find Available Work

bd ready --json

If no tasks available:

Check for blocked tasks: bd blocked --json
Report status and ask user what to do next

Phase 2: Claim Task

Select highest priority ready task

Mark as in-progress:

bd update <issue-id> --status in_progress

Read task details:
```
bd show <issue-id>
```

Phase 3: Setup Isolation (Optional)

For complex tasks, create isolated worktree:

Load using-git-worktrees skill
Create worktree for the task

Phase 4: Implement with TDD

Load test-driven-development skill
Follow RED-GREEN-REFACTOR cycle:
- Write failing test first
- Implement minimum code to pass
- Refactor while green

Phase 5: Verify Before Claiming Done

Load verification-before-completion skill
Run all verification commands
Confirm tests pass, no lint errors

Phase 6: Update Beads

bd update <issue-id> --notes "COMPLETED: <summary>. Files changed: <list>"

Phase 7: Finish or Continue

Ask user:

Continue to next task? → Loop to Phase 1
Finish branch? → Load finishing-a-development-branch skill

Output Format

CLAIMING: <issue-id> - <title>
PRIORITY: <priority>
DEPENDENCIES: <resolved deps>

[Implementation steps...]

STATUS: Complete | In Progress | Blocked
NEXT: <recommendation>

Execution Workflow

Execution Workflow

Trigger Phrases

Workflow

Phase 1: Find Available Work

Phase 2: Claim Task

Phase 3: Setup Isolation (Optional)

Phase 4: Implement with TDD

Phase 5: Verify Before Claiming Done

Phase 6: Update Beads

Phase 7: Finish or Continue

Output Format

Related Skills