plan/execplan claude code commands

execplan.md

Execute Plan Command

Overview

Execute a numerically-prefixed plan file from the plans folder based on the provided argument.

Instructions

Plan Selection

• Read the plan file with prefix matching $ARGUMENTS from the plans folder
• Ensure you understand the complete scope before beginning execution

Execution Guidelines

1. Progress Tracking: Update the plan document with your progress as you work
2. Commit Strategy:
   • Commit after each meaningful feature or fix is complete and working
   • Each commit should represent a single logical unit of work
   • Avoid bundling multiple unrelated changes in one commit
   • Never commit broken or failing code (unless intentionally adding failing tests before implementation)
   • Avoid mentioning Claude in commit messages
3. Testing Approach:
   • Focus on light-touch unit and integration testing initially
   • Prioritize having passing tests over exhaustive coverage
   • Ensure basic functionality works before expanding test coverage

Work Flow

• Read and understand the full plan first
• Break work into logical, committable chunks
• Update plan document with progress markers
• Test each piece as you complete it
• Commit working code with clear, descriptive messages

plan.md

Create Implementation Plan

Overview

Create a structured implementation plan document in the plans folder with auto-incremented numerical prefix.

Plan Creation Process

File Management

1. Location: Save to plans/ folder
2. Naming: Use auto-incremented prefix (001, 002, etc.) - find next available number
3. Format: Standard markdown file (.md extension)

Plan Structure Requirements

Document Format

• Start with high-level summary of the feature/change

• Break down into implementable steps suitable for developer handoff

• Use hierarchical technical numbering:

  1. Main Section
  1.1 Subsection
  1.2 Another Subsection
  1.2.1 Sub-subsection
  2. Next Main Section
  

Content Organization

1. Executive Summary: Brief overview of what's being built/changed
2. Technical Approach: High-level architectural decisions
3. Implementation Steps: Detailed breakdown of work
4. Testing Strategy: How to verify the implementation
5. Acceptance Criteria: Definition of done

Input Processing

1. Parse Requirements: Extract key functionality, constraints, and goals from the multi-paragraph input
2. Identify Scope: Determine what needs to be built, modified, or integrated
3. Structure Output: Transform the narrative requirements into the organized plan format above
4. Add Technical Detail: Supplement user requirements with necessary technical considerations
5. Create Actionable Steps: Break down abstract requirements into concrete implementation tasks

Raw Requirements

$ARGUMENTS