Implementation Planning

When to Use This Skill

Planning Mode triggers:

• Starting a new feature or user request
• Bug fixes requiring investigation
• Code refactoring or architecture changes
• Unexpected complexity discovered during execution

Implementation Mode triggers:

• Approved implementation plan exists
• User says "start implementation" or "begin work"
• Following up on a reviewed plan

Planning Mode: Detailed Workflow

Step 1: Context Gathering

Before writing any plan, gather comprehensive context using read-only operations:

Start with high-level overview:

1. Read project instructions in .github/instructions/ related to the task
2. Identify main components and modules involved
3. Search for similar existing patterns in the codebase

Progressive refinement:

1. Use broad searches before reading specific files
2. Trace dependencies and related functionality
3. Identify edge cases and constraints

Stopping criteria:

• Reach 80% confidence you understand the problem
• Can articulate root causes and proposed changes
• Understand testing and verification requirements

Tools for research:

• read_file - Read project documentation and source files
• file_search - Find relevant files by pattern or content
• grep - Search for specific code patterns
• list_directory - Understand project structure

Step 2: Create Implementation Instructions File

Create a structured markdown document that serves as the contract between planning and implementation phases.

File naming:

.github/implementations/implementation.instructions.md
.github/implementations/[module_name]_implementation.instructions.md

File location: Store all implementation plans in .github/implementations/ directory for consistency.

YAML Frontmatter Structure:

---