cc-mirror 1.0.3 → 1.1.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.
Files changed (25) hide show
  1. package/README.md +168 -98
  2. package/dist/cc-mirror.mjs +807 -287
  3. package/dist/skills/multi-agent-orchestrator/SKILL.md +391 -0
  4. package/dist/skills/multi-agent-orchestrator/references/code-review.md +266 -0
  5. package/dist/skills/multi-agent-orchestrator/references/data-analysis.md +315 -0
  6. package/dist/skills/multi-agent-orchestrator/references/devops.md +309 -0
  7. package/dist/skills/multi-agent-orchestrator/references/documentation.md +310 -0
  8. package/dist/skills/multi-agent-orchestrator/references/domains/code-review.md +301 -0
  9. package/dist/skills/multi-agent-orchestrator/references/domains/data-analysis.md +347 -0
  10. package/dist/skills/multi-agent-orchestrator/references/domains/devops.md +340 -0
  11. package/dist/skills/multi-agent-orchestrator/references/domains/documentation.md +343 -0
  12. package/dist/skills/multi-agent-orchestrator/references/domains/project-management.md +370 -0
  13. package/dist/skills/multi-agent-orchestrator/references/domains/research.md +322 -0
  14. package/dist/skills/multi-agent-orchestrator/references/domains/software-development.md +269 -0
  15. package/dist/skills/multi-agent-orchestrator/references/domains/testing.md +313 -0
  16. package/dist/skills/multi-agent-orchestrator/references/examples.md +377 -0
  17. package/dist/skills/multi-agent-orchestrator/references/guide.md +327 -0
  18. package/dist/skills/multi-agent-orchestrator/references/patterns.md +441 -0
  19. package/dist/skills/multi-agent-orchestrator/references/project-management.md +345 -0
  20. package/dist/skills/multi-agent-orchestrator/references/research.md +285 -0
  21. package/dist/skills/multi-agent-orchestrator/references/software-development.md +242 -0
  22. package/dist/skills/multi-agent-orchestrator/references/testing.md +282 -0
  23. package/dist/skills/multi-agent-orchestrator/references/tools.md +454 -0
  24. package/dist/tui.mjs +1063 -405
  25. package/package.json +2 -2
@@ -0,0 +1,343 @@
1
+ # Documentation Orchestration Patterns
2
+
3
+ ```
4
+ ┌─────────────────────────────────────────────────────────────┐
5
+ │ │
6
+ │ Good documentation is parallel-friendly. │
7
+ │ Multiple sections, generated simultaneously. │
8
+ │ │
9
+ └─────────────────────────────────────────────────────────────┘
10
+ ```
11
+
12
+ > **Load when**: API documentation, code documentation, README generation, architecture docs, user guides
13
+ > **Common patterns**: Endpoint Discovery, Batch JSDoc Generation, Comprehensive README
14
+
15
+ ## Table of Contents
16
+
17
+ 1. [API Documentation](#api-documentation)
18
+ 2. [Code Documentation](#code-documentation)
19
+ 3. [README Generation](#readme-generation)
20
+ 4. [Architecture Documentation](#architecture-documentation)
21
+ 5. [User Guides](#user-guides)
22
+
23
+ ---
24
+
25
+ ## API Documentation
26
+
27
+ ### Pattern: Endpoint Discovery and Documentation
28
+
29
+ ```
30
+ User Request: "Document all REST API endpoints"
31
+
32
+ Phase 1: EXPLORE
33
+ └─ Explore agent: Find all route definitions
34
+
35
+ Phase 2: FAN-OUT (Parallel documentation by domain)
36
+ ├─ Agent A: Document auth endpoints
37
+ ├─ Agent B: Document user endpoints
38
+ ├─ Agent C: Document product endpoints
39
+ └─ Agent D: Document order endpoints
40
+
41
+ Phase 3: REDUCE
42
+ └─ General-purpose agent: Compile into unified OpenAPI/Swagger spec
43
+ ```
44
+
45
+ ### Pattern: Request/Response Documentation
46
+
47
+ ```
48
+ Phase 1: EXPLORE
49
+ └─ Explore agent: Find endpoint handlers and schemas
50
+
51
+ Phase 2: FAN-OUT (Per endpoint group)
52
+ ├─ Agent A: Document request schemas, validation
53
+ ├─ Agent B: Document response schemas, status codes
54
+ └─ Agent C: Document error responses
55
+
56
+ Phase 3: PIPELINE
57
+ └─ General-purpose agent: Generate examples, test payloads
58
+ ```
59
+
60
+ ### Pattern: Interactive Documentation
61
+
62
+ ```
63
+ Phase 1: PIPELINE (Foundation)
64
+ ├─ Explore agent: Extract all endpoints with types
65
+ └─ General-purpose agent: Generate OpenAPI spec
66
+
67
+ Phase 2: FAN-OUT (Enhancement)
68
+ ├─ Agent A: Add example requests
69
+ ├─ Agent B: Add example responses
70
+ └─ Agent C: Add authentication examples
71
+
72
+ Phase 3: PIPELINE
73
+ └─ General-purpose agent: Setup Swagger UI / Redoc
74
+ ```
75
+
76
+ ---
77
+
78
+ ## Code Documentation
79
+
80
+ ### Pattern: Batch JSDoc/Docstring Generation
81
+
82
+ ```
83
+ User Request: "Add documentation to the utils module"
84
+
85
+ Phase 1: EXPLORE
86
+ └─ Explore agent: Find all undocumented functions
87
+
88
+ Phase 2: MAP (Parallel documentation)
89
+ ├─ Agent A: Document file1.ts functions
90
+ ├─ Agent B: Document file2.ts functions
91
+ └─ Agent C: Document file3.ts functions
92
+
93
+ Phase 3: PIPELINE
94
+ └─ General-purpose agent: Verify consistency, generate type docs
95
+ ```
96
+
97
+ ### Pattern: Complexity-Driven Documentation
98
+
99
+ ```
100
+ Phase 1: EXPLORE
101
+ └─ Explore agent: Find complex functions (high cyclomatic complexity)
102
+
103
+ Phase 2: FAN-OUT (Prioritized)
104
+ ├─ Agent A: Document most complex function
105
+ ├─ Agent B: Document second most complex
106
+ └─ Agent C: Document third most complex
107
+
108
+ Each agent:
109
+ - Explain algorithm/logic
110
+ - Document edge cases
111
+ - Add usage examples
112
+ ```
113
+
114
+ ### Pattern: Module Overview Generation
115
+
116
+ ```
117
+ Phase 1: EXPLORE
118
+ └─ Explore agent: Map module structure, exports, dependencies
119
+
120
+ Phase 2: PIPELINE
121
+ ├─ General-purpose agent: Write module overview
122
+ ├─ General-purpose agent: Document public API
123
+ └─ General-purpose agent: Add usage examples
124
+
125
+ Phase 3: FAN-OUT (Internal docs)
126
+ ├─ Agent A: Document internal utilities
127
+ └─ Agent B: Document configuration options
128
+ ```
129
+
130
+ ---
131
+
132
+ ## README Generation
133
+
134
+ ### Pattern: Comprehensive README
135
+
136
+ ```
137
+ User Request: "Create a README for this project"
138
+
139
+ Phase 1: FAN-OUT (Parallel information gathering)
140
+ ├─ Explore agent: Project structure and technologies
141
+ ├─ Explore agent: Build and run scripts (package.json, Makefile)
142
+ ├─ Explore agent: Environment variables and config
143
+ ├─ Explore agent: Test setup and commands
144
+ └─ Explore agent: Existing docs and comments
145
+
146
+ Phase 2: REDUCE
147
+ └─ General-purpose agent: Synthesize into structured README
148
+
149
+ Sections:
150
+ - Overview and purpose
151
+ - Quick start
152
+ - Installation
153
+ - Configuration
154
+ - Usage examples
155
+ - Development setup
156
+ - Testing
157
+ - Contributing
158
+ ```
159
+
160
+ ### Pattern: README Update
161
+
162
+ ```
163
+ Phase 1: FAN-OUT
164
+ ├─ Explore agent: Current README content
165
+ ├─ Explore agent: Recent changes to codebase
166
+ └─ Explore agent: New dependencies or features
167
+
168
+ Phase 2: PIPELINE
169
+ └─ General-purpose agent: Update README sections, maintain style
170
+ ```
171
+
172
+ ---
173
+
174
+ ## Architecture Documentation
175
+
176
+ ### Pattern: C4 Model Documentation
177
+
178
+ ```
179
+ User Request: "Document the system architecture"
180
+
181
+ Phase 1: FAN-OUT (Parallel level documentation)
182
+ ├─ Agent A: Context diagram (system + external actors)
183
+ ├─ Agent B: Container diagram (applications, data stores)
184
+ ├─ Agent C: Component diagram (internal components)
185
+ └─ Agent D: Code diagram (critical classes/modules)
186
+
187
+ Phase 2: REDUCE
188
+ └─ General-purpose agent: Compile into architecture doc with diagrams
189
+ ```
190
+
191
+ ### Pattern: Decision Record Generation
192
+
193
+ ```
194
+ Phase 1: EXPLORE
195
+ └─ Explore agent: Find architectural patterns in code
196
+
197
+ Phase 2: FAN-OUT
198
+ ├─ Agent A: Document decision 1 (why this database?)
199
+ ├─ Agent B: Document decision 2 (why this framework?)
200
+ └─ Agent C: Document decision 3 (why this structure?)
201
+
202
+ Each ADR includes:
203
+ - Context
204
+ - Decision
205
+ - Consequences
206
+ - Alternatives considered
207
+ ```
208
+
209
+ ### Pattern: Data Flow Documentation
210
+
211
+ ```
212
+ Phase 1: EXPLORE
213
+ └─ Explore agent: Trace data through system
214
+
215
+ Phase 2: PIPELINE
216
+ ├─ General-purpose agent: Document ingress points
217
+ ├─ General-purpose agent: Document transformations
218
+ ├─ General-purpose agent: Document storage
219
+ └─ General-purpose agent: Document egress points
220
+
221
+ Phase 3: REDUCE
222
+ └─ General-purpose agent: Create data flow diagram
223
+ ```
224
+
225
+ ---
226
+
227
+ ## User Guides
228
+
229
+ ### Pattern: Feature-Based Guides
230
+
231
+ ```
232
+ User Request: "Write user documentation for the dashboard"
233
+
234
+ Phase 1: EXPLORE
235
+ └─ Explore agent: Map dashboard features and capabilities
236
+
237
+ Phase 2: FAN-OUT (Parallel feature guides)
238
+ ├─ Agent A: Guide for feature 1 (with screenshots)
239
+ ├─ Agent B: Guide for feature 2
240
+ ├─ Agent C: Guide for feature 3
241
+ └─ Agent D: Troubleshooting guide
242
+
243
+ Phase 3: REDUCE
244
+ └─ General-purpose agent: Compile into user manual with TOC
245
+ ```
246
+
247
+ ### Pattern: Tutorial Generation
248
+
249
+ ```
250
+ Phase 1: EXPLORE
251
+ └─ Explore agent: Identify key user workflows
252
+
253
+ Phase 2: PIPELINE (Sequential tutorials)
254
+ ├─ General-purpose agent: Getting started tutorial
255
+ ├─ General-purpose agent: Basic usage tutorial
256
+ ├─ General-purpose agent: Advanced usage tutorial
257
+ └─ General-purpose agent: Best practices guide
258
+ ```
259
+
260
+ ### Pattern: FAQ Generation
261
+
262
+ ```
263
+ Phase 1: FAN-OUT
264
+ ├─ Explore agent: Common patterns in issues/tickets
265
+ ├─ Explore agent: Error messages and their causes
266
+ └─ Explore agent: Configuration gotchas
267
+
268
+ Phase 2: REDUCE
269
+ └─ General-purpose agent: Compile FAQ with clear answers
270
+ ```
271
+
272
+ ---
273
+
274
+ ## Documentation Quality Patterns
275
+
276
+ ### Pattern: Consistency Audit
277
+
278
+ ```
279
+ Phase 1: FAN-OUT
280
+ ├─ Agent A: Check terminology consistency
281
+ ├─ Agent B: Check formatting consistency
282
+ ├─ Agent C: Check example code validity
283
+ └─ Agent D: Check link validity
284
+
285
+ Phase 2: REDUCE
286
+ └─ General-purpose agent: Inconsistency report with fixes
287
+ ```
288
+
289
+ ### Pattern: Freshness Check
290
+
291
+ ```
292
+ Phase 1: FAN-OUT
293
+ ├─ Explore agent: Find outdated code examples
294
+ ├─ Explore agent: Find references to removed features
295
+ └─ Explore agent: Find mismatched version numbers
296
+
297
+ Phase 2: PIPELINE
298
+ └─ General-purpose agent: Update stale documentation
299
+ ```
300
+
301
+ ---
302
+
303
+ ## Task Management for Documentation
304
+
305
+ Structure documentation work with parallel generation:
306
+
307
+ ```python
308
+ # Create documentation tasks
309
+ TaskCreate(subject="Audit existing docs", description="Review current documentation state...")
310
+ TaskCreate(subject="Document API endpoints", description="REST API documentation...")
311
+ TaskCreate(subject="Document components", description="React component docs...")
312
+ TaskCreate(subject="Document utilities", description="Helper function docs...")
313
+ TaskCreate(subject="Review consistency", description="Ensure consistent style...")
314
+ TaskCreate(subject="Verify examples", description="Test all code examples...")
315
+
316
+ # Parallel doc generation after audit
317
+ TaskUpdate(taskId="2", addBlockedBy=["1"])
318
+ TaskUpdate(taskId="3", addBlockedBy=["1"])
319
+ TaskUpdate(taskId="4", addBlockedBy=["1"])
320
+ TaskUpdate(taskId="5", addBlockedBy=["2", "3", "4"])
321
+ TaskUpdate(taskId="6", addBlockedBy=["5"])
322
+
323
+ # Spawn parallel documentation agents
324
+ Task(subagent_type="general-purpose", prompt="TaskId 2: Document API endpoints...")
325
+ Task(subagent_type="general-purpose", prompt="TaskId 3: Document components...")
326
+ Task(subagent_type="general-purpose", prompt="TaskId 4: Document utilities...")
327
+ ```
328
+
329
+ ## Output Formats
330
+
331
+ | Doc Type | Format | Tool |
332
+ | ------------ | ------------------- | ---------------------- |
333
+ | API docs | OpenAPI/Swagger | YAML/JSON |
334
+ | Code docs | JSDoc/docstrings | Inline |
335
+ | READMEs | Markdown | .md files |
336
+ | Architecture | Markdown + diagrams | Mermaid/PlantUML |
337
+ | User guides | Markdown/HTML | Static site generators |
338
+
339
+ ---
340
+
341
+ ```
342
+ ─── ◈ Documentation ─────────────────────
343
+ ```
@@ -0,0 +1,370 @@
1
+ # Project Management Orchestration Patterns
2
+
3
+ ```
4
+ ┌─────────────────────────────────────────────────────────────┐
5
+ │ │
6
+ │ Complex projects, clearly decomposed. │
7
+ │ Dependencies tracked. Progress visible. Team aligned. │
8
+ │ │
9
+ └─────────────────────────────────────────────────────────────┘
10
+ ```
11
+
12
+ > **Load when**: Epic breakdown, sprint planning, progress tracking, dependency management, team coordination
13
+ > **Common patterns**: Hierarchical Decomposition, Capacity-Based Planning, Multi-Dimension Status
14
+
15
+ ## Table of Contents
16
+
17
+ 1. [Epic Breakdown](#epic-breakdown)
18
+ 2. [Sprint Planning](#sprint-planning)
19
+ 3. [Progress Tracking](#progress-tracking)
20
+ 4. [Dependency Management](#dependency-management)
21
+ 5. [Team Coordination](#team-coordination)
22
+
23
+ ---
24
+
25
+ ## Epic Breakdown
26
+
27
+ ### Pattern: Hierarchical Decomposition
28
+
29
+ ```
30
+ User Request: "Break down the authentication epic"
31
+
32
+ Phase 1: EXPLORE
33
+ └─ Explore agent: Understand requirements, existing system
34
+
35
+ Phase 2: PLAN
36
+ └─ Plan agent: Design high-level feature breakdown
37
+
38
+ Phase 3: FAN-OUT (Parallel story creation)
39
+ ├─ Agent A: User stories for login/logout
40
+ ├─ Agent B: User stories for registration
41
+ ├─ Agent C: User stories for password management
42
+ ├─ Agent D: User stories for session management
43
+ └─ Agent E: User stories for OAuth integration
44
+
45
+ Phase 4: REDUCE
46
+ └─ General-purpose agent: Organize into coherent backlog
47
+ ```
48
+
49
+ **Task Management Implementation:**
50
+
51
+ ```
52
+ # Create epic
53
+ TaskCreate(subject="Epic: User Authentication", description="Complete auth system")
54
+
55
+ # Create stories
56
+ TaskCreate(subject="Story: Login flow", description="...")
57
+ TaskCreate(subject="Story: Registration", description="...")
58
+ TaskCreate(subject="Story: Password reset", description="...")
59
+
60
+ # Set dependencies
61
+ TaskUpdate(taskId="3", addBlockedBy=["2"]) # Reset after registration
62
+ ```
63
+
64
+ ### Pattern: Vertical Slice Breakdown
65
+
66
+ ```
67
+ Phase 1: EXPLORE
68
+ └─ Explore agent: Map feature touchpoints (UI, API, DB)
69
+
70
+ Phase 2: FAN-OUT (Slice by user value)
71
+ ├─ Agent A: Define slice 1 (minimal viable feature)
72
+ ├─ Agent B: Define slice 2 (enhanced feature)
73
+ └─ Agent C: Define slice 3 (complete feature)
74
+
75
+ Phase 3: PIPELINE
76
+ └─ General-purpose agent: Estimate, prioritize, sequence
77
+ ```
78
+
79
+ ### Pattern: Spike-First Breakdown
80
+
81
+ ```
82
+ Phase 1: EXPLORE
83
+ └─ Explore agent: Identify unknowns and risks
84
+
85
+ Phase 2: FAN-OUT (Parallel spikes)
86
+ ├─ Agent A: Technical spike - feasibility
87
+ ├─ Agent B: Technical spike - performance
88
+ └─ Agent C: UX spike - user research
89
+
90
+ Phase 3: REDUCE
91
+ └─ General-purpose agent: Use spike findings to refine breakdown
92
+ ```
93
+
94
+ ---
95
+
96
+ ## Sprint Planning
97
+
98
+ ### Pattern: Capacity-Based Planning
99
+
100
+ ```
101
+ User Request: "Plan the next sprint"
102
+
103
+ Phase 1: FAN-OUT (Gather context)
104
+ ├─ Explore agent: Review backlog priority
105
+ ├─ Explore agent: Check team capacity
106
+ ├─ Explore agent: Review blockers and dependencies
107
+ └─ Explore agent: Check carryover from last sprint
108
+
109
+ Phase 2: REDUCE
110
+ └─ Plan agent: Propose sprint scope
111
+
112
+ Phase 3: FAN-OUT (Task breakdown)
113
+ ├─ Agent A: Break down story 1 into tasks
114
+ ├─ Agent B: Break down story 2 into tasks
115
+ └─ Agent C: Break down story 3 into tasks
116
+
117
+ Phase 4: PIPELINE
118
+ └─ General-purpose agent: Finalize sprint backlog
119
+ ```
120
+
121
+ **Task Structure:**
122
+
123
+ ```
124
+ # Sprint-level task
125
+ TaskCreate(subject="Sprint 14: Auth Implementation", description="...")
126
+
127
+ # Stories within sprint
128
+ TaskCreate(subject="Login API endpoint", description="...")
129
+ TaskCreate(subject="Login UI component", description="...")
130
+ TaskUpdate(taskId="2", addBlockedBy=["1"]) # UI needs API first
131
+
132
+ # Sub-tasks
133
+ TaskCreate(subject="Write login validation", description="...")
134
+ TaskCreate(subject="Add rate limiting", description="...")
135
+ ```
136
+
137
+ ### Pattern: Risk-Adjusted Planning
138
+
139
+ ```
140
+ Phase 1: FAN-OUT
141
+ ├─ Agent A: Identify technical risks
142
+ ├─ Agent B: Identify dependency risks
143
+ └─ Agent C: Identify scope risks
144
+
145
+ Phase 2: REDUCE
146
+ └─ Plan agent: Adjust estimates with risk buffer
147
+
148
+ Phase 3: PIPELINE
149
+ └─ General-purpose agent: Create contingency tasks
150
+ ```
151
+
152
+ ---
153
+
154
+ ## Progress Tracking
155
+
156
+ ### Pattern: Multi-Dimension Status
157
+
158
+ ```
159
+ User Request: "What's the project status?"
160
+
161
+ Phase 1: FAN-OUT (Parallel status gathering)
162
+ ├─ Agent A: Task completion status (from TaskList)
163
+ ├─ Agent B: Blocker analysis
164
+ ├─ Agent C: Timeline vs plan
165
+ ├─ Agent D: Quality metrics
166
+ └─ Agent E: Risk status
167
+
168
+ Phase 2: REDUCE
169
+ └─ General-purpose agent: Executive status summary
170
+ ```
171
+
172
+ **Using TaskList:**
173
+
174
+ ```
175
+ # Get current state
176
+ TaskList() # Returns all tasks with status
177
+
178
+ # Update progress
179
+ TaskUpdate(taskId="5", addComment={
180
+ author: "agent-id",
181
+ content: "50% complete, blocked on API review"
182
+ })
183
+
184
+ # Mark complete
185
+ TaskUpdate(taskId="5", status="resolved")
186
+ ```
187
+
188
+ ### Pattern: Burndown Tracking
189
+
190
+ ```
191
+ Phase 1: EXPLORE
192
+ └─ Explore agent: Calculate completed vs remaining work
193
+
194
+ Phase 2: PIPELINE
195
+ ├─ General-purpose agent: Project completion trajectory
196
+ ├─ General-purpose agent: Identify velocity trends
197
+ └─ General-purpose agent: Flag at-risk items
198
+
199
+ Phase 3: REDUCE
200
+ └─ General-purpose agent: Burndown report
201
+ ```
202
+
203
+ ### Pattern: Blocker Resolution
204
+
205
+ ```
206
+ Phase 1: EXPLORE
207
+ └─ Explore agent: Identify all blocked tasks
208
+
209
+ Phase 2: FAN-OUT (Parallel resolution paths)
210
+ ├─ Agent A: Investigate blocker 1
211
+ ├─ Agent B: Investigate blocker 2
212
+ └─ Agent C: Investigate blocker 3
213
+
214
+ Phase 3: REDUCE
215
+ └─ General-purpose agent: Resolution plan, escalation needs
216
+ ```
217
+
218
+ ---
219
+
220
+ ## Dependency Management
221
+
222
+ ### Pattern: Dependency Graph Construction
223
+
224
+ ```
225
+ User Request: "Map project dependencies"
226
+
227
+ Phase 1: EXPLORE
228
+ └─ Explore agent: List all tasks and their relationships
229
+
230
+ Phase 2: FAN-OUT
231
+ ├─ Agent A: Map technical dependencies
232
+ ├─ Agent B: Map team/resource dependencies
233
+ └─ Agent C: Map external dependencies
234
+
235
+ Phase 3: REDUCE
236
+ └─ General-purpose agent: Dependency graph, critical path
237
+ ```
238
+
239
+ **Implementation:**
240
+
241
+ ```
242
+ # Create dependency chain
243
+ TaskCreate(subject="Database schema", description="...")
244
+ TaskCreate(subject="API models", description="...")
245
+ TaskCreate(subject="API endpoints", description="...")
246
+ TaskCreate(subject="Frontend integration", description="...")
247
+
248
+ TaskUpdate(taskId="2", addBlockedBy=["1"])
249
+ TaskUpdate(taskId="3", addBlockedBy=["2"])
250
+ TaskUpdate(taskId="4", addBlockedBy=["3"])
251
+
252
+ # Cross-team dependency
253
+ TaskCreate(subject="External API access", description="Waiting on partner")
254
+ TaskUpdate(taskId="3", addBlockedBy=["5"]) # Blocked by external
255
+ ```
256
+
257
+ ### Pattern: Critical Path Analysis
258
+
259
+ ```
260
+ Phase 1: EXPLORE
261
+ └─ Explore agent: Map all task dependencies
262
+
263
+ Phase 2: PIPELINE
264
+ ├─ General-purpose agent: Calculate path lengths
265
+ ├─ General-purpose agent: Identify critical path
266
+ └─ General-purpose agent: Find parallel opportunities
267
+
268
+ Phase 3: REDUCE
269
+ └─ General-purpose agent: Optimization recommendations
270
+ ```
271
+
272
+ ### Pattern: Dependency Resolution
273
+
274
+ ```
275
+ Phase 1: FAN-OUT
276
+ ├─ Agent A: Identify circular dependencies
277
+ ├─ Agent B: Identify unnecessary dependencies
278
+ └─ Agent C: Identify dependency bottlenecks
279
+
280
+ Phase 2: PIPELINE
281
+ └─ General-purpose agent: Restructure to unblock work
282
+ ```
283
+
284
+ ---
285
+
286
+ ## Team Coordination
287
+
288
+ ### Pattern: Work Distribution
289
+
290
+ ```
291
+ User Request: "Assign work for this sprint"
292
+
293
+ Phase 1: FAN-OUT
294
+ ├─ Explore agent: Analyze task requirements
295
+ ├─ Explore agent: Review team skills/capacity
296
+ └─ Explore agent: Check current assignments
297
+
298
+ Phase 2: REDUCE
299
+ └─ Plan agent: Optimal assignment recommendations
300
+
301
+ Phase 3: FAN-OUT (Parallel task assignment)
302
+ ├─ Agent A: Create task assignments for dev 1
303
+ ├─ Agent B: Create task assignments for dev 2
304
+ └─ Agent C: Create task assignments for dev 3
305
+ ```
306
+
307
+ ### Pattern: Handoff Coordination
308
+
309
+ ```
310
+ Phase 1: EXPLORE
311
+ └─ Explore agent: Identify tasks requiring handoffs
312
+
313
+ Phase 2: PIPELINE
314
+ ├─ General-purpose agent: Document handoff requirements
315
+ ├─ General-purpose agent: Create handoff checklist
316
+ └─ General-purpose agent: Schedule coordination points
317
+ ```
318
+
319
+ ### Pattern: Multi-Team Sync
320
+
321
+ ```
322
+ Phase 1: FAN-OUT
323
+ ├─ Agent A: Gather Team A status
324
+ ├─ Agent B: Gather Team B status
325
+ └─ Agent C: Identify cross-team dependencies
326
+
327
+ Phase 2: REDUCE
328
+ └─ General-purpose agent: Cross-team status, blockers, needs
329
+ ```
330
+
331
+ ---
332
+
333
+ ## Task Management in Practice
334
+
335
+ All project management work should use TaskCreate for proper tracking:
336
+
337
+ ```python
338
+ # Sprint planning example
339
+ TaskCreate(subject="Sprint 14 Planning", description="Plan next sprint scope...")
340
+ TaskCreate(subject="Review backlog", description="Prioritize stories...")
341
+ TaskCreate(subject="Break down Story A", description="Create implementation tasks...")
342
+ TaskCreate(subject="Break down Story B", description="Create implementation tasks...")
343
+ TaskCreate(subject="Set dependencies", description="Wire task dependencies...")
344
+ TaskCreate(subject="Assign work", description="Distribute to team...")
345
+
346
+ # Planning sequence
347
+ TaskUpdate(taskId="2", addBlockedBy=["1"])
348
+ TaskUpdate(taskId="3", addBlockedBy=["2"])
349
+ TaskUpdate(taskId="4", addBlockedBy=["2"])
350
+ TaskUpdate(taskId="5", addBlockedBy=["3", "4"])
351
+ TaskUpdate(taskId="6", addBlockedBy=["5"])
352
+
353
+ # Parallel breakdown
354
+ Task(subagent_type="general-purpose", prompt="TaskId 3: Break down Story A...")
355
+ Task(subagent_type="general-purpose", prompt="TaskId 4: Break down Story B...")
356
+ ```
357
+
358
+ ## Best Practices
359
+
360
+ 1. **Break down early** - Large tasks are hard to track
361
+ 2. **Set dependencies explicitly** - Prevents blocked work
362
+ 3. **Update status frequently** - Real-time visibility
363
+ 4. **Comment on blockers** - Context for resolution
364
+ 5. **Close completed tasks immediately** - Accurate progress
365
+
366
+ ---
367
+
368
+ ```
369
+ ─── ◈ Project Management ────────────────
370
+ ```