task-plan-implementation

name	task-plan-implementation
description	Implement task plans systematically with progressive tracking and change records. Use when executing a plan file from /plan/ or .copilot-tracking/plans/. Enforces reading the full plan first, implementing tasks in order, marking tasks complete, and updating a change log after every task. Covers plan analysis, implementation quality standards, progress validation, and release summary generation.
argument-hint	[path to plan file, e.g. plan/feature-tag-editor-1.md]

Task Plan Implementation Instructions

Implement plan tasks systematically, track progress in change logs, validate each task, and maintain release-ready documentation.

Core Implementation Process

1. Plan Analysis and Preparation

MUST complete before starting implementation:

• Read and fully understand the complete plan file including scope, objectives, all phases, and every checklist item
• Read and fully understand the corresponding changes file completely
• Identify all referenced files mentioned in the plan and examine them for context
• 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:
   • Ensure implementation is associated with a specific task from the plan
   • Read the entire details section for that task from the associated details file
   • 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
   • Create working functionality that meets all task requirements
   • Include proper error handling, documentation, and best practices
4. Mark task complete and update changes tracking:
   • Update plan file: change [ ] to [x] for completed task
   • MANDATORY after EVERY task: Update the changes file with Added, Modified, or Removed entries
   • If any changes diverge from plan, call it out explicitly with the specific reason

3. Implementation Quality Standards

Every implementation MUST:

• Follow existing workspace patterns and conventions
• Implement complete, working functionality that meets all task requirements
• Include appropriate error handling and validation
• Use consistent naming conventions and code structure
• Add necessary documentation for complex logic
• Ensure compatibility with existing systems and dependencies

4. Continuous Progress and Validation

After implementing each task:

1. Validate changes against the task requirements
2. Fix any problems before moving to the next task
3. Mark completed tasks [x] in the plan file
4. Update the changes file with a summary of what was implemented
5. Continue to the next unchecked task

Continue until:

• All tasks in the plan are marked complete [x]
• All specified files have been created or updated with working code
• All success criteria from the plan have been verified

5. Completion Criteria

Implementation is complete when:

• ✅ All plan tasks are marked complete [x]
• ✅ All specified files contain working code
• ✅ Code follows workspace patterns and conventions
• ✅ All functionality works as expected
• ✅ Changes file is updated after every task completion
• ✅ Final release summary is appended only after ALL phases complete

Implementation Workflow

1. Read and fully understand plan file and all checklists
2. Read and fully understand changes file
3. For each unchecked task:
   a. Read details for that task
   b. Fully understand all implementation requirements
   c. Implement task with working code following workspace patterns
   d. Validate implementation meets task requirements
   e. Mark task complete [x] in plan file
   f. Update changes file with Added/Modified/Removed entries
   g. Note any divergences from plan with specific reasons
4. Repeat until all tasks complete
5. Only after ALL phases complete [x]: Add final Release Summary to changes file

Changes File Template

Save changes file in .copilot-tracking/changes/ as YYYYMMDD-task-description-changes.md:

<!-- markdownlint-disable-file -->
# Release Changes: [task name]

**Related Plan**: [plan-file-name]
**Implementation Date**: YYYY-MM-DD

## Summary
[Brief description of overall changes]

## Changes

### Added
- relative/file/path.py — one sentence summary

### Modified
- relative/file/path.py — one sentence summary

### Removed
- relative/file/path.py — reason

## Release Summary

**Total Files Affected**: N

### Files Created (N)
- file-path — purpose

### Files Modified (N)
- file-path — changes made