Bd 3 Plan

Required Workflow

1. Read the ticket and research files fully.
2. Confirm current-state constraints against code when needed.
3. Produce a phased plan with clear success criteria per phase.
4. Write or recommend the default plan path:
   • docs/plans/[slug].md

Delegation Guidance

• Stay local by default.
• Use Codex explorer agents only for narrow evidence gaps that do not justify broad replanning.

Plan Shape

# [Feature/Task Name] Implementation Plan

## Overview

## Current State Analysis

## Desired End State

## What We Are Not Doing

## Implementation Approach

## Phase 1: [Name]
### Changes Required

### Success Criteria
#### Automated Verification
#### Manual Verification

## Phase 2: [Name]

## Testing Strategy

## Rollback/Mitigation Notes

Completion Guidance

After the plan is created, the next Codex invocation should be:

use bd-4-execute with [plan path]

Notes

• The plan should be decision-complete enough that the implementer does not need to invent missing behavior.