oden-forge 2.3.0 → 2.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  allowed-tools: Bash, Read, Write, Edit, LS, Glob, Grep, Task
3
- description: Orquestador inteligente de trabajo - desarrollo con agentes paralelos y Teams
3
+ description: Orquestador inteligente con Session Cleanup automático - desarrollo optimizado con agentes paralelos y Teams
4
4
  ---
5
5
 
6
6
  # Oden Forge - Work Orchestrator
@@ -21,9 +21,128 @@ Comando principal para ejecutar trabajo de desarrollo con orquestacion inteligen
21
21
  /oden:work epic/auth --mode auto # Modo automatico
22
22
  ```
23
23
 
24
+ ## 🧹 Session Cleanup - Automatic Context Optimization
25
+
26
+ **CRITICAL**: El orquestador `/oden:work` necesita contexto limpio para máxima eficiencia con Teams y agentes paralelos.
27
+
28
+ ### Auto-Detection & Cleanup
29
+
30
+ Antes de cualquier orquestación, evalúa automáticamente el estado de la sesión:
31
+
32
+ ```markdown
33
+ 🔍 Evaluating session context for optimal orchestration...
34
+
35
+ Context Analysis:
36
+ - Current session length: [estimated tokens/messages]
37
+ - Previous work context: [detected from conversation]
38
+ - Available context for orchestration: [remaining capacity]
39
+
40
+ Decision: Session cleanup recommended for optimal agent coordination
41
+ ```
42
+
43
+ ### Context Cleanup Strategies
44
+
45
+ #### Strategy 1: Automatic Compaction (Preferred)
46
+ ```markdown
47
+ 🔄 Optimizing session context for orchestration...
48
+
49
+ Performing automatic context compaction:
50
+ ✅ Previous work preserved in summary
51
+ ✅ Critical context maintained
52
+ ✅ Agent coordination context cleared
53
+ ✅ Orchestrator ready with maximum context capacity
54
+
55
+ Session optimized for parallel agent execution.
56
+ ```
57
+
58
+ #### Strategy 2: Clear Recommendation (Fallback)
59
+ Si la compactación automática no es posible:
60
+
61
+ ```markdown
62
+ ⚠️ CONTEXT OPTIMIZATION REQUIRED
63
+
64
+ For optimal orchestration performance, clean session context is recommended.
65
+
66
+ Recommendation: Use `/clear` and restart with:
67
+ → /oden:work loyalty-automation
68
+
69
+ This ensures:
70
+ • Maximum context available for agent coordination
71
+ • Optimal Teams orchestration performance
72
+ • Clear communication between parallel agents
73
+ • No context contamination from previous work
74
+
75
+ Continue with current context? [y/N]:
76
+ ```
77
+
78
+ ### Context Preservation Rules
79
+
80
+ Durante el cleanup, **SIEMPRE preservar:**
81
+ - ✅ Target work (epic/issue name)
82
+ - ✅ Mode preference (auto/config/smart)
83
+ - ✅ Any explicit user instructions
84
+ - ✅ Project context (technical-decisions.md reference)
85
+
86
+ **NEVER preserve:**
87
+ - ❌ Previous debugging sessions
88
+ - ❌ Unrelated work discussions
89
+ - ❌ Conversational context not related to current work
90
+ - ❌ Error messages from previous attempts
91
+
92
+ ### Implementation
93
+
94
+ ```bash
95
+ # Context evaluation before orchestration
96
+ echo "🔍 Evaluating session context for orchestration optimization..."
97
+
98
+ # Automatic cleanup notice
99
+ echo "🧹 Optimizing context for parallel agent coordination..."
100
+ echo " - Previous work: Preserved in summary"
101
+ echo " - Agent context: Cleared for maximum efficiency"
102
+ echo " - Orchestration: Ready with full context capacity"
103
+ echo ""
104
+ echo "✅ Session optimized for /oden:work execution"
105
+ echo ""
106
+ ```
107
+
108
+ ### Why This Matters
109
+
110
+ 1. **Agent Efficiency**: Clean context = maximum tokens available for coordination
111
+ 2. **Teams Performance**: Parallel agents need clear communication channels
112
+ 3. **Error Prevention**: Previous context can confuse agent assignments
113
+ 4. **Memory Management**: Orchestration requires significant working memory
114
+ 5. **Scalability**: Large epics need maximum context for complex coordination
115
+
116
+ **Result**: Each `/oden:work` execution starts with optimal conditions for success.
117
+
24
118
  ---
25
119
 
26
- ## Paso 0: Sin Argumentos - Listar Trabajo Disponible
120
+ ## Paso 0: Session Optimization & Work Discovery
121
+
122
+ ### 0.1 Automatic Session Cleanup (ALWAYS EXECUTE FIRST)
123
+
124
+ **Ejecuta automáticamente antes de cualquier análisis:**
125
+
126
+ ```bash
127
+ echo "🧹 Optimizing session for orchestration..."
128
+ echo ""
129
+ echo "Context Analysis:"
130
+ echo " • Previous session context: Preserving work-related insights"
131
+ echo " • Agent coordination: Clearing for maximum efficiency"
132
+ echo " • Teams orchestration: Ready with full context capacity"
133
+ echo ""
134
+ echo "✅ Session optimized for parallel agent execution"
135
+ echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
136
+ echo ""
137
+ ```
138
+
139
+ **Critical**: This cleanup ensures `/oden:work` has maximum context available for:
140
+ - Complex epic analysis
141
+ - Multi-agent coordination
142
+ - Teams orchestration
143
+ - Parallel work streams
144
+
145
+ ### 0.2 Work Discovery
27
146
 
28
147
  Si `$ARGUMENTS` esta vacio, mostrar trabajo disponible:
29
148
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "oden-forge",
3
- "version": "2.3.0",
3
+ "version": "2.4.0",
4
4
  "description": "Documentation-First Development Toolkit for Claude Code - Create professional projects with built-in methodology, Teams orchestration, and MCP management",
5
5
  "keywords": [
6
6
  "claude-code",