EuConquisto Composer MCP

--- document: Project Knowledge Optimization Task version: 1.0.0 status: ready_for_execution priority: MEDIUM owner: Claude Code created: 2025-07-01 last_updated: 2025-07-01 task_id: TASK-KNOWLEDGE-OPT-001 dependencies: ["Current project documentation analysis"] estimated_duration: 60-90 minutes coordination_protocol: 4-phase-execution-plan.md --- # TASK: Project Knowledge Optimization for Token Efficiency ## 🎯 **Objective** Create session-type specific project knowledge files to optimize token usage in Claude Desktop sessions while maintaining necessary context for different types of work (analysis, coordination, implementation, deployment). ## 📋 **Task Overview** **Task ID**: TASK-KNOWLEDGE-OPT-001 **Owner**: Claude Code **Priority**: MEDIUM **Status**: READY FOR EXECUTION **Dependencies**: Current project documentation available **Estimated Duration**: 60-90 minutes **Created**: 2025-07-01 **Coordination**: Follow 4-phase-execution-plan.md protocol ## 🔄 **Implementation Requirements** ### **Target Structure** ``` project-knowledge/ ├── analysis-context.md # Architecture, requirements, technical decisions ├── coordination-context.md # Task status, handoffs, blockers, progress ├── implementation-context.md # Technical specs, APIs, file locations, code ├── deployment-context.md # Production, testing, rollout, institutional ``` ### **Content Guidelines** **analysis-context.md**: - Project architecture and technical decisions - API specifications and integration patterns - Technical requirements and constraints - Implementation strategies and approaches **coordination-context.md**: - Current task status and priorities - Handoff protocols between Claude Desktop/Code - Project milestones and completion status - Blocking issues and resolution paths **implementation-context.md**: - File locations and structure - Code specifications and patterns - Technical implementation details - Testing and validation procedures **deployment-context.md**: - Production deployment procedures - User training and institutional rollout - Success metrics and monitoring - Business context and stakeholder information ## 📊 **Success Criteria** ### **Token Efficiency** - Each context file ≤ 2000 tokens - Focused content relevant to session type - Eliminates need for full project knowledge loading ### **Content Quality** - All essential information preserved - Clear, actionable content for each session type - Cross-references between files where needed - Maintained accuracy and completeness ### **Operational Effectiveness** - Claude Desktop can quickly select appropriate context - Session objectives clearly mapped to knowledge files - Improved response speed and focus - Scalable structure for project growth ## 🔧 **Implementation Notes** ### **Source Material Analysis** - Review existing project documentation - Identify content overlap and redundancy - Categorize information by session type relevance - Preserve critical cross-references ### **Content Optimization** - Summarize verbose sections where possible - Focus on actionable information - Maintain technical accuracy - Include essential file paths and references ### **File Organization** - Consistent markdown structure - Clear section headers for quick navigation - Version control and update timestamps - Cross-reference links between context files ## ⚠️ **Implementation Constraints** ### **Content Preservation** - No critical information loss during optimization - Maintain technical accuracy - Preserve decision rationale and context - Keep essential file paths and configurations ### **Token Targets** - Each file optimized for Claude Desktop session efficiency - Balance comprehensiveness with brevity - Focus on frequently needed information - Eliminate redundant descriptions --- **Ready for immediate execution by Claude Code to improve session token efficiency across all project coordination activities.**