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
• Start epic <epic-id> (handoff from planning session)

Workflow

Phase 0: Handoff Detection

If user message matches Start epic <epic-id>:

1. Load epic from beads:

   bd show <epic-id> --json
   

2. Parse notes for plan location: Look for PLAN: <path> in notes field

3. Read the plan:

   cat <plan-path>
   

4. Get ready tasks:

   bd ready --json
   

   Filter to tasks that are children of this epic

5. Begin execution at Phase 1 with epic context loaded

If no handoff detected: Proceed directly to Phase 1.

Phase 1: Find Available Work

bd ready --json

If no tasks available:

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

Phase 2: Claim Task

1. Select highest priority ready task

2. Mark as in-progress:

   bd update <issue-id> --status in_progress
   

3. CRITICAL: Record thread URL for doc-sync integration

   ⚠️ This step is REQUIRED - doc-sync relies on thread URLs to extract knowledge.

   Before proceeding, verify:

   • You have the current Amp thread URL (check Environment section or $AMP_THREAD_URL)
   • The URL is valid (format: https://ampcode.com/threads/T-... or http://localhost:.../threads/T-...)

   bd update <issue-id> --notes "THREAD: <current-amp-thread-url>"
   

   If thread URL is unavailable: STOP and notify user. Do not proceed without recording the thread link - this creates orphaned work that cannot be synced to documentation.

4. 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

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

Phase 5: Verify Before Claiming Done

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

Phase 6: Update Beads

bd update <issue-id> --notes "COMPLETED: <summary>. THREAD: <amp-thread-url>. 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>