@codemcp/workflows-core 5.2.2 → 5.2.4

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 (21) hide show
  1. package/package.json +1 -1
  2. package/resources/workflows/adr.yaml +62 -48
  3. package/resources/workflows/big-bang-conversion.yaml +231 -172
  4. package/resources/workflows/boundary-testing.yaml +137 -95
  5. package/resources/workflows/bugfix.yaml +33 -38
  6. package/resources/workflows/business-analysis.yaml +130 -172
  7. package/resources/workflows/c4-analysis.yaml +120 -114
  8. package/resources/workflows/epcc.yaml +43 -10
  9. package/resources/workflows/game-beginner.yaml +113 -103
  10. package/resources/workflows/greenfield.yaml +61 -38
  11. package/resources/workflows/minor.yaml +51 -28
  12. package/resources/workflows/posts.yaml +41 -42
  13. package/resources/workflows/sdd-bugfix-crowd.yaml +181 -206
  14. package/resources/workflows/sdd-bugfix.yaml +168 -179
  15. package/resources/workflows/sdd-feature-crowd.yaml +357 -380
  16. package/resources/workflows/sdd-feature.yaml +162 -155
  17. package/resources/workflows/sdd-greenfield-crowd.yaml +82 -74
  18. package/resources/workflows/sdd-greenfield.yaml +153 -147
  19. package/resources/workflows/slides.yaml +29 -35
  20. package/resources/workflows/tdd.yaml +59 -48
  21. package/resources/workflows/waterfall.yaml +64 -44
package/resources/workflows/sdd-feature-crowd.yaml CHANGED
@@ -31,8 +31,7 @@ states:
31
31
  default_instructions: |
32
32
  **Team Collaboration Mode**
33
33
 
34
- You are $VIBE_ROLE working in a collaborative team on this feature development.
35
- Current phase: ANALYZE
34
+ You are `$VIBE_ROLE` working in a collaborative team on this feature development.
36
35
 
37
36
  Your team members can help you at any time through messaging.
38
37
 
@@ -43,41 +42,41 @@ states:
43
42
  role: business-analyst
44
43
  transition_reason: 'Analysis completed, moving to specification'
45
44
  additional_instructions: |
46
- **You are RESPONSIBLE for the analyze phase.**
47
-
48
- You have exclusive control during this phase:
49
- - Only you can edit the plan file
50
- - Only you can proceed to the next phase
51
-
52
- **Analysis Tasks:**
53
- 1. **For New Features**: Brief analysis focusing on:
54
- - How this feature fits into the existing system
55
- - Integration points with current functionality
56
- - Existing patterns and conventions to follow
57
-
58
- 2. **For Enhancements**: Thorough analysis of:
59
- - Current implementation and its limitations
60
- - User pain points and feedback
61
- - Performance or usability issues
62
- - Technical debt that should be addressed
63
-
64
- 3. **Context Gathering**:
65
- - Review existing codebase and architecture
66
- - Understand current user workflows
67
- - Identify constraints and dependencies
68
- - Document assumptions about the current state
69
-
70
- **Collaboration:**
45
+ **Drive the analyze phase as the RESPONSIBLE agent.**
46
+
47
+ **Your Exclusive Permissions:**
48
+ - Edit the plan file
49
+ - Proceed to the next phase
50
+
51
+ **STEP 1: Gather Context**
52
+ - Review existing codebase and architecture
53
+ - Understand current user workflows
54
+ - Identify constraints and dependencies
55
+ - Document assumptions about the current state
56
+
57
+ **STEP 2: Analyze Requirements**
58
+
59
+ For New Features:
60
+ - Identify how the feature fits into the existing system
61
+ - Map integration points with current functionality
62
+ - Document existing patterns and conventions to follow
63
+
64
+ For Enhancements:
65
+ - Review current implementation and its limitations
66
+ - Identify user pain points and feedback
67
+ - Analyze performance or usability issues
68
+ - Document technical debt that should be addressed
69
+
70
+ **STEP 3: Collaborate for Insights**
71
71
  - Use send_message to ask architect about existing architecture constraints
72
72
  - Use send_message to ask developer about current implementation details
73
- - They are available to answer your questions
73
+ - Wait for responses to inform your analysis
74
74
 
75
- **Output**: Create `$VIBE_DIR/specs/$BRANCH_NAME/current-state-analysis.md`
76
-
77
- **Before proceeding to specify phase:**
78
- 1. Use send_message_to_operator to report analysis completion
79
- 2. You remain RESPONSIBLE in specify phase (continue driving the work)
80
- 3. Only you can call proceed_to_phase
75
+ **STEP 4: Document and Transition**
76
+ - Create `$VIBE_DIR/specs/$BRANCH_NAME/current-state-analysis.md`
77
+ - Use send_message_to_operator to report analysis completion
78
+ - You remain RESPONSIBLE in the specify phase (continue driving the work)
79
+ - Call proceed_to_phase only when ready
81
80
 
82
81
  # Architect is CONSULTED during analyze phase
83
82
  - trigger: 'analysis_complete'
@@ -85,26 +84,25 @@ states:
85
84
  role: architect
86
85
  transition_reason: 'Analysis completed, transitioning to specification'
87
86
  additional_instructions: |
88
- **You are CONSULTED during the analyze phase.**
87
+ **Provide Consultation as CONSULTED Agent**
89
88
 
90
89
  Business-analyst is driving this work. You are in consultative mode.
91
90
 
92
- **Your Responsibilities:**
93
- - Monitor your messages for questions from business-analyst
94
- - Respond when asked about:
95
- * Existing architecture constraints
96
- * System integration points
97
- * Technical feasibility concerns
91
+ **Monitor and Respond:**
92
+ - Check get_my_messages for questions from business-analyst
93
+ - Answer when asked about architecture constraints
94
+ - Discuss system integration points
95
+ - Address technical feasibility concerns
98
96
 
99
- **Important Constraints:**
100
- - Do NOT edit the plan file (only business-analyst can)
101
- - Do NOT attempt to proceed to next phase
97
+ **Constraints:**
98
+ - Do NOT edit the plan file (business-analyst has exclusive control)
99
+ - Do NOT proceed to next phase
102
100
  - Wait for business-analyst to ask questions
103
101
 
104
- **How to Help:**
105
- - Use get_my_messages to check for questions
106
- - Provide clear, actionable feedback about architecture
107
- - Share knowledge about existing system patterns
102
+ **Provide Value:**
103
+ - Share clear, actionable feedback about architecture
104
+ - Document knowledge about existing system patterns
105
+ - Use send_message to proactively share relevant insights
108
106
 
109
107
  # Developer is CONSULTED during analyze phase
110
108
  - trigger: 'analysis_complete'
@@ -112,42 +110,40 @@ states:
112
110
  role: developer
113
111
  transition_reason: 'Analysis completed, transitioning to specification'
114
112
  additional_instructions: |
115
- **You are CONSULTED during the analyze phase.**
113
+ **Provide Consultation as CONSULTED Agent**
116
114
 
117
115
  Business-analyst is driving this work. You are in consultative mode.
118
116
 
119
- **Your Responsibilities:**
120
- - Monitor your messages for questions from business-analyst
121
- - Respond when asked about:
122
- * Current implementation details
123
- * Existing code patterns
124
- * Technical complexity estimates
117
+ **Monitor and Respond:**
118
+ - Check get_my_messages for questions from business-analyst
119
+ - Answer when asked about current implementation details
120
+ - Discuss existing code patterns
121
+ - Provide technical complexity estimates
125
122
 
126
- **Important Constraints:**
127
- - Do NOT edit the plan file (only business-analyst can)
128
- - Do NOT attempt to proceed to next phase
123
+ **Constraints:**
124
+ - Do NOT edit the plan file (business-analyst has exclusive control)
125
+ - Do NOT proceed to next phase
129
126
  - Wait for business-analyst to ask questions
130
127
 
131
- **How to Help:**
132
- - Use get_my_messages to check for questions
133
- - Provide insights about existing codebase
134
- - Share implementation challenges and patterns
128
+ **Provide Value:**
129
+ - Share insights about existing codebase
130
+ - Document implementation challenges and patterns
131
+ - Use send_message to proactively share relevant knowledge
135
132
 
136
133
  # Skip analysis option (all agents can use this)
137
134
  - trigger: 'skip_analysis'
138
135
  to: 'specify'
139
136
  transition_reason: 'Analysis not needed, proceeding to specification'
140
137
  additional_instructions: |
141
- Skipping analysis phase for straightforward new feature.
142
- Proceeding directly to specification using provided requirements.
138
+ Skip the analysis phase for straightforward new features.
139
+ Proceed directly to specification using provided requirements.
143
140
 
144
141
  specify:
145
142
  description: 'Create feature specification'
146
143
  default_instructions: |
147
144
  **Team Collaboration Mode**
148
145
 
149
- You are $VIBE_ROLE working in a collaborative team on this feature development.
150
- Current phase: SPECIFY
146
+ You are `$VIBE_ROLE` working in a collaborative team on this feature development.
151
147
 
152
148
  Business-analyst is responsible. Architect and developer are consulted.
153
149
 
@@ -158,48 +154,47 @@ states:
158
154
  role: business-analyst
159
155
  transition_reason: 'Specification completed, ready for clarification'
160
156
  additional_instructions: |
161
- **You are RESPONSIBLE for the specify phase.**
162
-
163
- You have exclusive control during this phase:
164
- - Only you can edit the plan file
165
- - Only you can proceed to the next phase
166
-
167
- **Specification Tasks:**
168
-
169
- 1. **Parse Requirements**: Extract key concepts from user's description
170
- - Identify: actors, actions, data, constraints
171
- - Consider existing system context (from analysis if performed)
172
- - Focus on WHAT users need and WHY, not HOW to implement
173
-
174
- 2. **Interactive Requirements Gathering**: Ask clarifying questions about:
175
- - Integration points with existing features
176
- - User impact and affected users
177
- - Data dependencies
178
- - Performance requirements
179
- - Backward compatibility concerns
180
-
181
- 3. **Handle Ambiguities**:
182
- - Make informed guesses based on context and industry standards
183
- - Only use [NEEDS CLARIFICATION: question] for critical decisions (max 3)
184
- - Prioritize: scope > security/privacy > user experience > technical details
185
-
186
- 4. **Collaboration:**
187
- - Use send_message to ask architect: "Is this technically feasible?"
188
- - Use send_message to ask developer: "How complex is this to implement?"
189
- - They will provide feedback to improve your specification
190
-
191
- **Output**: Create `$VIBE_DIR/specs/$BRANCH_NAME/spec.md` with:
192
- - User scenarios and testing
193
- - Functional requirements
194
- - Success criteria
195
- - Integration points
196
-
197
- **Before proceeding to clarify phase:**
198
- 1. Use send_message to ask architect and developer to review spec.md
199
- 2. Wait for their feedback and address concerns
200
- 3. Use send_message_to_operator: "Specification complete, moving to clarification"
201
- 4. You remain RESPONSIBLE in clarify phase
202
- 5. Only you can call proceed_to_phase
157
+ **Drive the specify phase as the RESPONSIBLE agent.**
158
+
159
+ **Your Exclusive Permissions:**
160
+ - Edit the plan file
161
+ - Proceed to the next phase
162
+
163
+ **STEP 1: Extract Requirements**
164
+ - Parse key concepts from user's description
165
+ - Identify actors, actions, data, and constraints
166
+ - Use existing system context from analysis (if performed)
167
+ - Focus on WHAT users need and WHY, not HOW to implement
168
+
169
+ **STEP 2: Gather Clarifications**
170
+ Ask questions about:
171
+ - Integration points with existing features
172
+ - User impact and affected users
173
+ - Data dependencies
174
+ - Performance requirements
175
+ - Backward compatibility concerns
176
+
177
+ **STEP 3: Resolve Ambiguities**
178
+ - Make informed guesses based on context and industry standards
179
+ - Use `[NEEDS CLARIFICATION: question]` only for critical decisions (max 3)
180
+ - Prioritize: scope > security/privacy > user experience > technical details
181
+
182
+ **STEP 4: Collaborate for Feedback**
183
+ - Use send_message to ask architect: "Is this technically feasible?"
184
+ - Use send_message to ask developer: "How complex is this to implement?"
185
+ - Wait for responses and incorporate feedback
186
+
187
+ **STEP 5: Document and Transition**
188
+ - Create `$VIBE_DIR/specs/$BRANCH_NAME/spec.md` with:
189
+ - User scenarios and testing
190
+ - Functional requirements
191
+ - Success criteria
192
+ - Integration points
193
+ - Use send_message to ask architect and developer to review spec.md
194
+ - Wait for their feedback and address concerns
195
+ - Use send_message_to_operator: "Specification complete, moving to clarification"
196
+ - You remain RESPONSIBLE in clarify phase
197
+ - Call proceed_to_phase only when ready
203
198
 
204
199
  # Architect is CONSULTED during specify phase
205
200
  - trigger: 'specification_complete'
@@ -207,23 +202,22 @@ states:
207
202
  role: architect
208
203
  transition_reason: 'Specification completed, transitioning to clarification'
209
204
  additional_instructions: |
210
- **You are CONSULTED during the specify phase.**
205
+ **Provide Consultation as CONSULTED Agent**
211
206
 
212
207
  Business-analyst is driving this work. You are in consultative mode.
213
208
 
214
- **Your Responsibilities:**
215
- - Monitor messages for review requests from business-analyst
216
- - Provide feedback on:
217
- * Technical feasibility of requirements
218
- * Architecture constraints and integration concerns
219
- * System scalability and performance implications
220
- * Technology stack compatibility
209
+ **Monitor and Provide Feedback:**
210
+ - Check get_my_messages for review requests from business-analyst
211
+ - Assess technical feasibility of requirements
212
+ - Discuss architecture constraints and integration concerns
213
+ - Analyze system scalability and performance implications
214
+ - Evaluate technology stack compatibility
221
215
 
222
- **Important Constraints:**
223
- - Do NOT edit the plan file (only business-analyst can)
224
- - Do NOT attempt to proceed to next phase
216
+ **Constraints:**
217
+ - Do NOT edit the plan file (business-analyst has exclusive control)
218
+ - Do NOT proceed to next phase
225
219
 
226
- **How to Help:**
220
+ **Provide Value:**
227
221
  - Use get_my_messages to check for review requests
228
222
  - Use send_message to provide detailed feedback
229
223
  - Ask clarifying questions if requirements are unclear
@@ -235,23 +229,22 @@ states:
235
229
  role: developer
236
230
  transition_reason: 'Specification completed, transitioning to clarification'
237
231
  additional_instructions: |
238
- **You are CONSULTED during the specify phase.**
232
+ **Provide Consultation as CONSULTED Agent**
239
233
 
240
234
  Business-analyst is driving this work. You are in consultative mode.
241
235
 
242
- **Your Responsibilities:**
243
- - Monitor messages for review requests from business-analyst
244
- - Provide feedback on:
245
- * Implementation complexity and effort
246
- * Technical challenges and risks
247
- * Compatibility with existing codebase
248
- * Testing requirements
236
+ **Monitor and Provide Feedback:**
237
+ - Check get_my_messages for review requests from business-analyst
238
+ - Assess implementation complexity and effort
239
+ - Identify technical challenges and risks
240
+ - Evaluate compatibility with existing codebase
241
+ - Discuss testing requirements
249
242
 
250
- **Important Constraints:**
251
- - Do NOT edit the plan file (only business-analyst can)
252
- - Do NOT attempt to proceed to next phase
243
+ **Constraints:**
244
+ - Do NOT edit the plan file (business-analyst has exclusive control)
245
+ - Do NOT proceed to next phase
253
246
 
254
- **How to Help:**
247
+ **Provide Value:**
255
248
  - Use get_my_messages to check for review requests
256
249
  - Use send_message to provide honest complexity estimates
257
250
  - Highlight potential implementation challenges
@@ -263,16 +256,17 @@ states:
263
256
  role: business-analyst
264
257
  transition_reason: 'Specification needs user clarification'
265
258
  additional_instructions: |
266
- Specification has unresolved clarifications. Present structured questions to the user,
267
- wait for their responses, then update the specification accordingly.
259
+ Resolve unresolved clarifications by:
260
+ - Present structured questions to the user
261
+ - Wait for their responses
262
+ - Update the specification accordingly
268
263
 
269
264
  clarify:
270
265
  description: 'Review and clarify specification details'
271
266
  default_instructions: |
272
267
  **Team Collaboration Mode**
273
268
 
274
- You are $VIBE_ROLE working in a collaborative team on this feature development.
275
- Current phase: CLARIFY
269
+ You are `$VIBE_ROLE` working in a collaborative team on this feature development.
276
270
 
277
271
  Business-analyst is responsible. Architect is consulted.
278
272
 
@@ -283,39 +277,36 @@ states:
283
277
  role: business-analyst
284
278
  transition_reason: 'All clarifications resolved, handing off to architect'
285
279
  additional_instructions: |
286
- **You are RESPONSIBLE for the clarify phase.**
287
-
288
- You have exclusive control during this phase:
289
- - Only you can edit the plan file
290
- - Only you can proceed to the next phase
291
-
292
- **Clarification Tasks:**
293
-
294
- 1. **Specification Review**:
295
- - Check for any remaining [NEEDS CLARIFICATION] markers
296
- - Verify all functional requirements are testable
297
- - Ensure success criteria are measurable
298
- - Validate user scenarios are complete
299
-
300
- 2. **Handle Remaining Clarifications**:
301
- If [NEEDS CLARIFICATION] markers exist:
302
- - Extract all markers from the spec (max 3)
303
- - For each, present structured questions with options
304
- - Wait for user responses
305
- - Update specification with chosen answers
306
-
307
- 3. **Final Validation**:
308
- - Ensure no implementation details leaked in
309
- - Verify requirements align with existing system
310
- - Use send_message to ask architect for final spec review
311
-
312
- **Handoff to Architect:**
313
-
314
- Before proceeding to plan phase:
315
- 1. Use send_message to architect: "Specification is complete and clarified. Please take the lead for the plan phase. Review: $VIBE_DIR/specs/$BRANCH_NAME/spec.md"
316
- 2. Use send_message to developer: "Specification finalized, architect will create the plan next"
317
- 3. Use send_message_to_operator: "Clarification complete, handing off to architect for planning"
318
- 4. Call proceed_to_phase - you transition to CONSULTED role in plan phase
280
+ **Drive the clarify phase as the RESPONSIBLE agent.**
281
+
282
+ **Your Exclusive Permissions:**
283
+ - Edit the plan file
284
+ - Proceed to the next phase
285
+
286
+ **STEP 1: Review Specification**
287
+ - Check for any remaining `[NEEDS CLARIFICATION]` markers
288
+ - Verify all functional requirements are testable
289
+ - Ensure success criteria are measurable
290
+ - Validate user scenarios are complete
291
+
292
+ **STEP 2: Resolve Remaining Clarifications**
293
+ If `[NEEDS CLARIFICATION]` markers exist:
294
+ - Extract all markers from the spec (max 3)
295
+ - Present structured questions with options to the user
296
+ - Wait for user responses
297
+ - Update specification with chosen answers
298
+
299
+ **STEP 3: Validate and Prepare Handoff**
300
+ - Ensure no implementation details leaked in
301
+ - Verify requirements align with existing system
302
+ - Use send_message to ask architect for final spec review
303
+
304
+ **STEP 4: Hand Off to Architect**
305
+ - Use send_message to architect: "Specification is complete and clarified. Please take the lead for the plan phase. Review: `$VIBE_DIR/specs/$BRANCH_NAME/spec.md`"
306
+ - Use send_message to developer: "Specification finalized, architect will create the plan next"
307
+ - Use send_message_to_operator: "Clarification complete, handing off to architect for planning"
308
+ - You transition to CONSULTED role in plan phase
309
+ - Call proceed_to_phase only when ready
319
310
 
320
311
  # Architect is CONSULTED during clarify phase
321
312
  - trigger: 'clarification_complete'
@@ -323,21 +314,21 @@ states:
323
314
  role: architect
324
315
  transition_reason: 'Clarifications resolved, preparing to take lead in plan phase'
325
316
  additional_instructions: |
326
- **You are CONSULTED during the clarify phase.**
317
+ **Provide Consultation as CONSULTED Agent**
327
318
 
328
319
  Business-analyst is finalizing clarifications. You are in consultative mode.
329
320
 
330
- **Your Responsibilities:**
331
- - Monitor messages for final review requests
321
+ **Monitor and Provide Feedback:**
322
+ - Check get_my_messages for final review requests
332
323
  - Validate specification is ready for technical planning
333
324
  - Provide feedback on any remaining technical concerns
334
325
 
335
- **Important Constraints:**
336
- - Do NOT edit the plan file (only business-analyst can)
337
- - Do NOT attempt to proceed to next phase
326
+ **Constraints:**
327
+ - Do NOT edit the plan file (business-analyst has exclusive control)
328
+ - Do NOT proceed to next phase
338
329
 
339
- **Handoff Notice:**
340
- - When business-analyst completes clarify phase, YOU become RESPONSIBLE
330
+ **Prepare for Your Leadership Role:**
331
+ When business-analyst completes clarify phase, YOU become RESPONSIBLE:
341
332
  - You will take the lead in the plan phase
342
333
  - Prepare to design the system architecture and create implementation plan
343
334
 
@@ -347,19 +338,19 @@ states:
347
338
  role: developer
348
339
  transition_reason: 'Clarifications resolved, architect taking lead for planning'
349
340
  additional_instructions: |
350
- **You are INFORMED during the clarify phase.**
341
+ **Monitor Progress as INFORMED Agent**
351
342
 
352
343
  Business-analyst is finalizing clarifications. You are in monitoring mode.
353
344
 
354
- **Your Responsibilities:**
355
- - Stay aware of specification updates
356
- - Prepare to be consulted during planning phase
345
+ **Stay Aware:**
346
+ - Monitor specification updates
347
+ - Prepare for consultation during planning phase
357
348
  - No active work required in this phase
358
349
 
359
- **Next Phase:**
350
+ **Get Ready for Next Phase:**
360
351
  - Architect will take the lead in plan phase
361
352
  - You will be CONSULTED during planning
362
- - Be ready to provide implementation feedback when architect asks
353
+ - Prepare to provide implementation feedback when architect asks
363
354
 
364
355
  # For needs_user_input loop
365
356
  - trigger: 'needs_user_input'
@@ -367,16 +358,17 @@ states:
367
358
  role: business-analyst
368
359
  transition_reason: 'Waiting for user responses to clarification questions'
369
360
  additional_instructions: |
370
- Waiting for user responses to clarification questions. Present the questions clearly
371
- and wait for user input before proceeding.
361
+ Resolve user input needs by:
362
+ - Present clarification questions clearly
363
+ - Wait for user input
364
+ - Process responses before proceeding
372
365
 
373
366
  plan:
374
367
  description: 'Generate implementation plan with constitutional compliance'
375
368
  default_instructions: |
376
369
  **Team Collaboration Mode**
377
370
 
378
- You are $VIBE_ROLE working in a collaborative team on this feature development.
379
- Current phase: PLAN
371
+ You are `$VIBE_ROLE` working in a collaborative team on this feature development.
380
372
 
381
373
  Architect is responsible. Business-analyst and developer are consulted.
382
374
 
@@ -387,21 +379,21 @@ states:
387
379
  role: business-analyst
388
380
  transition_reason: 'Plan completed, architect moving to tasks'
389
381
  additional_instructions: |
390
- **You are CONSULTED during the plan phase.**
382
+ **Provide Consultation as CONSULTED Agent**
391
383
 
392
384
  Architect is driving technical planning. You are in consultative mode.
393
385
 
394
- **Your Responsibilities:**
395
- - Monitor messages for questions from architect
386
+ **Monitor and Validate:**
387
+ - Check get_my_messages for questions from architect
396
388
  - Validate plan aligns with specification requirements
397
- - Clarify any requirements that are unclear
389
+ - Clarify any ambiguous requirements
398
390
  - Approve or suggest adjustments to technical approach
399
391
 
400
- **Important Constraints:**
401
- - Do NOT edit the plan file (only architect can)
402
- - Do NOT attempt to proceed to next phase
392
+ **Constraints:**
393
+ - Do NOT edit the plan file (architect has exclusive control)
394
+ - Do NOT proceed to next phase
403
395
 
404
- **How to Help:**
396
+ **Provide Value:**
405
397
  - Use get_my_messages to check for architect's questions
406
398
  - Use send_message to validate alignment with spec
407
399
  - Raise concerns if plan doesn't meet business requirements
@@ -413,41 +405,39 @@ states:
413
405
  role: architect
414
406
  transition_reason: 'Implementation plan completed, moving to task breakdown'
415
407
  additional_instructions: |
416
- **You are RESPONSIBLE for the plan phase.**
417
-
418
- You have exclusive control during this phase:
419
- - Only you can edit the plan file
420
- - Only you can proceed to the next phase
421
-
422
- **Planning Tasks:**
423
-
424
- 1. **Load Context**:
425
- - Read specification: `$VIBE_DIR/specs/$BRANCH_NAME/spec.md`
426
- - Read analysis: `$VIBE_DIR/specs/$BRANCH_NAME/current-state-analysis.md` (if exists)
427
- - Review existing project patterns and conventions
428
-
429
- 2. **Collaborate on Technical Approach**:
430
- - Use send_message to business-analyst: "Does this approach align with requirements?"
431
- - Use send_message to developer: "Is this implementation strategy sound?"
432
- - Wait for feedback and incorporate it
433
-
434
- 3. **Technical Context Analysis**:
435
- - Identify integration with existing system
436
- - Map dependencies and integration points
437
- - Choose appropriate technology stack
438
- - Mark unknowns for research
439
-
440
- 4. **Create Plan**: Document in `$VIBE_DIR/specs/$BRANCH_NAME/plan.md`:
441
- - High-level architecture
442
- - Technology decisions
443
- - Integration strategy
444
- - Implementation phases
445
-
446
- **You remain RESPONSIBLE in tasks phase** (continue driving technical work)
447
-
448
- **Before proceeding:**
449
- 1. Use send_message_to_operator: "Planning complete, moving to task breakdown"
450
- 2. Only you can call proceed_to_phase
408
+ **Drive the plan phase as the RESPONSIBLE agent.**
409
+
410
+ **Your Exclusive Permissions:**
411
+ - Edit the plan file
412
+ - Proceed to the next phase
413
+
414
+ **STEP 1: Load Context**
415
+ - Read specification: `$VIBE_DIR/specs/$BRANCH_NAME/spec.md`
416
+ - Read analysis: `$VIBE_DIR/specs/$BRANCH_NAME/current-state-analysis.md` (if exists)
417
+ - Review existing project patterns and conventions
418
+
419
+ **STEP 2: Collaborate on Technical Approach**
420
+ - Use send_message to business-analyst: "Does this approach align with requirements?"
421
+ - Use send_message to developer: "Is this implementation strategy sound?"
422
+ - Wait for feedback and incorporate it
423
+
424
+ **STEP 3: Analyze Technical Context**
425
+ - Identify integration with existing system
426
+ - Map dependencies and integration points
427
+ - Choose appropriate technology stack
428
+ - Mark unknowns for research
429
+
430
+ **STEP 4: Create Plan**
431
+ Document in `$VIBE_DIR/specs/$BRANCH_NAME/plan.md`:
432
+ - High-level architecture
433
+ - Technology decisions
434
+ - Integration strategy
435
+ - Implementation phases
436
+
437
+ **STEP 5: Transition to Tasks**
438
+ - You remain RESPONSIBLE in tasks phase (continue driving technical work)
439
+ - Use send_message_to_operator: "Planning complete, moving to task breakdown"
440
+ - Call proceed_to_phase only when ready
451
441
 
452
442
  # Developer is CONSULTED during plan phase
453
443
  - trigger: 'plan_complete'
@@ -455,23 +445,22 @@ states:
455
445
  role: developer
456
446
  transition_reason: 'Plan completed, architect moving to tasks'
457
447
  additional_instructions: |
458
- **You are CONSULTED during the plan phase.**
448
+ **Provide Consultation as CONSULTED Agent**
459
449
 
460
450
  Architect is driving technical planning. You are in consultative mode.
461
451
 
462
- **Your Responsibilities:**
463
- - Monitor messages for questions from architect
464
- - Provide feedback on:
465
- * Implementation feasibility and complexity
466
- * Existing code patterns and conventions
467
- * Potential technical challenges
468
- * Testing requirements and strategies
452
+ **Monitor and Provide Feedback:**
453
+ - Check get_my_messages for questions from architect
454
+ - Assess implementation feasibility and complexity
455
+ - Discuss existing code patterns and conventions
456
+ - Identify potential technical challenges
457
+ - Suggest testing requirements and strategies
469
458
 
470
- **Important Constraints:**
471
- - Do NOT edit the plan file (only architect can)
472
- - Do NOT attempt to proceed to next phase
459
+ **Constraints:**
460
+ - Do NOT edit the plan file (architect has exclusive control)
461
+ - Do NOT proceed to next phase
473
462
 
474
- **How to Help:**
463
+ **Provide Value:**
475
464
  - Use get_my_messages to check for architect's questions
476
465
  - Use send_message to provide honest implementation feedback
477
466
  - Suggest alternative approaches if needed
@@ -483,16 +472,16 @@ states:
483
472
  role: architect
484
473
  transition_reason: 'Plan conflicts with existing architecture, needs revision'
485
474
  additional_instructions: |
486
- Implementation plan conflicts with existing architecture or principles.
487
- Review and revise the approach to ensure proper integration.
475
+ Resolve architectural conflicts by:
476
+ - Review how plan conflicts with existing architecture or principles
477
+ - Revise the approach to ensure proper integration
488
478
 
489
479
  tasks:
490
480
  description: 'Generate actionable, dependency-ordered tasks'
491
481
  default_instructions: |
492
482
  **Team Collaboration Mode**
493
483
 
494
- You are $VIBE_ROLE working in a collaborative team on this feature development.
495
- Current phase: TASKS
484
+ You are `$VIBE_ROLE` working in a collaborative team on this feature development.
496
485
 
497
486
  Architect is responsible. Business-analyst is informed. Developer is consulted.
498
487
 
@@ -503,19 +492,19 @@ states:
503
492
  role: business-analyst
504
493
  transition_reason: 'Tasks generated, developer taking lead for implementation'
505
494
  additional_instructions: |
506
- **You are INFORMED during the tasks phase.**
495
+ **Monitor Progress as INFORMED Agent**
507
496
 
508
497
  Architect is creating the task breakdown. You are in monitoring mode.
509
498
 
510
- **Your Responsibilities:**
511
- - Stay aware of task structure
512
- - Be ready to clarify requirements during implementation
499
+ **Stay Aware:**
500
+ - Monitor task structure
501
+ - Prepare for consultation during implementation
513
502
  - No active work required in this phase
514
503
 
515
- **Next Phase:**
504
+ **Get Ready for Next Phase:**
516
505
  - Developer will take the lead in implement phase
517
506
  - You will be CONSULTED during implementation
518
- - Be ready to clarify requirements when developer asks
507
+ - Prepare to clarify requirements when developer asks
519
508
 
520
509
  # Architect is RESPONSIBLE for tasks phase
521
510
  - trigger: 'tasks_generated'
@@ -523,43 +512,41 @@ states:
523
512
  role: architect
524
513
  transition_reason: 'Tasks generated, handing off to developer'
525
514
  additional_instructions: |
526
- **You are RESPONSIBLE for the tasks phase.**
527
-
528
- You have exclusive control during this phase:
529
- - Only you can edit the plan file
530
- - Only you can proceed to the next phase
531
-
532
- **Task Generation:**
533
-
534
- 1. **Load Design Documents**:
535
- - Required: `$VIBE_DIR/specs/$BRANCH_NAME/plan.md`, `$VIBE_DIR/specs/$BRANCH_NAME/spec.md`
536
- - Optional: `$VIBE_DIR/specs/$BRANCH_NAME/technology-research.md`
537
-
538
- 2. **Extract User Stories**: From spec.md with priorities (P1, P2, P3...)
539
-
540
- 3. **Generate Task Breakdown**:
541
- - Setup Phase: Integration and shared infrastructure
542
- - Foundational Phase: Prerequisites for the feature
543
- - User Story Phases (P1, P2, P3...): One phase per story
544
- - Mark parallelizable tasks with [P]
545
-
546
- 4. **Collaborate with Developer**:
547
- - Use send_message to developer: "Please review task breakdown for implementability"
548
- - Wait for feedback and adjust
549
-
550
- 5. **Create Documents**:
551
- - `$VIBE_DIR/specs/$BRANCH_NAME/data-model.md`
552
- - `$VIBE_DIR/specs/$BRANCH_NAME/contracts/` (API contracts)
553
- - `$VIBE_DIR/specs/$BRANCH_NAME/quickstart.md`
554
- - `$VIBE_DIR/specs/$BRANCH_NAME/tasks.md`
555
-
556
- **Handoff to Developer:**
557
-
558
- Before proceeding to implement phase:
559
- 1. Use send_message to developer: "Task breakdown complete. Please take the lead for implementation phase. See: $VIBE_DIR/specs/$BRANCH_NAME/tasks.md"
560
- 2. Use send_message to business-analyst: "Implementation will begin, you'll be consulted for requirement clarifications"
561
- 3. Use send_message_to_operator: "Tasks ready, handing off to developer"
562
- 4. Call proceed_to_phase - you transition to CONSULTED role in implement phase
515
+ **Drive the tasks phase as the RESPONSIBLE agent.**
516
+
517
+ **Your Exclusive Permissions:**
518
+ - Edit the plan file
519
+ - Proceed to the next phase
520
+
521
+ **STEP 1: Load Design Documents**
522
+ - Required: `$VIBE_DIR/specs/$BRANCH_NAME/plan.md`, `$VIBE_DIR/specs/$BRANCH_NAME/spec.md`
523
+ - Optional: `$VIBE_DIR/specs/$BRANCH_NAME/technology-research.md`
524
+
525
+ **STEP 2: Extract User Stories**
526
+ - From spec.md with priorities (P1, P2, P3...)
527
+
528
+ **STEP 3: Generate Task Breakdown**
529
+ - Setup Phase: Integration and shared infrastructure
530
+ - Foundational Phase: Prerequisites for the feature
531
+ - User Story Phases (P1, P2, P3...): One phase per story
532
+ - Mark parallelizable tasks with `[P]`
533
+
534
+ **STEP 4: Collaborate with Developer**
535
+ - Use send_message to developer: "Please review task breakdown for implementability"
536
+ - Wait for feedback and adjust
537
+
538
+ **STEP 5: Create Documentation**
539
+ - `$VIBE_DIR/specs/$BRANCH_NAME/data-model.md`
540
+ - `$VIBE_DIR/specs/$BRANCH_NAME/contracts/` (API contracts)
541
+ - `$VIBE_DIR/specs/$BRANCH_NAME/quickstart.md`
542
+ - `$VIBE_DIR/specs/$BRANCH_NAME/tasks.md`
543
+
544
+ **STEP 6: Hand Off to Developer**
545
+ - Use send_message to developer: "Task breakdown complete. Please take the lead for implementation phase. See: `$VIBE_DIR/specs/$BRANCH_NAME/tasks.md`"
546
+ - Use send_message to business-analyst: "Implementation will begin, you'll be consulted for requirement clarifications"
547
+ - Use send_message_to_operator: "Tasks ready, handing off to developer"
548
+ - You transition to CONSULTED role in implement phase
549
+ - Call proceed_to_phase only when ready
563
550
 
564
551
  # Developer is CONSULTED during tasks phase
565
552
  - trigger: 'tasks_generated'
@@ -567,24 +554,23 @@ states:
567
554
  role: developer
568
555
  transition_reason: 'Tasks generated, preparing to take lead for implementation'
569
556
  additional_instructions: |
570
- **You are CONSULTED during the tasks phase.**
557
+ **Provide Consultation as CONSULTED Agent**
571
558
 
572
559
  Architect is creating the task breakdown. You are in consultative mode.
573
560
 
574
- **Your Responsibilities:**
575
- - Monitor messages for review requests from architect
576
- - Provide feedback on:
577
- * Task granularity and completeness
578
- * Implementation order and dependencies
579
- * Complexity estimates
580
- * Testing approach
561
+ **Monitor and Provide Feedback:**
562
+ - Check get_my_messages for review requests from architect
563
+ - Assess task granularity and completeness
564
+ - Discuss implementation order and dependencies
565
+ - Provide complexity estimates
566
+ - Suggest testing approach
581
567
 
582
- **Important Constraints:**
583
- - Do NOT edit the plan file (only architect can)
584
- - Do NOT attempt to proceed to next phase
568
+ **Constraints:**
569
+ - Do NOT edit the plan file (architect has exclusive control)
570
+ - Do NOT proceed to next phase
585
571
 
586
- **Handoff Notice:**
587
- - When architect completes tasks phase, YOU become RESPONSIBLE
572
+ **Prepare for Your Leadership Role:**
573
+ When architect completes tasks phase, YOU become RESPONSIBLE:
588
574
  - You will take the lead in the implement phase
589
575
  - Review the tasks.md and prepare to begin implementation
590
576
 
@@ -593,8 +579,7 @@ states:
593
579
  default_instructions: |
594
580
  **Team Collaboration Mode**
595
581
 
596
- You are $VIBE_ROLE working in a collaborative team on this feature development.
597
- Current phase: IMPLEMENT
582
+ You are `$VIBE_ROLE` working in a collaborative team on this feature development.
598
583
 
599
584
  Developer is responsible. Architect and business-analyst are consulted.
600
585
 
@@ -605,23 +590,22 @@ states:
605
590
  role: business-analyst
606
591
  transition_reason: 'Implementation complete'
607
592
  additional_instructions: |
608
- **You are CONSULTED during the implement phase.**
593
+ **Provide Consultation as CONSULTED Agent**
609
594
 
610
595
  Developer is driving implementation. You are in consultative mode.
611
596
 
612
- **Your Responsibilities:**
613
- - Monitor messages for questions from developer
614
- - Provide clarification on:
615
- * Requirements interpretation
616
- * User story acceptance criteria
617
- * Business rules and constraints
618
- * Success criteria validation
597
+ **Monitor and Clarify:**
598
+ - Check get_my_messages for questions from developer
599
+ - Clarify requirements interpretation
600
+ - Explain user story acceptance criteria
601
+ - Document business rules and constraints
602
+ - Validate success criteria
619
603
 
620
- **Important Constraints:**
621
- - Do NOT edit the plan file (only developer can)
622
- - Do NOT attempt to proceed to next phase
604
+ **Constraints:**
605
+ - Do NOT edit the plan file (developer has exclusive control)
606
+ - Do NOT proceed to next phase
623
607
 
624
- **How to Help:**
608
+ **Provide Value:**
625
609
  - Use get_my_messages to check for developer's questions
626
610
  - Use send_message to clarify requirements quickly
627
611
  - Validate implementation against specification when asked
@@ -633,23 +617,22 @@ states:
633
617
  role: architect
634
618
  transition_reason: 'Implementation complete'
635
619
  additional_instructions: |
636
- **You are CONSULTED during the implement phase.**
620
+ **Provide Consultation as CONSULTED Agent**
637
621
 
638
622
  Developer is driving implementation. You are in consultative mode.
639
623
 
640
- **Your Responsibilities:**
641
- - Monitor messages for questions from developer
642
- - Provide guidance on:
643
- * Architecture decisions and patterns
644
- * Design patterns and best practices
645
- * Integration approaches
646
- * Technical trade-offs
624
+ **Monitor and Provide Guidance:**
625
+ - Check get_my_messages for questions from developer
626
+ - Guide architecture decisions and patterns
627
+ - Discuss design patterns and best practices
628
+ - Address integration approaches
629
+ - Clarify technical trade-offs
647
630
 
648
- **Important Constraints:**
649
- - Do NOT edit the plan file (only developer can)
650
- - Do NOT attempt to proceed to next phase
631
+ **Constraints:**
632
+ - Do NOT edit the plan file (developer has exclusive control)
633
+ - Do NOT proceed to next phase
651
634
 
652
- **How to Help:**
635
+ **Provide Value:**
653
636
  - Use get_my_messages to check for developer's questions
654
637
  - Use send_message to provide architecture guidance
655
638
  - Review code against architecture plan when asked
@@ -661,44 +644,41 @@ states:
661
644
  role: developer
662
645
  transition_reason: 'Implementation complete, feature ready'
663
646
  additional_instructions: |
664
- **You are RESPONSIBLE for the implement phase.**
665
-
666
- You have exclusive control during this phase:
667
- - Only you can edit the plan file
668
- - Only you can proceed (mark complete)
669
-
670
- **Implementation Tasks:**
671
-
672
- 1. **Follow Task Breakdown**: Execute tasks from `$VIBE_DIR/specs/$BRANCH_NAME/tasks.md`
673
- - Work through tasks in order
674
- - Mark completed tasks with [x] in plan file
675
- - Focus on one user story at a time
676
-
677
- 2. **Collaborate When Needed:**
678
- - Use send_message to architect when design questions arise
679
- - Use send_message to business-analyst when requirements unclear
680
- - They are available to unblock you
681
-
682
- 3. **Quality Standards:**
683
- - Follow existing code patterns
684
- - Write tests for new functionality
685
- - Ensure integration with existing system
686
- - Handle errors appropriately
687
-
688
- 4. **Progress Tracking:**
689
- - Update plan file with completed tasks
690
- - Document any deviations or decisions
691
- - Keep implementation aligned with specification
692
-
693
- **Final Validation:**
694
-
695
- Before marking complete:
696
- 1. Use send_message to architect: "Please review implementation against architecture plan"
697
- 2. Use send_message to business-analyst: "Please validate implementation meets specification"
698
- 3. Wait for their reviews and address any concerns
699
- 4. Run all tests and ensure they pass
700
- 5. Use send_message_to_operator: "Implementation complete and reviewed by team"
701
- 6. This is a terminal state - feature is complete
647
+ **Drive the implement phase as the RESPONSIBLE agent.**
648
+
649
+ **Your Exclusive Permissions:**
650
+ - Edit the plan file
651
+ - Mark work as complete
652
+
653
+ **STEP 1: Execute Tasks**
654
+ - Follow task breakdown from `$VIBE_DIR/specs/$BRANCH_NAME/tasks.md`
655
+ - Work through tasks in order
656
+ - Mark completed tasks with `[x]` in plan file
657
+ - Focus on one user story at a time
658
+
659
+ **STEP 2: Collaborate When Needed**
660
+ - Use send_message to architect when design questions arise
661
+ - Use send_message to business-analyst when requirements unclear
662
+ - Wait for team responses to unblock your work
663
+
664
+ **STEP 3: Maintain Quality Standards**
665
+ - Follow existing code patterns
666
+ - Write tests for new functionality
667
+ - Ensure integration with existing system
668
+ - Handle errors appropriately
669
+
670
+ **STEP 4: Track Progress**
671
+ - Update plan file with completed tasks
672
+ - Document any deviations or decisions
673
+ - Keep implementation aligned with specification
674
+
675
+ **STEP 5: Final Validation Before Completion**
676
+ - Use send_message to architect: "Please review implementation against architecture plan"
677
+ - Use send_message to business-analyst: "Please validate implementation meets specification"
678
+ - Wait for their reviews and address any concerns
679
+ - Run all tests and ensure they pass
680
+ - Use send_message_to_operator: "Implementation complete and reviewed by team"
681
+ - This is a terminal state - feature is complete
702
682
 
703
683
  # Implementation blocked - return to plan phase
704
684
  - trigger: 'implementation_blocked'
@@ -706,12 +686,11 @@ states:
706
686
  role: developer
707
687
  transition_reason: 'Implementation blocked, need to revise plan'
708
688
  additional_instructions: |
709
- Implementation is blocked by technical issues. Notify the team:
710
-
711
- 1. Use send_message to architect: "Implementation blocked: [explain issue]. Need to revise plan."
712
- 2. Use send_message to business-analyst: "Implementation blocked, may need requirement changes: [explain]"
713
- 3. Use send_message_to_operator: "Implementation blocked, returning to plan phase"
714
- 4. Call proceed_to_phase - architect will take lead again in plan phase
689
+ Resolve blocking issues by:
690
+ - Use send_message to architect: "Implementation blocked: [explain issue]. Need to revise plan."
691
+ - Use send_message to business-analyst: "Implementation blocked, may need requirement changes: [explain]"
692
+ - Use send_message_to_operator: "Implementation blocked, returning to plan phase"
693
+ - Call proceed_to_phase - architect will take lead again in plan phase
715
694
 
716
695
  # Integration issues - return to analyze
717
696
  - trigger: 'integration_issues'
@@ -719,12 +698,11 @@ states:
719
698
  role: developer
720
699
  transition_reason: 'Integration issues require deeper system analysis'
721
700
  additional_instructions: |
722
- Significant integration issues discovered. Notify the team:
723
-
724
- 1. Use send_message to business-analyst: "Integration issues found: [explain]. Need deeper analysis."
725
- 2. Use send_message to architect: "Integration problems require re-analysis: [explain]"
726
- 3. Use send_message_to_operator: "Integration issues, returning to analyze phase"
727
- 4. Call proceed_to_phase - business-analyst will take lead in analyze phase
701
+ Resolve integration issues by:
702
+ - Use send_message to business-analyst: "Integration issues found: [explain]. Need deeper analysis."
703
+ - Use send_message to architect: "Integration problems require re-analysis: [explain]"
704
+ - Use send_message_to_operator: "Integration issues, returning to analyze phase"
705
+ - Call proceed_to_phase - business-analyst will take lead in analyze phase
728
706
 
729
707
  # Global transitions available from any state
730
708
  global_transitions:
@@ -732,5 +710,4 @@ global_transitions:
732
710
  to: 'analyze'
733
711
  transition_reason: 'Feature abandoned, restart from beginning'
734
712
  additional_instructions: |
735
- Feature development abandoned. If you want to restart, begin again with
736
- analyzing the requirements and current state.
713
+ If you want to restart, begin again by analyzing the requirements and current state.