Implementation Plan Guide

A structured guide for creating comprehensive implementation plans before starting development work.

When to Use

• Planning new features or significant functionality additions
• Preparing for refactoring or architectural changes
• Documenting approach before starting complex implementation work
• Ensuring clear acceptance criteria and testing strategy

Instructions

Required Sections

1. Background and Context

Document the background and history that led to this implementation:

• Why: What problem or requirement does this address?
• Context: What is the current situation or issue?
• History: What events or changes led to this need?
• Related Issues: Any related issues, discussions, or previous attempts?

2. Acceptance Criteria

• Build and all tests must pass
• Unit tests and integration tests must be created for the implemented changes
• If project-specific verification rules exist (e.g., .cursor/rules/build-and-test-verification.mdc), follow them

3. Implementation Details

Document the planned approach:

• Approach: How will this be implemented?
• Changes: What files, components, or systems will be modified?
• Dependencies: Any dependencies or prerequisites?
• Testing Strategy: How will the changes be tested?

Language Requirement

All implementation plans must be written in English.