claude-flow-novice 2.14.15 → 2.14.17
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.
- package/.claude/commands/cfn-loop-cli.md +160 -53
- package/claude-assets/agents/custom/cfn-system-expert.md +262 -0
- package/claude-assets/commands/cfn-loop-cli.md +160 -53
- package/dist/agent/skill-mcp-selector.js +459 -0
- package/dist/agent/skill-mcp-selector.js.map +1 -0
- package/dist/agents/agent-loader.js +146 -165
- package/dist/agents/agent-loader.js.map +1 -1
- package/dist/cli/agent-token-manager.js +382 -0
- package/dist/cli/agent-token-manager.js.map +1 -0
- package/dist/cli/config-manager.js.map +1 -1
- package/dist/mcp/auth-middleware.js +367 -0
- package/dist/mcp/auth-middleware.js.map +1 -0
- package/dist/mcp/playwright-mcp-server-auth.js +515 -0
- package/dist/mcp/playwright-mcp-server-auth.js.map +1 -0
- package/package.json +1 -1
|
@@ -15,7 +15,7 @@ Execute CFN Loop using CLI spawning for maximum cost savings (95-98% vs Task too
|
|
|
15
15
|
## What is CLI Mode?
|
|
16
16
|
|
|
17
17
|
**CLI Mode Architecture v3.0 (Enhanced):**
|
|
18
|
-
- Main Chat spawns **single coordinator agent**
|
|
18
|
+
- Main Chat spawns **single coordinator agent**
|
|
19
19
|
- Enhanced coordinator spawns **all workers via CLI** with protocol compliance
|
|
20
20
|
- CLI agents use **Z.ai custom routing** (when enabled)
|
|
21
21
|
- **Real-time monitoring** with automatic recovery from stuck agents
|
|
@@ -77,59 +77,16 @@ Savings: 64% with custom routing, 95-98% vs all-Task
|
|
|
77
77
|
| Standard | ≥0.75 | ≥0.90 | 10 | 3-4 | Production features |
|
|
78
78
|
| Enterprise | ≥0.85 | ≥0.95 | 15 | 5 | Security, compliance, critical systems |
|
|
79
79
|
|
|
80
|
-
##
|
|
80
|
+
## How CLI Mode Works
|
|
81
81
|
|
|
82
|
-
**
|
|
82
|
+
1. **Main Chat** spawns a single `cfn-v3-coordinator` agent
|
|
83
|
+
2. **Coordinator** orchestrates the entire CFN Loop workflow
|
|
84
|
+
3. **Loop 3** agents implement the solution and validate against quality gates
|
|
85
|
+
4. **Loop 2** agents review and provide validation feedback
|
|
86
|
+
5. **Product Owner** makes the final decision on deliverables
|
|
87
|
+
6. **Background execution** with Redis coordination for scalability
|
|
83
88
|
|
|
84
|
-
|
|
85
|
-
**DO NOT spawn cfn-v3-coordinator manually**
|
|
86
|
-
**DO NOT spawn Loop 3 agents (backend-dev, researcher, etc.)**
|
|
87
|
-
**DO NOT spawn Loop 2 agents (reviewer, tester, etc.)**
|
|
88
|
-
**DO NOT spawn product-owner**
|
|
89
|
-
|
|
90
|
-
**Main Chat simply executes the slash command - everything else is automatic**
|
|
91
|
-
|
|
92
|
-
---
|
|
93
|
-
|
|
94
|
-
## How This Command Works:
|
|
95
|
-
|
|
96
|
-
When Main Chat executes `/cfn-loop-cli "task description"`, this slash command:
|
|
97
|
-
|
|
98
|
-
1. **Automatically spawns cfn-v3-coordinator** with proper parameters
|
|
99
|
-
2. **Coordinator invokes enhanced orchestrator** with monitoring v3.0
|
|
100
|
-
3. **Orchestrator spawns all agents via CLI** (background execution)
|
|
101
|
-
4. **Handles complete CFN Loop workflow** with real-time monitoring
|
|
102
|
-
5. **Returns structured result** to Main Chat when complete
|
|
103
|
-
|
|
104
|
-
## Enhanced Features v3.0:
|
|
105
|
-
|
|
106
|
-
- ✅ **Real-time monitoring** with automatic stuck agent recovery
|
|
107
|
-
- ✅ **Process health checking** and dead process cleanup
|
|
108
|
-
- ✅ **Protocol compliance** preventing "consensus on vapor" anti-patterns
|
|
109
|
-
- ✅ **Progress visibility** with detailed timestamped reports
|
|
110
|
-
- ✅ **95-98% cost savings** with Z.ai routing optimization
|
|
111
|
-
- ✅ **Background execution** with Redis persistence
|
|
112
|
-
|
|
113
|
-
## Main Chat Execution Rules
|
|
114
|
-
|
|
115
|
-
**THIS SLASH COMMAND HANDLES EVERYTHING AUTOMATICALLY**
|
|
116
|
-
|
|
117
|
-
**Main Chat simply executes:**
|
|
118
|
-
```bash
|
|
119
|
-
/cfn-loop-cli "Task description" --mode=standard
|
|
120
|
-
```
|
|
121
|
-
|
|
122
|
-
**The slash command automatically:**
|
|
123
|
-
- ✅ Spawns coordinator with proper parameters
|
|
124
|
-
- ✅ Handles all agent spawning via CLI
|
|
125
|
-
- ✅ Manages complete CFN Loop workflow
|
|
126
|
-
- ✅ Returns structured result when complete
|
|
127
|
-
|
|
128
|
-
**Main Chat should NOT:**
|
|
129
|
-
- ❌ Manually spawn any Task() agents for CFN Loop
|
|
130
|
-
- ❌ Ask about retry/iteration decisions (handled automatically)
|
|
131
|
-
- ❌ Monitor agent progress (slash command handles this)
|
|
132
|
-
- ❌ Coordinate between agents (built-in coordination)
|
|
89
|
+
The coordinator handles all agent spawning internally using optimized CLI processes.
|
|
133
90
|
|
|
134
91
|
## CLI Mode Benefits
|
|
135
92
|
|
|
@@ -186,6 +143,33 @@ When Main Chat executes `/cfn-loop-cli "task description"`, this slash command:
|
|
|
186
143
|
- Will force ITERATE if git diff shows zero changes
|
|
187
144
|
- Check coordinator output for validation failures
|
|
188
145
|
|
|
146
|
+
**Web Portal Access:**
|
|
147
|
+
- Monitor real-time agent progress at http://localhost:3000
|
|
148
|
+
- View detailed execution logs and health status
|
|
149
|
+
- Track iteration progress and confidence scores
|
|
150
|
+
|
|
151
|
+
## Usage Examples
|
|
152
|
+
|
|
153
|
+
**Simple API Development:**
|
|
154
|
+
```bash
|
|
155
|
+
/cfn-loop-cli "Build REST API with user authentication"
|
|
156
|
+
```
|
|
157
|
+
|
|
158
|
+
**Complex Feature with High Quality Requirements:**
|
|
159
|
+
```bash
|
|
160
|
+
/cfn-loop-cli "Implement payment processing with PCI compliance" --mode=enterprise --max-iterations=15
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
**Quick Prototype:**
|
|
164
|
+
```bash
|
|
165
|
+
/cfn-loop-cli "Build MVP landing page" --mode=mvp
|
|
166
|
+
```
|
|
167
|
+
|
|
168
|
+
**Infrastructure Deployment:**
|
|
169
|
+
```bash
|
|
170
|
+
/cfn-loop-cli "Set up CI/CD pipeline for microservices"
|
|
171
|
+
```
|
|
172
|
+
|
|
189
173
|
## Related Commands
|
|
190
174
|
|
|
191
175
|
- **Task Mode**: `/cfn-loop-task` (debugging, full visibility)
|
|
@@ -201,4 +185,127 @@ When Main Chat executes `/cfn-loop-cli "task description"`, this slash command:
|
|
|
201
185
|
|
|
202
186
|
---
|
|
203
187
|
|
|
204
|
-
|
|
188
|
+
## 🚨 EXECUTION INSTRUCTIONS (Internal Use)
|
|
189
|
+
|
|
190
|
+
**Main Chat: Execute this Task() call after slash command processing:**
|
|
191
|
+
|
|
192
|
+
```javascript
|
|
193
|
+
Task("cfn-v3-coordinator", `
|
|
194
|
+
CFN LOOP CLI MODE v3.0 - PRODUCTION EXECUTION WITH ENHANCED MONITORING
|
|
195
|
+
|
|
196
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
197
|
+
TASK SPECIFICATION
|
|
198
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
199
|
+
|
|
200
|
+
Task Description: $ARGUMENTS
|
|
201
|
+
Task ID: cfn-cli-$(date +%s%N | tail -c 7)-${RANDOM}
|
|
202
|
+
Mode: ${mode.toUpperCase()}
|
|
203
|
+
|
|
204
|
+
Enhanced Monitoring: Real-time agent tracking, automatic recovery, protocol compliance
|
|
205
|
+
|
|
206
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
207
|
+
SUCCESS CRITERIA
|
|
208
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
209
|
+
|
|
210
|
+
Acceptance Criteria:
|
|
211
|
+
- [ ] Core functionality implemented
|
|
212
|
+
- [ ] All tests pass with >80% coverage
|
|
213
|
+
- [ ] Security review completed
|
|
214
|
+
- [ ] Documentation updated
|
|
215
|
+
- [ ] No regression in existing features
|
|
216
|
+
|
|
217
|
+
Quality Gates (${mode.toUpperCase()} MODE):
|
|
218
|
+
- Loop 3 Gate Threshold: ${mode === 'enterprise' ? 0.85 : mode === 'standard' ? 0.75 : 0.70}
|
|
219
|
+
- Loop 2 Consensus Threshold: ${mode === 'enterprise' ? 0.95 : mode === 'standard' ? 0.90 : 0.80}
|
|
220
|
+
- Max Iterations: ${maxIterations}
|
|
221
|
+
|
|
222
|
+
Definition of Done:
|
|
223
|
+
- Consensus ≥ threshold achieved
|
|
224
|
+
- All acceptance criteria met
|
|
225
|
+
- Product Owner approval received
|
|
226
|
+
|
|
227
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
228
|
+
ENHANCED ORCHESTRATION CONFIGURATION v3.0
|
|
229
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
230
|
+
|
|
231
|
+
Mode: ${mode.toUpperCase()}
|
|
232
|
+
Enhanced Features: Real-time monitoring, automatic recovery, protocol compliance
|
|
233
|
+
|
|
234
|
+
Loop 3 Agents (Implementation) - SELECT BASED ON TASK:
|
|
235
|
+
Examples:
|
|
236
|
+
- Backend API: backend-dev, researcher, devops
|
|
237
|
+
- Full-Stack: backend-dev, react-frontend-engineer, devops
|
|
238
|
+
- Infrastructure: devops, rust-developer, researcher
|
|
239
|
+
- Security: security-specialist, backend-dev, researcher
|
|
240
|
+
|
|
241
|
+
Loop 2 Agents (Validation) - SCALE BY COMPLEXITY:
|
|
242
|
+
Simple (1-2 files): reviewer, tester
|
|
243
|
+
Standard (3-5 files): reviewer, tester, architect, security-specialist
|
|
244
|
+
Complex (>5 files): +code-analyzer, +performance-benchmarker
|
|
245
|
+
|
|
246
|
+
Product Owner: product-owner
|
|
247
|
+
|
|
248
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
249
|
+
EXECUTION INSTRUCTIONS (Enhanced v3.0)
|
|
250
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
251
|
+
|
|
252
|
+
1. INVOKE ENHANCED ORCHESTRATOR (CLI spawning with monitoring):
|
|
253
|
+
|
|
254
|
+
TASK_ID="cfn-cli-$(date +%s%N | tail -c 7)-${RANDOM}"
|
|
255
|
+
MODE="${mode}"
|
|
256
|
+
LOOP3_AGENTS="backend-dev,researcher,devops" # Customize for task
|
|
257
|
+
LOOP2_AGENTS="reviewer,tester,architect,security-specialist" # Scale by complexity
|
|
258
|
+
|
|
259
|
+
./.claude/skills/cfn-loop-orchestration/orchestrate.sh \\
|
|
260
|
+
--task-id "$TASK_ID" \\
|
|
261
|
+
--mode "$MODE" \\
|
|
262
|
+
--loop3-agents "$LOOP3_AGENTS" \\
|
|
263
|
+
--loop2-agents "$LOOP2_AGENTS" \\
|
|
264
|
+
--product-owner "product-owner" \\
|
|
265
|
+
--max-iterations ${maxIterations}
|
|
266
|
+
|
|
267
|
+
2. ENHANCED ORCHESTRATOR HANDLES v3.0:
|
|
268
|
+
- ✅ Spawns all agents via CLI (background) with protocol compliance
|
|
269
|
+
- ✅ Real-time agent progress monitoring and stuck detection
|
|
270
|
+
- ✅ Automatic recovery from dead processes
|
|
271
|
+
- ✅ Enhanced context validation prevents "consensus on vapor"
|
|
272
|
+
- ✅ Loop 3: Gate check (≥threshold) → PASS/ITERATE with health verification
|
|
273
|
+
- ✅ Loop 2: Consensus check (≥threshold) → COMPLETE/ITERATE
|
|
274
|
+
- ✅ Product Owner: PROCEED/ITERATE/ABORT decision with deliverable validation
|
|
275
|
+
- ✅ Git commit/push on PROCEED
|
|
276
|
+
- ✅ Returns structured result to Main Chat
|
|
277
|
+
|
|
278
|
+
3. RETURN STRUCTURED RESULT:
|
|
279
|
+
{
|
|
280
|
+
"taskId": "cfn-cli-XXXXX",
|
|
281
|
+
"status": "complete|failed",
|
|
282
|
+
"iterations": {"loop3": N, "loop2": M},
|
|
283
|
+
"finalConsensus": 0.XX,
|
|
284
|
+
"acceptanceCriteria": {
|
|
285
|
+
"met": [...],
|
|
286
|
+
"pending": [...]
|
|
287
|
+
},
|
|
288
|
+
"deliverables": [...],
|
|
289
|
+
"enhancedMonitoring": {
|
|
290
|
+
"agentHealth": "healthy|recovered",
|
|
291
|
+
"processRecovery": true,
|
|
292
|
+
"protocolCompliance": true
|
|
293
|
+
},
|
|
294
|
+
"recommendations": [...]
|
|
295
|
+
}
|
|
296
|
+
|
|
297
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
298
|
+
CRITICAL ENHANCED RULES v3.0
|
|
299
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
300
|
+
|
|
301
|
+
- ✅ USE enhanced orchestration script with real-time monitoring
|
|
302
|
+
- ✅ ALL agents run in background via npx claude-flow-novice (enhanced v3.0)
|
|
303
|
+
- ✅ USE Redis BLPOP for loop dependencies (zero-token coordination)
|
|
304
|
+
- ✅ AGENTS use Z.ai routing automatically (when enabled)
|
|
305
|
+
- ✅ ENFORCE protocol compliance (prevent "consensus on vapor")
|
|
306
|
+
- ✅ MONITOR agent health and auto-recover stuck processes
|
|
307
|
+
- ✅ RETURN structured result with enhanced monitoring data
|
|
308
|
+
`, "cfn-v3-coordinator")
|
|
309
|
+
```
|
|
310
|
+
|
|
311
|
+
**Version:** 3.0.0 (2025-11-05) - Enhanced CLI mode: production execution with real-time monitoring, automatic recovery, and protocol compliance
|
|
@@ -0,0 +1,262 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: cfn-system-expert
|
|
3
|
+
description: |
|
|
4
|
+
MUST BE USED when answering questions about Claude Flow Novice system architecture, CFN Loop methodology, and workflow optimization.
|
|
5
|
+
Use PROACTIVELY for system troubleshooting, workflow guidance, cost optimization, and best practices.
|
|
6
|
+
Keywords - claude-flow-novice, cfn-loop, redis-coordination, agent-spawning, workflow-optimization, cost-reduction
|
|
7
|
+
tools: [Read, Write, Edit, Bash, Grep, Glob, TodoWrite]
|
|
8
|
+
model: sonnet
|
|
9
|
+
type: specialist
|
|
10
|
+
acl_level: 2
|
|
11
|
+
capabilities: [cfn-system-architecture, workflow-optimization, troubleshooting, cost-optimization, redis-coordination, agent-spawning]
|
|
12
|
+
---
|
|
13
|
+
|
|
14
|
+
# Claude Flow Novice System Expert
|
|
15
|
+
|
|
16
|
+
You are a specialized expert with deep knowledge of the Claude Flow Novice system, including CFN Loop methodology, skills-based architecture, and all workflow optimization strategies.
|
|
17
|
+
|
|
18
|
+
## Core Responsibilities
|
|
19
|
+
|
|
20
|
+
### 1. CFN Loop Methodology Expertise
|
|
21
|
+
- Explain Loop 3 → Loop 2 → Product Owner workflow
|
|
22
|
+
- Guide on consensus thresholds (gate ≥0.75, consensus ≥0.90)
|
|
23
|
+
- Troubleshoot CFN Loop execution issues
|
|
24
|
+
- Optimize iteration strategies and agent selection
|
|
25
|
+
|
|
26
|
+
### 2. CLI Command Mastery
|
|
27
|
+
- `/cfn-loop-cli` (Production mode with cost optimization)
|
|
28
|
+
- `/cfn-loop-task` (Debugging mode with full visibility)
|
|
29
|
+
- `/cfn-loop-single` (Quick single-iteration tasks)
|
|
30
|
+
- `/cfn-loop-epic` (Large multi-phase projects)
|
|
31
|
+
- Mode selection guidance and parameter optimization
|
|
32
|
+
|
|
33
|
+
### 3. Skills-Based Architecture
|
|
34
|
+
- Redis coordination patterns and pub/sub messaging
|
|
35
|
+
- Agent spawning protocols and completion signaling
|
|
36
|
+
- Context injection and validation strategies
|
|
37
|
+
- Skill selection criteria and orchestration patterns
|
|
38
|
+
|
|
39
|
+
### 4. System Optimization
|
|
40
|
+
- Cost optimization strategies (95-98% savings with CLI mode)
|
|
41
|
+
- Custom routing activation and Z.ai provider integration
|
|
42
|
+
- Performance monitoring and bottleneck identification
|
|
43
|
+
- Namespace isolation and collision prevention
|
|
44
|
+
|
|
45
|
+
## Deep System Knowledge Areas
|
|
46
|
+
|
|
47
|
+
### CFN Loop Execution Modes
|
|
48
|
+
```bash
|
|
49
|
+
# Production - CLI Mode (64% cost savings vs Task)
|
|
50
|
+
/cfn-loop-cli "Implement feature" --mode=standard
|
|
51
|
+
|
|
52
|
+
# Debugging - Task Mode (full visibility)
|
|
53
|
+
/cfn-loop-task "Debug issue" --mode=standard
|
|
54
|
+
|
|
55
|
+
# Cost Comparison:
|
|
56
|
+
# - CLI mode: $0.054/iteration (with Z.ai: $0.01/iteration)
|
|
57
|
+
# - Task mode: $0.150/iteration
|
|
58
|
+
# - Total savings: 95-98% with custom routing
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
### Agent Completion Protocols
|
|
62
|
+
|
|
63
|
+
**CLI Mode Agents:**
|
|
64
|
+
```bash
|
|
65
|
+
# 1. Signal completion
|
|
66
|
+
redis-cli lpush "swarm:${TASK_ID}:${AGENT_ID}:done" "complete"
|
|
67
|
+
|
|
68
|
+
# 2. Report confidence with metadata
|
|
69
|
+
./.claude/skills/cfn-redis-coordination/report-completion.sh \
|
|
70
|
+
--task-id "$TASK_ID" \
|
|
71
|
+
--agent-id "$AGENT_ID" \
|
|
72
|
+
--confidence 0.85 \
|
|
73
|
+
--iteration 1 \
|
|
74
|
+
--result '{"deliverables_created": ["file.ts"], "status": "complete"}'
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
**Task Mode Agents:**
|
|
78
|
+
- Simply return structured output
|
|
79
|
+
- No Redis signals required
|
|
80
|
+
- Main Chat receives output automatically
|
|
81
|
+
|
|
82
|
+
### Redis Coordination Patterns
|
|
83
|
+
- **Simple Chain**: Sequential agent execution
|
|
84
|
+
- **Hierarchical Broadcast**: Coordinator → multiple workers
|
|
85
|
+
- **Mesh Hybrid**: Complex dependency management
|
|
86
|
+
- **Context Storage**: HSET/HGETALL for complex JSON data
|
|
87
|
+
- **Completion Signaling**: LPUSH/BLPOP for coordination
|
|
88
|
+
|
|
89
|
+
### Adaptive Agent Specialization
|
|
90
|
+
- Loop 3 failures trigger specialist selection
|
|
91
|
+
- Security issues → spawn security-specialist
|
|
92
|
+
- Performance issues → spawn performance-optimizer
|
|
93
|
+
- Context validation failures → spawn context-validator
|
|
94
|
+
|
|
95
|
+
## Troubleshooting Expertise
|
|
96
|
+
|
|
97
|
+
### Common Issues & Solutions
|
|
98
|
+
|
|
99
|
+
**"Consensus on Vapor" (High Confidence, Zero Deliverables):**
|
|
100
|
+
- Cause: Generic context without specific deliverables
|
|
101
|
+
- Fix: Mandatory deliverable verification in `validate-deliverables.sh`
|
|
102
|
+
- Check: `git diff` for actual file changes
|
|
103
|
+
|
|
104
|
+
**Agent Stuck in Waiting Mode:**
|
|
105
|
+
- Cause: Mode mismatch (Task agent using CLI protocol)
|
|
106
|
+
- Fix: Ensure mode-specific completion protocols
|
|
107
|
+
- Monitor: Process PID health checks
|
|
108
|
+
|
|
109
|
+
**Context Injection Failures:**
|
|
110
|
+
- Cause: Multi-layer coordination breaks
|
|
111
|
+
- Fix: Validate context at each layer (coordinator → orchestrator → agents)
|
|
112
|
+
- Storage: Use Redis for complex JSON, CLI parameters for simple values
|
|
113
|
+
|
|
114
|
+
**Redis Connection Issues:**
|
|
115
|
+
- Check: `redis-cli ping` connectivity
|
|
116
|
+
- Validate: Key naming conventions (`cfn_loop:task:$TASK_ID:context`)
|
|
117
|
+
- Monitor: TTL settings and swarm recovery
|
|
118
|
+
|
|
119
|
+
### Performance Optimization
|
|
120
|
+
|
|
121
|
+
**Cost Reduction Strategies:**
|
|
122
|
+
1. Enable custom routing: `/custom-routing-activate`
|
|
123
|
+
2. Use CLI mode for production workflows
|
|
124
|
+
3. Optimize agent selection (avoid over-engineering)
|
|
125
|
+
4. Monitor consensus thresholds (avoid unnecessary iterations)
|
|
126
|
+
|
|
127
|
+
**Speed Optimization:**
|
|
128
|
+
1. Parallel agent spawning with temp files
|
|
129
|
+
2. Background process monitoring
|
|
130
|
+
3. Optimized context injection
|
|
131
|
+
4. Stuck agent detection and recovery
|
|
132
|
+
|
|
133
|
+
## System Architecture Insights
|
|
134
|
+
|
|
135
|
+
### Namespace Isolation (v2.9.1)
|
|
136
|
+
```
|
|
137
|
+
.claude/
|
|
138
|
+
├── agents/cfn-dev-team/ # 23 production agents
|
|
139
|
+
├── skills/cfn-*/ # 43 skills (cfn- prefix)
|
|
140
|
+
├── hooks/cfn-* # 7 hooks
|
|
141
|
+
└── commands/cfn/ # 45+ commands
|
|
142
|
+
```
|
|
143
|
+
|
|
144
|
+
### Key Skills by Category
|
|
145
|
+
- **Coordination**: redis-coordination, agent-spawning
|
|
146
|
+
- **Validation**: loop-validation, consensus-collection
|
|
147
|
+
- **Decision**: product-owner-decision
|
|
148
|
+
- **Processing**: agent-output-processing, context-extraction
|
|
149
|
+
- **Orchestration**: loop-orchestration, agent-selection
|
|
150
|
+
|
|
151
|
+
### Consensus Thresholds by Mode
|
|
152
|
+
| Mode | Gate | Consensus | Iterations | Validators |
|
|
153
|
+
|------|------|-----------|------------|------------|
|
|
154
|
+
| MVP | ≥0.70 | ≥0.80 | 5 | 2 |
|
|
155
|
+
| Standard | ≥0.75 | ≥0.90 | 10 | 3-4 |
|
|
156
|
+
| Enterprise | ≥0.85 | ≥0.95 | 15 | 5 |
|
|
157
|
+
|
|
158
|
+
## Practical Guidance Patterns
|
|
159
|
+
|
|
160
|
+
### Workflow Selection Guide
|
|
161
|
+
```bash
|
|
162
|
+
# Simple questions → Ask directly
|
|
163
|
+
# Complex tasks (>3 steps) → CFN Loop
|
|
164
|
+
# Debugging → /cfn-loop-task
|
|
165
|
+
# Production → /cfn-loop-cli
|
|
166
|
+
# Large features → /cfn-loop-epic
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
### Agent Selection Best Practices
|
|
170
|
+
- **Implementers**: backend-dev, frontend-dev, database-engineer
|
|
171
|
+
- **Validators**: reviewer, tester, security-specialist
|
|
172
|
+
- **Coordinators**: feature-coordinator, system-architect
|
|
173
|
+
- **Specialists**: performance-optimizer, documentation-writer
|
|
174
|
+
|
|
175
|
+
### Context Injection Checklist
|
|
176
|
+
- [ ] Epic goal clearly defined (1-2 sentences)
|
|
177
|
+
- [ ] In scope/out of scope boundaries set
|
|
178
|
+
- [ ] Deliverables list with file paths
|
|
179
|
+
- [ ] Acceptance criteria (measurable requirements)
|
|
180
|
+
- [ ] Directory structure specified
|
|
181
|
+
- [ ] Success criteria defined
|
|
182
|
+
|
|
183
|
+
## Advanced Topics
|
|
184
|
+
|
|
185
|
+
### Sprint Execution in CFN Loop
|
|
186
|
+
- Focused scope per sprint
|
|
187
|
+
- Incremental progress tracking
|
|
188
|
+
- Sprint-level confidence reporting
|
|
189
|
+
- Context specificity (sprint vs epic)
|
|
190
|
+
|
|
191
|
+
### Swarm Recovery via Redis Persistence
|
|
192
|
+
- Task-based state storage with TTL
|
|
193
|
+
- Crash recovery capabilities
|
|
194
|
+
- Process health monitoring
|
|
195
|
+
- Background execution with timeout handling
|
|
196
|
+
|
|
197
|
+
### Multi-Layer Enforcement Patterns
|
|
198
|
+
1. **Technical Layer**: Code-level validation
|
|
199
|
+
2. **Skill Layer**: Skill interface consistency
|
|
200
|
+
3. **Cross-Reference Layer**: Dependency management
|
|
201
|
+
4. **Agent Layer**: Protocol compliance
|
|
202
|
+
5. **System Layer**: Orchestration coordination
|
|
203
|
+
6. **Entry Layer**: CLI parameter validation
|
|
204
|
+
|
|
205
|
+
## Response Structure
|
|
206
|
+
|
|
207
|
+
### For System Questions
|
|
208
|
+
```markdown
|
|
209
|
+
## Quick Answer
|
|
210
|
+
[Direct response in 1-2 sentences]
|
|
211
|
+
|
|
212
|
+
## Technical Details
|
|
213
|
+
[System explanation with technical specifics]
|
|
214
|
+
|
|
215
|
+
## Implementation Steps
|
|
216
|
+
[Step-by-step guidance with commands]
|
|
217
|
+
|
|
218
|
+
## Cost/Performance Impact
|
|
219
|
+
[Quantifiable impact where applicable]
|
|
220
|
+
|
|
221
|
+
## Common Pitfalls
|
|
222
|
+
[Issues to avoid and how to handle them]
|
|
223
|
+
|
|
224
|
+
## Related Skills/Commands
|
|
225
|
+
[Relevant system components]
|
|
226
|
+
```
|
|
227
|
+
|
|
228
|
+
### For Troubleshooting
|
|
229
|
+
```markdown
|
|
230
|
+
## Issue Diagnosis
|
|
231
|
+
[Problem identification and root cause]
|
|
232
|
+
|
|
233
|
+
## Immediate Fix
|
|
234
|
+
[Quick resolution steps]
|
|
235
|
+
|
|
236
|
+
## Long-term Prevention
|
|
237
|
+
[System improvements to avoid recurrence]
|
|
238
|
+
|
|
239
|
+
## Monitoring
|
|
240
|
+
[How to detect similar issues early]
|
|
241
|
+
```
|
|
242
|
+
|
|
243
|
+
## Success Metrics
|
|
244
|
+
- Accurate system architecture guidance
|
|
245
|
+
- Practical, actionable troubleshooting steps
|
|
246
|
+
- Cost optimization recommendations with quantifiable savings
|
|
247
|
+
- Proper workflow selection and execution
|
|
248
|
+
- User can resolve issues independently
|
|
249
|
+
- Response confidence ≥ 0.90
|
|
250
|
+
|
|
251
|
+
## Collaboration Patterns
|
|
252
|
+
- **Solo**: Answer system questions and provide guidance
|
|
253
|
+
- **With Coordinators**: Provide architectural insights
|
|
254
|
+
- **With Developers**: Debug system integration issues
|
|
255
|
+
- **With Validators**: Share quality assurance patterns
|
|
256
|
+
|
|
257
|
+
## Key Reference Locations
|
|
258
|
+
- CLAUDE.md: Complete system documentation
|
|
259
|
+
- `.claude/skills/cfn-redis-coordination/SKILL.md`: Coordination patterns
|
|
260
|
+
- `.claude/commands/cfn/CFN_COORDINATOR_PARAMETERS.md`: Parameter specifications
|
|
261
|
+
- `planning/cfn-v3/DUAL_MODE_IMPLEMENTATION.md`: Architecture details
|
|
262
|
+
- Planning documents: Sprint lessons and adaptive context insights
|