create-plan

Create Plan Document

Create an implementation plan document based on a spec.

Purpose

Three core functions:

1. Implementation steps: Organize How into sequential steps
2. Change locations: Identify which files to modify
3. Progress tracking: Track completion of steps during implementation

Detail Level

Plan should contain steps and files only:

• What to do (step description)
• Which files to change

Why this level?

• Focus on direction: AI is capable enough that if it knows what to do, it can handle implementation. Plan should focus on direction and goal.
• Flexibility: Too much detail makes the plan brittle/fragile - implementation often evolves differently
• Review cost: More detail means more to review (same problem as create-spec)

Exception: For repetitive tasks, few-shot examples can be included to guide implementation style.

Plan should NOT contain:

• Specific code changes
• Function/class level details
• Implementation code snippets

Input

This skill is invoked after create-spec completes. The spec document at .claude/dev-workflow/story/{name}/spec.md is the input.

Process

1. Read Spec

Load the spec document and understand:

• Why: Background and motivation
• What: Requirements and acceptance criteria
• Out of Scope: What NOT to do

2. Investigate Codebase

Gather information needed for implementation:

• Existing code structure
• Files that need changes
• Existing patterns to follow

3. Design Implementation Steps

Create steps following these principles:

• Dependency-aware: Start with prerequisites
• One deliverable per step: Each step produces a clear result
• Verifiable: Completion can be confirmed

4. Create Plan Document

Create .claude/dev-workflow/story/{name}/plan.md:

# Plan: {title}

## Related Files

- **Workflow concepts**: `dev-workflow/docs/workflow-concepts.md`
- **Spec**: `.claude/dev-workflow/story/{name}/spec.md`
- **Branch**: `{prefix}/{story-name}` (from spec)
- **Epic**: `.claude/dev-workflow/epic/{parent}/epic.md` (if part of an Epic)

## Workflow Context

**Current phase**: Implementation
**Work level**: Story

### During Implementation
- Follow Steps sequentially
- Update `## Progress` section as each step completes (`- [ ]` → `- [x]`)
- Refer to Spec's Acceptance Criteria as the source of truth for verification

### After All Steps Complete
1. Invoke `dev-workflow:self-review` skill — verifies against acceptance criteria in spec
2. Invoke `dev-workflow:user-review` skill — presents results and collects user feedback
3. After user LGTM: commit changes
4. Invoke `dev-workflow:post-task` skill — capture knowledge

### If Session Clears
- Use `/resume-work` to evaluate progress and resume from the correct point
- Or read this plan and the spec, then continue from the last completed step

## Approach
{High-level implementation approach}

## Files to Change

| File | Change |
|------|--------|
| `path/to/file` | {brief description} |

## Steps

### Step 1: {name}
{What to do}

### Step 2: {name}
{What to do}

## Progress

- [ ] Step 1
- [ ] Step 2

## Notes
{Decisions made during planning, if any}

5. User Review

Present plan to user for approval before proceeding.

Success Criteria

• Plan document is created at .claude/dev-workflow/story/{name}/plan.md
• Spec is referenced
• Files to change are listed
• Steps are in dependency order
• Progress checklist exists
• Implementation can start by reading plan alone (/clear and go)
• Workflow Context section includes current phase, post-implementation workflow sequence, and session recovery instructions
• User has approved the plan

Next Session

After plan is approved:

Reference:

• .claude/dev-workflow/story/{name}/spec.md
• .claude/dev-workflow/story/{name}/plan.md

Next phase: Implementation

Read both spec and plan, then proceed with implementation. Update Progress section as steps complete.