create-plan

Create Implementation Plan

Use this rule to generate detailed implementation plans for TODOs, breaking down complex tasks into ordered, actionable steps.

Important Note

Before generate any implementation plan and checklist, follow the steps in the prepare rule to thoroughly research and understand the codebase context. This ensures your implementation aligns with existing patterns and standard of the codebase.

When to use

• When planning the implementation of a TODO item from a list
• When breaking down a complex feature into manageable steps
• When you need a step-by-step checklist approach to solving a problem

Instructions

The following instructions will help you create an implementation plat for a TODO item. Create the folder if it doesn't already exist .cursor/memory to store implementation plants, then follow the following steps and instructions:

1. First, thoroughly analyze the TODO description to understand:

   • The main goal/purpose of the feature
   • The specific technical requirements
   • Any risks or edge cases mentioned
   • Platform-specific considerations

2. Create a markdown file in the .cursor/memory/{todo-name}-checklist.md format using the edit_file tool:

   # EXAMPLE COMMAND: Replace {todo-name} with the specific TODO identifier
   edit_file(
     target_file: ".cursor/memory/{todo-name}-checklist.md",
     instructions: "Creating implementation plan checklist file for TODO X",
     code_edit: "---\ncreatedOn: \"2023-06-15T14:30:00-07:00\"\nupdatedOn: \"2023-06-15T14:30:00-07:00\"\n---\n\n# TODO X: [Feature Name] Implementation Checklist\n\n## Background\n..."
   )
   

3. Always include a YAML frontmatter at the top of the file with the following fields:

   • createdOn: The ISO date time string (with timezone) when the file was first created
   • updatedOn: Initially the same as createdOn, but must be updated by the implementor whenever they make changes
   • Example:

     ---
     createdOn: "2023-06-15T14:30:00-07:00"
     updatedOn: "2023-06-15T14:30:00-07:00"
     ---
     

   • The planner MUST use the current local date time with timezone information when creating the file
   • The implementor MUST update the updatedOn value whenever they modify the file or mark checklist items as complete
   • Here are examples of valid ISO date time strings with timezone information:
     • "2023-06-15T14:30:00-07:00" (Pacific Daylight Time)
     • "2023-06-15T16:30:00-05:00" (Central Daylight Time)
     • "2023-06-15T22:30:00+01:00" (British Summer Time)
     • "2023-06-16T06:30:00+09:00" (Japan Standard Time)