custom_github_copilot_agent_builder: Instructions file for GitHub Copilot

Task Plan Implementation Instructions

You will implement your specific task plan located in .copilot-tracking/plans/** and .copilot-tracking/details/**. Your goal is to progressively and completely implement each step in the plan files to create high-quality, working software that meets all specified requirements.

Implementation progress MUST be tracked in a corresponding changes files located in .copilot-tracking/changes/**.

Core Implementation Process

1. Plan Analysis and Preparation

MUST complete before starting implementation:

• MANDATORY: Read and fully understand the complete plan file including scope, objectives, all phases, and every checklist item
• MANDATORY: Read and fully understand the corresponding changes file completely - if any parts are missing from context, read the entire file back in using read_file
• MANDATORY: Identify all referenced files mentioned in the plan and examine them for context
• MANDATORY: Understand current project structure and conventions

2. Systematic Implementation Process

Implement each task in the plan systematically:

1. Process tasks in order - Follow the plan sequence exactly, one task at a time

2. MANDATORY before implementing any task:

   • ALWAYS ensure implementation is associated with a specific task from the plan
   • ALWAYS read the entire details section for that task from the associated details markdown file in .copilot-tracking/details/**
   • FULLY understand all implementation details before proceeding
   • Gather any additional required context as needed

3. Implement the task completely with working code:

   • Follow existing code patterns and conventions from the workspace
   • Create working functionality that meets all task requirements specified in the details
   • Include proper error handling, documentation, and follow best practices

4. Mark task complete and update changes tracking:

   • Update plan file: change [ ] to [x] for completed task
   • MANDATORY after completing EVERY task: Update the changes file by appending to the appropriate Added, Modified, or Removed sections with relative file paths and one-sentence summary of what was implemented
   • MANDATORY: If any changes diverge from the task plan and details, specifically call out within the relevant section that the change was made outside of the plan and include the specific reason
   • If ALL tasks in a phase are complete [x], mark the phase header as complete [x]