executing-plans

Executing Plans

Overview

Load plan, review critically, execute tasks in batches, report for review between batches.

Core principle: Batch execution with checkpoints for architect review.

Announce at start: "I'm using the executing-plans skill to implement this plan."

The Process

Step 0: Verify Worktree

Before touching any code, verify you are NOT on main/master:

git branch --show-current

If on main/master or no worktree exists:

• REQUIRED SUB-SKILL: Use fulcrum:using-git-worktrees to create an isolated workspace
• Do not proceed until in a feature branch worktree

If already in a feature branch: Continue to Step 1.

Step 1: Load and Review Plan

1. Read plan file
2. Review critically - identify any questions or concerns about the plan
3. If concerns: Raise them with your human partner before starting
4. If no concerns: Create TodoWrite and proceed

Step 2: Execute Batch

Default: First 3 tasks

Record stage entry: Append to .claude/workflow-state.jsonl: {"stage":"implement","action":"entered","timestamp":"<ISO8601>"}

For each task:

1. Mark as in_progress
2. Follow each step exactly (plan has bite-sized steps)
3. Run verifications as specified
4. Mark as completed

Step 3: Report

When batch complete:

• Show what was implemented
• Show verification output
• Say: "Ready for feedback."

Step 4: Continue

Based on feedback:

• Apply changes if needed
• Execute next batch
• Repeat until complete

Step 5: Complete Development

Record stage completion: Append to .claude/workflow-state.jsonl: {"stage":"implement","action":"completed","timestamp":"<ISO8601>"}

After all tasks complete and verified:

• Announce: "I'm using the finishing-a-development-branch skill to complete this work."
• REQUIRED SUB-SKILL: Use fulcrum: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 mid-batch (missing dependency, test fails, instruction unclear)
• Plan 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 the plan based on your feedback
• Fundamental approach needs rethinking

Don't force through blockers - stop and ask.

Remember

• Review plan critically first
• Follow plan steps exactly
• Don't skip verifications
• Reference skills when plan says to
• Between batches: just report and wait
• Stop when blocked, don't guess
• Never start implementation on main/master branch without explicit user consent

Integration

Required workflow skills:

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