ACE MCP Server

--- description: Basic task tracking for Level 2 Simple Enhancement tasks globs: "**/level2/**", "**/tracking/**", "**/task/**" alwaysApply: false --- # BASIC TASK TRACKING FOR LEVEL 2 > **TL;DR:** This document outlines a streamlined task tracking approach for Level 2 (Simple Enhancement) tasks. It provides a balanced framework for managing task progress with minimal overhead. ## 🔍 TASK TRACKING OVERVIEW Level 2 tasks require a more structured tracking approach than Level 1, but don't need the comprehensive tracking of higher-level tasks. This basic tracking system provides sufficient structure while maintaining efficiency. ## 📋 TASK TRACKING PRINCIPLES 1. **Clarity**: Tasks should be clearly defined 2. **Visibility**: Progress should be visible at a glance 3. **Structure**: Break work into logical subtasks 4. **Updates**: Keep progress regularly updated 5. **Completion**: Clearly mark when tasks are done ## 📋 TASK STRUCTURE FOR LEVEL 2 ```markdown ## [Feature Name] Enhancement **Status**: [Not Started/In Progress/Complete] **Priority**: [High/Medium/Low] **Estimated Effort**: [Small/Medium/Large] ### Description [Brief description of the enhancement] ### Requirements - [Requirement 1] - [Requirement 2] - [Requirement 3] ### Subtasks - [ ] [Subtask 1] - [ ] [Subtask 2] - [ ] [Subtask 3] ### Dependencies - [Dependency 1] - [Dependency 2] ### Notes [Any additional information or context] ``` ## 📋 TASKS.MD ORGANIZATION Organize tasks.md with these sections for Level 2 tasks: ```markdown # Tasks ## Active Enhancements - [Enhancement 1] - [Status] - [Enhancement 2] - [Status] ## Enhancement Details ### [Enhancement 1] [Task structure as above] ### [Enhancement 2] [Task structure as above] ## Completed Enhancements - [X] [Completed Enhancement 1] (YYYY-MM-DD) - [X] [Completed Enhancement 2] (YYYY-MM-DD) ``` ## 📋 UPDATING TASK STATUS Update tasks using this process: 1. **Starting a Task**: - Update Status to "In Progress" - Add start date to Notes 2. **Progress Updates**: - Check off subtasks as completed - Add brief notes about progress - Update any changed requirements 3. **Completing a Task**: - Update Status to "Complete" - Check off all subtasks - Move to Completed Enhancements - Add completion date ## 📋 SUBTASK MANAGEMENT For Level 2 tasks, subtasks should: 1. Be actionable and specific 2. Represent approximately 30-60 minutes of work 3. Follow a logical sequence 4. Be updated as soon as completed 5. Include verification steps Example of well-structured subtasks: ```markdown ### Subtasks - [ ] Review existing implementation of related features - [ ] Create draft UI design for new button - [ ] Add HTML structure for new component - [ ] Implement button functionality in JavaScript - [ ] Add appropriate styling in CSS - [ ] Add event handling - [ ] Test on desktop browsers - [ ] Test on mobile browsers - [ ] Update user documentation ``` ## 📋 PROGRESS VISUALIZATION Use progress indicators to show status: ```markdown ### Progress [###-------] 30% Complete ``` For subtasks: ```markdown ### Subtasks (3/10 Complete) - [X] Subtask 1 - [X] Subtask 2 - [X] Subtask 3 - [ ] Subtask 4 - [ ] Subtask 5 ``` ## 📋 TRACKING VERIFICATION CHECKLIST ``` ✓ TASK TRACKING VERIFICATION - Task clearly defined? [YES/NO] - Requirements listed? [YES/NO] - Subtasks created? [YES/NO] - Dependencies identified? [YES/NO] - Status up-to-date? [YES/NO] → If all YES: Task tracking is adequate → If any NO: Update task tracking ``` ## 📋 MINIMAL MODE TRACKING For minimal mode, use this format: ``` ✓ TASK: [Enhancement name] ✓ STATUS: [In Progress/Complete] ✓ SUBTASKS: [X/Y Complete] ✓ NEXT: [Next action] ``` ## 🔄 INTEGRATION WITH MEMORY BANK Task tracking integrates with Memory Bank: ```mermaid graph TD TasksFile["tasks.md"] --> Active["activeContext.md"] TasksFile --> Progress["progress.md"] Active -->|"Current focus"| TasksFile Progress -->|"Completion status"| TasksFile ``` ## 🚨 TASKS.MD PRIMACY PRINCIPLE Remember: ``` ┌─────────────────────────────────────────────────────┐ │ tasks.md is the SINGLE SOURCE OF TRUTH for ALL │ │ task tracking. ALL task updates MUST be reflected │ │ in tasks.md IMMEDIATELY. │ └─────────────────────────────────────────────────────┘ ``` This ensures everyone has visibility into current task status at all times.