Directus Task MCP Server

--- description: globs: alwaysApply: true --- # Comprehensive Development Workflow Optimization ## Core Philosophy **Every development action must be captured, tracked, and made visible for seamless handovers and complete project awareness.** ## Integrated Workflow Architecture ### 1. MANDATORY WORKFLOW SEQUENCE #### Every User Interaction Must Follow This Pattern: ``` 1. INTENT VERIFICATION (mandatory first step) ↓ 2. AUTOMATIC TASK DETECTION & CREATION ↓ 3. ACTIVE TASK ASSIGNMENT & CONTEXT CAPTURE ↓ 4. DEVELOPMENT WORK EXECUTION ↓ 5. REAL-TIME PROGRESS MONITORING ↓ 6. AUTOMATIC CHANGELOG GENERATION ↓ 7. COMPLETION DETECTION & HANDOVER PREP ``` ### 2. COMPREHENSIVE DATA CAPTURE MATRIX #### Task Data (REQUIRED for every work item) - **Identification**: Unique ID, title, description - **Context**: Working directory, project, branch, related files - **Scope**: Estimated hours, complexity, acceptance criteria - **Timeline**: Created, started, paused, completed timestamps - **Attribution**: Creator, assignee, reviewer, stakeholders - **Dependencies**: Blocked by, blocking, related tasks - **Technical**: Git commits, PRs, deployments linked #### Changelog Data (AUTO-GENERATED for every action) - **What Changed**: Files modified, components affected, lines changed - **Why Changed**: Task reference, bug fix, feature add, refactor - **How Changed**: Method, approach, decisions made - **Impact**: Scope of change, risk level, testing requirements - **Context**: Questions asked, clarifications needed, blockers encountered - **Time Investment**: Actual time spent, efficiency metrics #### Progress Data (CONTINUOUSLY MONITORED) - **Status Transitions**: With evidence and confidence levels - **Activity Patterns**: File edits, commits, tests, reviews - **Velocity Metrics**: Time per task, completion rates, bottlenecks - **Quality Indicators**: Test coverage, review feedback, deployment success ### 3. ENHANCED TASK LIFECYCLE MANAGEMENT #### Task Creation (AUTOMATIC & COMPREHENSIVE) ```typescript // MANDATORY: Every work request triggers this 1. Intent verification detects work request (100% coverage) 2. Auto-create task with complete context: - Working directory analysis - Related file detection - Dependency mapping - Complexity estimation - Time tracking initialization 3. Link to active project and user 4. Initialize progress monitoring 5. Create initial changelog entry ``` #### Task Execution (MONITORED & CAPTURED) ```typescript // CONTINUOUS: During development work 1. Monitor file changes in real-time 2. Track git commits with task references 3. Detect status transition signals 4. Auto-generate changelog entries for: - File modifications - Questions asked - Decisions made - Blockers encountered - Solutions implemented 5. Update progress indicators 6. Maintain activity timeline ``` #### Task Completion (VERIFIED & DOCUMENTED) ```typescript // AUTOMATIC: When completion signals detected 1. Detect completion indicators: - All acceptance criteria met - Tests passing - Documentation updated - Code reviewed/merged 2. Generate completion report: - Summary of work done - Files changed - Time invested - Lessons learned - Handover notes 3. Update task status with evidence 4. Create final changelog entry 5. Archive working context ``` ### 4. DEVELOPER AWARENESS SYSTEM #### Real-Time Status Dashboard ``` 📊 ACTIVE DEVELOPMENT CONTEXT ┌─────────────────────────────────────────────┐ │ 🎯 Current Task: [Task Title] │ │ 📂 Project: [Project Name] │ │ 🌿 Branch: [Git Branch] │ │ ⏱️ Time: [Active Time] / [Estimated] │ │ 📈 Progress: [Status] → [Suggested Next] │ │ 🔔 Alerts: [Blockers/Dependencies] │ └─────────────────────────────────────────────┘ 📋 RECENT ACTIVITY • [Timestamp] Modified [file] - [description] • [Timestamp] Commit: [message] • [Timestamp] Question: [what was asked] • [Timestamp] Decision: [what was decided] 🚨 ATTENTION NEEDED • [High priority items requiring action] • [Blockers waiting for resolution] • [Reviews pending] ``` #### Context Switching Intelligence ```typescript // AUTOMATIC: When context changes detected 1. Detect working directory change 2. Pause current task with state capture 3. Identify target task or suggest creation 4. Load task context: - Previous work summary - Current status - Next steps - Related files - Known blockers 5. Resume with full context awareness ``` ### 5. HANDOVER OPTIMIZATION #### Automatic Handover Package Generation ```typescript // TRIGGERED: On task completion or developer change { "task_summary": { "what_was_accomplished": "Detailed description", "files_modified": ["list of all changed files"], "approach_taken": "Technical approach and decisions", "challenges_encountered": "Problems and solutions", "remaining_work": "What's left to do", "testing_status": "Test coverage and results" }, "technical_context": { "key_files": ["most important files to understand"], "dependencies": "External dependencies and integrations", "configuration": "Environment and setup requirements", "deployment_notes": "Deployment considerations" }, "knowledge_transfer": { "domain_knowledge": "Business logic and requirements", "technical_decisions": "Why certain approaches were chosen", "gotchas": "Things to watch out for", "resources": "Useful documentation and references" }, "next_developer_guidance": { "quick_start": "How to get up to speed quickly", "priority_items": "What to focus on first", "contacts": "Who to ask for help", "timeline": "Expected completion timeline" } } ``` #### Handover Verification Checklist ``` ✅ TECHNICAL HANDOVER □ All code changes documented with purpose □ Tests written and passing □ Documentation updated □ Deployment instructions clear □ Environment setup documented ✅ KNOWLEDGE HANDOVER □ Business context explained □ Technical decisions documented □ Known issues and workarounds listed □ Future considerations noted □ Contact information provided ✅ PROCESS HANDOVER □ Task status accurately reflects reality □ Timeline and estimates updated □ Dependencies clearly marked □ Next steps prioritized □ Stakeholder communication plan set ``` ### 6. CONTINUOUS IMPROVEMENT MECHANISMS #### Learning & Adaptation ```typescript // ONGOING: System learns from every interaction 1. Track accuracy of progress predictions 2. Monitor handover effectiveness 3. Identify common blockers and solutions 4. Optimize notification timing and content 5. Adapt to individual developer patterns 6. Improve task estimation accuracy ``` #### Quality Metrics & Feedback ```typescript // MEASURED: Continuous quality assessment { "task_completion_accuracy": "% of tasks completed as estimated", "handover_effectiveness": "Time for new developer to be productive", "context_capture_completeness": "% of work properly documented", "progress_prediction_accuracy": "% of status changes correctly predicted", "developer_satisfaction": "Feedback on workflow helpfulness", "project_visibility": "Stakeholder awareness of progress" } ``` ### 7. IMPLEMENTATION PRIORITIES #### Phase 1: Foundation (Week 1) 1. **Mandatory Intent Verification**: 100% compliance enforcement 2. **Automatic Task Creation**: Every work request creates task 3. **Basic Progress Monitoring**: File changes and commits 4. **Essential Changelog**: What, when, who for every change #### Phase 2: Intelligence (Week 2) 1. **Smart Status Detection**: Automatic progress suggestions 2. **Context Switching**: Seamless task transitions 3. **Enhanced Changelog**: Why, how, impact for every change 4. **Real-time Dashboard**: Developer awareness interface #### Phase 3: Optimization (Week 3) 1. **Handover Automation**: Complete knowledge transfer packages 2. **Predictive Analytics**: Completion time and blocker prediction 3. **Quality Metrics**: Continuous improvement feedback 4. **Team Collaboration**: Multi-developer coordination ### 8. CRITICAL SUCCESS FACTORS #### Non-Negotiable Requirements 1. **Zero Work Without Tasks**: Every development action must be task-linked 2. **Complete Change Tracking**: Every file modification must be documented 3. **Real-time Visibility**: Current status must always be accurate 4. **Seamless Handovers**: New developers productive within 30 minutes 5. **Continuous Learning**: System improves with every interaction #### Success Metrics - **Task Coverage**: 100% of development work tracked in tasks - **Change Documentation**: 100% of modifications captured in changelog - **Handover Speed**: <30 minutes for new developer onboarding - **Progress Accuracy**: >90% correct status predictions - **Developer Satisfaction**: >8/10 workflow helpfulness rating ### 9. ENFORCEMENT MECHANISMS #### Automated Enforcement ```typescript // SYSTEM-LEVEL: Prevent non-compliant workflows 1. Block file modifications without active task 2. Require changelog entry for every commit 3. Enforce intent verification before any action 4. Auto-pause tasks during extended inactivity 5. Mandate handover documentation before task completion ``` #### Quality Gates ```typescript // VALIDATION: Ensure completeness before progression 1. Task creation must include context and estimates 2. Status changes require evidence and confidence 3. Completion requires handover documentation 4. Deployment requires task completion verification 5. Handover requires recipient acknowledgment ``` ## INTEGRATION WITH EXISTING RULES ### Enhanced Intent Verification - **Expand scope**: Detect not just task creation but all work activities - **Add context**: Include project state, active tasks, recent changes - **Improve routing**: Direct to appropriate workflow based on intent type ### Smarter Task Monitoring - **Real-time tracking**: Monitor file changes, not just commits - **Predictive analytics**: Use patterns to predict completion - **Proactive intervention**: Detect blockers before they become critical ### Advanced Active Task Detection - **Multi-task awareness**: Handle concurrent work streams - **Context preservation**: Maintain state across task switches - **Intelligent suggestions**: Recommend task switches based on activity ### Comprehensive Deployment Integration - **Task linkage**: Every deployment must reference completed tasks - **Change documentation**: Auto-generate deployment notes from changelogs - **Rollback preparation**: Maintain rollback instructions with each deployment This comprehensive workflow ensures that every aspect of development is captured, tracked, and made visible for optimal team coordination and knowledge transfer.