ACE MCP Server

--- description: Basic reflection format for Level 2 Simple Enhancement tasks globs: "**/level2/**", "**/reflection/**" alwaysApply: false --- # BASIC REFLECTION FOR LEVEL 2 TASKS > **TL;DR:** This document outlines a basic reflection approach for Level 2 (Simple Enhancement) tasks, ensuring that key insights and lessons are captured without unnecessary overhead. ## 🔍 REFLECTION OVERVIEW Reflection is essential for improving future work, even for simpler Level 2 enhancements. This basic reflection approach focuses on key outcomes, challenges, and lessons learned while maintaining efficiency. ## 📋 REFLECTION PRINCIPLES 1. **Honesty**: Accurately represent successes and challenges 2. **Specificity**: Include concrete examples and observations 3. **Insight**: Go beyond surface observations to derive useful insights 4. **Improvement**: Focus on actionable takeaways for future work 5. **Efficiency**: Keep reflection concise and focused on key learnings ## 📋 BASIC REFLECTION STRUCTURE ```markdown # Level 2 Enhancement Reflection: [Feature Name] ## Enhancement Summary [Brief one-paragraph summary of the enhancement] ## What Went Well - [Specific success point 1] - [Specific success point 2] - [Specific success point 3] ## Challenges Encountered - [Specific challenge 1] - [Specific challenge 2] - [Specific challenge 3] ## Solutions Applied - [Solution to challenge 1] - [Solution to challenge 2] - [Solution to challenge 3] ## Key Technical Insights - [Technical insight 1] - [Technical insight 2] - [Technical insight 3] ## Process Insights - [Process insight 1] - [Process insight 2] - [Process insight 3] ## Action Items for Future Work - [Specific action item 1] - [Specific action item 2] - [Specific action item 3] ## Time Estimation Accuracy - Estimated time: [X hours/days] - Actual time: [Y hours/days] - Variance: [Z%] - Reason for variance: [Brief explanation] ``` ## 📋 REFLECTION QUALITY High-quality reflections for Level 2 tasks should: 1. **Provide specific examples** rather than vague statements 2. **Identify concrete takeaways** not general observations 3. **Connect challenges to solutions** with clear reasoning 4. **Analyze estimation accuracy** to improve future planning 5. **Generate actionable improvements** for future work ## 📋 REFLECTION PROCESS Follow these steps for effective Level 2 task reflection: 1. **Schedule Reflection**: - Allocate dedicated time for reflection - Complete reflection within 24 hours of task completion 2. **Gather Information**: - Review the original task requirements - Examine implementation details - Consider challenges encountered - Review time tracking data 3. **Complete Template**: - Fill in all sections of the reflection template - Include specific, concrete examples - Be honest about challenges 4. **Extract Insights**: - Identify patterns in challenges - Connect challenges to potential future improvements - Consider process improvements 5. **Document Action Items**: - Create specific, actionable improvements - Link these to future tasks where applicable 6. **Store Reflection**: - Save reflection with the task archive - Add cross-references to relevant documents ## 📋 EXAMPLES: VAGUE VS. SPECIFIC ENTRIES ### ❌ Vague Entries (Insufficient) - "The implementation went well." - "We had some challenges with the code." - "The feature works as expected." ### ✅ Specific Entries (Sufficient) - "The modular approach allowed for easy integration with the existing codebase, specifically the clean separation between the UI layer and data processing logic." - "Challenge: The state management became complex when handling multiple user interactions. Solution: Implemented a more structured reducer pattern with clear actions and state transitions." - "Action Item: Create a reusable component for file selection that handles all the edge cases we encountered in this implementation." ## 📋 REFLECTION VERIFICATION CHECKLIST ``` ✓ REFLECTION VERIFICATION - All template sections completed? [YES/NO] - Specific examples provided? [YES/NO] - Challenges honestly addressed? [YES/NO] - Concrete solutions documented? [YES/NO] - Actionable insights generated? [YES/NO] - Time estimation analyzed? [YES/NO] → If all YES: Reflection complete → If any NO: Improve reflection quality ``` ## 📋 MINIMAL MODE REFLECTION For minimal mode, use this format: ``` ✓ REFLECTION: [Feature Name] ✓ WENT WELL: [Key success] ✓ CHALLENGE: [Key challenge] ✓ SOLUTION: [Key solution] ✓ INSIGHT: [Most important takeaway] ✓ ACTION: [Top priority action item] ✓ TIME: Est [X] vs. Actual [Y] ([Z%] variance) ``` ## 🔄 INTEGRATION WITH MEMORY BANK Reflection integrates with Memory Bank: ```mermaid graph TD Reflection["Enhancement<br>Reflection"] --> Archive["Add to<br>Archive"] Reflection --> ProgressUpdate["Update<br>progress.md"] Reflection --> ActionItems["Document<br>Action Items"] ActionItems --> Tasks["Add to<br>tasks.md"] Archive & ProgressUpdate & Tasks --> CrossLinks["Create<br>Cross-Links"] ``` ## 🚨 CONTINUOUS IMPROVEMENT PRINCIPLE Remember: ``` ┌─────────────────────────────────────────────────────┐ │ Every reflection should produce at least ONE │ │ actionable improvement for future work. │ └─────────────────────────────────────────────────────┘ ``` This ensures that reflection directly contributes to ongoing improvement of both the product and the process.