From 95ad73a88adcc7a939ef81a28528787950635ad4 Mon Sep 17 00:00:00 2001 From: Daniel Scott-Raynsford Date: Sat, 9 Aug 2025 09:20:11 +1200 Subject: [PATCH] CHANGE: update tools list and enhance implementation plan - Reordered tools in the implementation plan for clarity. - Added structured implementation phases with task tables. - Revised goal description for better understanding. --- chatmodes/implementation-plan.chatmode.md | 31 +++++++++++++++-------- 1 file changed, 21 insertions(+), 10 deletions(-) diff --git a/chatmodes/implementation-plan.chatmode.md b/chatmodes/implementation-plan.chatmode.md index fd7d942..7741b39 100644 --- a/chatmodes/implementation-plan.chatmode.md +++ b/chatmodes/implementation-plan.chatmode.md @@ -1,6 +1,6 @@ --- description: 'Generate an implementation plan for new features or refactoring existing code.' -tools: ['changes', 'codebase', 'editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'github'] +tools: ['codebase', 'usages', 'vscodeAPI', 'think', 'problems', 'changes', 'testFailure', 'terminalSelection', 'terminalLastCommand', 'openSimpleBrowser', 'fetch', 'findTestFiles', 'searchResults', 'githubRepo', 'extensions', 'editFiles', 'runNotebooks', 'search', 'new', 'runCommands', 'runTasks'] --- # Implementation Plan Generation Mode @@ -63,25 +63,18 @@ All implementation plans must strictly adhere to the following template. Each se - Tables must include all required columns with specific task details - No placeholder text may remain in the final output -## Status - -The status of the implementation plan must be clearly defined in the front matter and must reflect the current state of the plan. The status can be one of the following (status_color in brackets): `Completed` (bright green badge), `In progress` (yellow badge), `Planned` (blue badge), `Deprecated` (red badge), or `On Hold` (orange badge). It should also be displayed as a badge in the introduction section. - ```md --- -goal: [Concise Title Describing the Package Plan's Goal] +goal: [Concise Title Describing the Package Implementation Plan's Goal] version: [Optional: e.g., 1.0, Date] date_created: [YYYY-MM-DD] last_updated: [Optional: YYYY-MM-DD] owner: [Optional: Team/Individual responsible for this spec] -status: 'Completed'|'In progress'|'Planned'|'Deprecated'|'On Hold' tags: [Optional: List of relevant tags or categories, e.g., `feature`, `upgrade`, `chore`, `architecture`, `migration`, `bug` etc] --- # Introduction -![Status: ](https://img.shields.io/badge/status--) - [A short concise introduction to the plan and the goal it is intended to achieve.] ## 1. Requirements & Constraints @@ -97,7 +90,25 @@ tags: [Optional: List of relevant tags or categories, e.g., `feature`, `upgrade` ## 2. Implementation Steps -[Describe the steps/tasks required to achieve the goal.] +### Implementation Phase 1 + +- GOAL-001: [Describe the goal of this phase, e.g., "Implement feature X", "Refactor module Y", etc.] + +| Task | Description | Completed | Date | +|------|-------------|-----------|------| +| TASK-001 | Description of task 1 | ✅ | 2025-04-25 | +| TASK-002 | Description of task 2 | | | +| TASK-003 | Description of task 3 | | | + +### Implementation Phase 2 + +- GOAL-002: [Describe the goal of this phase, e.g., "Implement feature X", "Refactor module Y", etc.] + +| Task | Description | Completed | Date | +|------|-------------|-----------|------| +| TASK-004 | Description of task 4 | | | +| TASK-005 | Description of task 5 | | | +| TASK-006 | Description of task 6 | | | ## 3. Alternatives