Skip to content

Latest commit

 

History

History
178 lines (141 loc) · 3.72 KB

claude-workflow.md

File metadata and controls

178 lines (141 loc) · 3.72 KB
title aliases tags created updated
Claude Development Workflow
Claude Process
Three-Phase Development
development
workflow
claude
process
2025-01-13
2025-01-27

Three-Phase Claude Development Workflow

Note

Streamlined development workflow combining analysis and planning into a single phase, followed by implementation and cleanup phases using Claude 3.5 Sonnet and Claude 3 Haiku.

Development Flow

graph TD
    A[Analysis & Planning - Sonnet] -->|Technical Spec| B[Implementation - Sonnet]
    B -->|Code Complete| C[Cleanup & Documentation - Haiku]
    C -->|Task Complete| A
Loading

Workflow Phases

1. Analysis & Planning (Sonnet)

Purpose: Select and plan next most valuable task Output: Combined Analysis & Technical Specification

[!tip] Use [[examples/analysis-planning-prompt|Analysis & Planning Prompt]]

Selection Criteria:

  1. Priority & blocking status
  2. Dependencies
  3. Technical complexity
  4. Value/effort ratio

Planning Focus:

  1. Technical design
  2. Interfaces
  3. Data flow
  4. Test strategy
  5. Migration steps

2. Implementation (Sonnet)

Purpose: Execute technical specification Output: Code Changes, Tests, Core Documentation

[!tip] Use [[examples/implementation-prompt|Implementation Prompt]]

Implementation Steps:

  1. Write tests
  2. Create/update interfaces
  3. Implement core changes
  4. Verify criteria
  5. Add essential docs

3. Cleanup & Documentation (Haiku)

Purpose: Clean up code and update documentation Output: Clean codebase, updated documentation, closed issues

[!tip] Use [[examples/cleanup-docs-prompt|Cleanup & Documentation Prompt]]

Cleanup Steps:

  1. Update project docs
  2. Clean up code
  3. Review/update tests
  4. Update issues
  5. Final commit

Phase Transitions

Analysis & Planning → Implementation

  1. Complete combined analysis & technical spec
  2. Verify interfaces defined
  3. Create implementation chat
  4. Hand off spec

Implementation → Cleanup

  1. Verify implementation
  2. Basic tests passing
  3. Create cleanup chat
  4. Hand off summary

Cleanup → Next Analysis

  1. Verify criteria met
  2. Close issues
  3. Create analysis chat
  4. Begin next task

Document Templates

Combined Analysis & Technical Specification

TASK ANALYSIS
GitHub Issue: #[number] [title]
Labels: [high-priority, bug, feature, etc]
Description: [1-2 sentences]
Priority: [High/Medium/Low] ([reasoning])
Current State: [1-2 sentences]

TECHNICAL DESIGN
Data Flow:
- [flow point 1]
- [flow point 2]

Core Changes:
1. [Change Area 1]
   - Location: [file]
   - Details: [specifics]
   
2. [Change Area 2]
   - Location: [file]
   - Details: [specifics]

INTERFACES
[Interface definitions]

IMPLEMENTATION STEPS
1. [ ] [First step]
2. [ ] [Second step]

Files to Modify:
- [path]: [changes]
Files to Create:
- [path]: [purpose]

TEST PLAN
1. Unit Tests:
   - [test scenario]
2. Integration Tests:
   - [test scenario]

MIGRATION PLAN
1. [Step 1]
2. [Step 2]

SUCCESS CRITERIA
- [ ] [criterion]
- [ ] [criterion]

TECHNICAL NOTES
- [technical detail]
- [technical detail]

FUTURE TASKS
- [ ] [future task]
- [ ] [future task]

Best Practices

Chat Management

  • One chat for analysis & planning
  • Clear transitions
  • Context in handoffs
  • Link GitHub issues

Documentation

  • Update during dev
  • Keep templates current
  • Document decisions
  • Note future tasks

Testing

  • Tests first
  • Cover edge cases
  • Verify criteria

GitHub Integration

  • Reference issues
  • Close completed
  • Create follow-ups
  • Update labels

Related Documents

  • [[examples/analysis-planning-prompt|Analysis & Planning]]
  • [[examples/implementation-prompt|Implementation]]
  • [[examples/cleanup-docs-prompt|Cleanup & Documentation]]
  • GitHub: https://github.com/jerseycheese/BootHillGM