Executing Plans

Step 2: Execute Tasks

For each task:

1. Claim the task:

   bd update <task-id> --claim
   

2. Read the task's design field for step-by-step instructions:

   bd show <task-id>
   

3. Follow each step exactly (tasks have bite-sized steps)
4. Run verifications as specified
5. Close the task:

   bd close <task-id> --reason "<what was done>"
   

Step 3: Complete Development

After all tasks complete and verified:

• Announce: "I'm using the finishing-a-development-branch skill to complete this work."
• REQUIRED SUB-SKILL: Use finishing-a-development-branch
• Follow that skill to verify tests, present options, execute choice

When to Stop and Ask for Help

STOP executing immediately when:

• Hit a blocker (missing dependency, test fails, instruction unclear)
• Task has critical gaps preventing starting
• You don't understand an instruction
• Verification fails repeatedly

Ask for clarification rather than guessing.

When to Revisit Earlier Steps

Return to Review (Step 1) when:

• Partner updates tasks based on your feedback
• Fundamental approach needs rethinking

Don't force through blockers - stop and ask.

Remember

• Review tasks critically first
• Follow task design steps exactly
• Don't skip verifications
• Reference skills when task says to
• Stop when blocked, don't guess
• Never start implementation on main/master branch without explicit user consent

Integration

Required workflow skills:

• using-git-worktrees - REQUIRED: Set up isolated workspace before starting
• writing-plans - Creates the bd task hierarchy this skill executes
• finishing-a-development-branch - Complete development after all tasks