vibe-fabric 0.3.3 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (53) hide show
  1. package/dist/cli/commands/analyze.d.ts +33 -0
  2. package/dist/cli/commands/analyze.d.ts.map +1 -0
  3. package/dist/cli/commands/analyze.js +243 -0
  4. package/dist/cli/commands/analyze.js.map +1 -0
  5. package/dist/cli/commands/config/get.d.ts +9 -0
  6. package/dist/cli/commands/config/get.d.ts.map +1 -0
  7. package/dist/cli/commands/config/get.js +69 -0
  8. package/dist/cli/commands/config/get.js.map +1 -0
  9. package/dist/cli/commands/config/list.d.ts +24 -0
  10. package/dist/cli/commands/config/list.d.ts.map +1 -0
  11. package/dist/cli/commands/config/list.js +146 -0
  12. package/dist/cli/commands/config/list.js.map +1 -0
  13. package/dist/cli/commands/config/set.d.ts +14 -0
  14. package/dist/cli/commands/config/set.d.ts.map +1 -0
  15. package/dist/cli/commands/config/set.js +111 -0
  16. package/dist/cli/commands/config/set.js.map +1 -0
  17. package/dist/cli/commands/repo/list.d.ts +26 -0
  18. package/dist/cli/commands/repo/list.d.ts.map +1 -0
  19. package/dist/cli/commands/repo/list.js +197 -0
  20. package/dist/cli/commands/repo/list.js.map +1 -0
  21. package/dist/cli/commands/repo/remove.d.ts +29 -0
  22. package/dist/cli/commands/repo/remove.d.ts.map +1 -0
  23. package/dist/cli/commands/repo/remove.js +219 -0
  24. package/dist/cli/commands/repo/remove.js.map +1 -0
  25. package/dist/cli/commands/report.d.ts +16 -0
  26. package/dist/cli/commands/report.d.ts.map +1 -0
  27. package/dist/cli/commands/report.js +160 -0
  28. package/dist/cli/commands/report.js.map +1 -0
  29. package/dist/cli/index.js +14 -0
  30. package/dist/cli/index.js.map +1 -1
  31. package/dist/core/config.d.ts +25 -0
  32. package/dist/core/config.d.ts.map +1 -1
  33. package/dist/core/config.js +77 -0
  34. package/dist/core/config.js.map +1 -1
  35. package/dist/core/repo/templates/claude-agents.d.ts.map +1 -1
  36. package/dist/core/repo/templates/claude-agents.js +136 -28
  37. package/dist/core/repo/templates/claude-agents.js.map +1 -1
  38. package/dist/core/repo/templates/claude-prompts.d.ts +1 -1
  39. package/dist/core/repo/templates/claude-prompts.d.ts.map +1 -1
  40. package/dist/core/repo/templates/claude-prompts.js +412 -157
  41. package/dist/core/repo/templates/claude-prompts.js.map +1 -1
  42. package/dist/core/repo/templates/claude-scripts.d.ts.map +1 -1
  43. package/dist/core/repo/templates/claude-scripts.js +555 -94
  44. package/dist/core/repo/templates/claude-scripts.js.map +1 -1
  45. package/dist/core/report.d.ts +25 -0
  46. package/dist/core/report.d.ts.map +1 -0
  47. package/dist/core/report.js +702 -0
  48. package/dist/core/report.js.map +1 -0
  49. package/dist/types/report.d.ts +158 -0
  50. package/dist/types/report.d.ts.map +1 -0
  51. package/dist/types/report.js +7 -0
  52. package/dist/types/report.js.map +1 -0
  53. package/package.json +1 -1
@@ -1,257 +1,512 @@
1
1
  /**
2
- * .claude/prompts/ templates
2
+ * .claude/prompts/ templates for Ralph autonomous executor
3
3
  */
4
4
  export const claudePrompts = [
5
- // ralph-research.md
5
+ // ralph-research.md - Research phase prompt (REQ-6)
6
6
  {
7
7
  path: '.claude/prompts/ralph-research.md',
8
- content: `# Ralph Research Prompt
8
+ content: `# Ralph Research Phase
9
9
 
10
- ## Context
10
+ You are preparing context for autonomous execution of plan:
11
+ \`{PLAN_PATH}\`
11
12
 
12
- Plan ID: {{PLAN_ID}}
13
- Session Number: {{SESSION_NUMBER}}
14
- Previous Sessions: {{PREVIOUS_SESSIONS}}
13
+ ## Mission
15
14
 
16
- ## Instructions
15
+ Gather ALL necessary context ONCE so subsequent task sessions can execute without re-researching.
16
+ This research will be used by all following execution sessions, which start with fresh context.
17
17
 
18
- Prepare for the next execution session by:
18
+ ## Process
19
19
 
20
- 1. **Review Progress**
21
- - Read the plan file
22
- - Check the progress log
23
- - Identify completed vs pending steps
20
+ 1. **Read the Plan**
21
+ - Read the full plan file at \`{PLAN_PATH}\`
22
+ - Understand all tasks and acceptance criteria
23
+ - Note dependencies between tasks
24
+
25
+ 2. **Analyze Codebase Context**
26
+ - Read maps in \`vibe/maps/\` if they exist
27
+ - Search knowledge base in \`vibe/knowledge-base/\`
28
+ - Check \`vibe/implementation-plans/completed/\` for similar work
29
+ - Identify patterns and conventions in the codebase
24
30
 
25
- 2. **Gather Context**
26
- - Read relevant source files
27
- - Check knowledge base for related entries
28
- - Review any error logs from previous sessions
31
+ 3. **Identify Key Files**
32
+ - For each task, list the files that need to be read or modified
33
+ - Note any shared utilities or types needed
34
+ - Identify test file locations
29
35
 
30
- 3. **Plan Next Steps**
31
- - Identify 2-3 steps to accomplish this session
32
- - Note any dependencies or blockers
33
- - Prepare code context
36
+ 4. **Document Gotchas**
37
+ - Check for known issues in knowledge base
38
+ - Note any architectural constraints
39
+ - Identify potential blockers
40
+
41
+ ## Output
34
42
 
35
- ## Output Format
43
+ Append a "## Ralph Research Context" section to the plan file with:
36
44
 
37
45
  \`\`\`markdown
38
- # Session {{SESSION_NUMBER}} Brief
46
+ ## Ralph Research Context
47
+
48
+ ### Codebase Summary
49
+ - [Key architectural patterns]
50
+ - [Relevant conventions]
51
+ - [Important utilities/types]
52
+
53
+ ### Maps Analysis
54
+ - [Summary of relevant entity maps]
55
+ - [API/service relationships]
56
+
57
+ ### Knowledge Base Findings
58
+ - [Relevant gotchas or decisions]
59
+ - [Patterns from similar implementations]
60
+
61
+ ### Key Files by Task
39
62
 
40
- ## Progress Summary
41
- - Steps completed: X/Y
42
- - Last completed: [step description]
43
- - Blockers: [any issues]
63
+ **Task 1:**
64
+ - Read: [files to read]
65
+ - Modify: [files to modify]
66
+ - Test: [test file]
44
67
 
45
- ## Next Steps
46
- 1. [Step to do]
47
- 2. [Step to do]
68
+ **Task 2:**
69
+ - Read: [files]
70
+ - Modify: [files]
71
+ - Test: [test file]
48
72
 
49
- ## Context Files
50
- - path/to/file1.ts
51
- - path/to/file2.ts
73
+ [Continue for all tasks...]
52
74
 
53
- ## Notes
54
- [Any relevant context or warnings]
75
+ ### Potential Blockers
76
+ - [Any identified risks or blockers]
55
77
  \`\`\`
78
+
79
+ ## Rules
80
+
81
+ - Be thorough - subsequent sessions depend on this research
82
+ - Be specific - list actual file paths, not generic descriptions
83
+ - Be concise - avoid unnecessary prose
84
+ - When complete, EXIT immediately
56
85
  `,
57
86
  },
58
- // ralph-execution.md
87
+ // ralph-execution.md - Task execution prompt (REQ-7)
59
88
  {
60
89
  path: '.claude/prompts/ralph-execution.md',
61
- content: `# Ralph Execution Prompt
90
+ content: `# Ralph Task Execution
62
91
 
63
- ## Context
92
+ You are executing **Task {CURRENT_TASK} of {TOTAL_TASKS}** from plan:
93
+ \`{PLAN_PATH}\`
64
94
 
65
- Plan ID: {{PLAN_ID}}
66
- Session Brief: {{SESSION_BRIEF}}
67
- Steps to Execute: {{STEPS}}
95
+ ## CRITICAL RULES
68
96
 
69
- ## Instructions
97
+ 1. **Complete ONLY Task {CURRENT_TASK}**
98
+ - Do NOT attempt other tasks
99
+ - Do NOT "look ahead" to future tasks
100
+ - Do NOT continue after this task
70
101
 
71
- Execute the planned steps for this session:
102
+ 2. **Fresh Context**
103
+ - You are starting with NO memory of previous tasks
104
+ - Read the "Ralph Research Context" section for background
105
+ - Read the plan's progress log for what's already done
72
106
 
73
- 1. **Read the brief** - Understand what to accomplish
74
- 2. **Execute each step** - Make the required changes
75
- 3. **Verify changes** - Run tests, check behavior
76
- 4. **Log progress** - Update the plan's progress log
107
+ 3. **Validation Required**
108
+ - Run typecheck after every code change: \`npm run typecheck\` or \`npx tsc --noEmit\`
109
+ - Run lint after every code change: \`npm run lint\`
110
+ - Fix ALL issues before marking task complete
77
111
 
78
- ## Guidelines
112
+ 4. **Exit Protocol**
113
+ - Update progress log in plan file
114
+ - Mark task complete in progress log
115
+ - EXIT immediately after
79
116
 
80
- - Make focused, incremental changes
81
- - Test after each significant change
82
- - Document any deviations from the plan
83
- - Note any issues for the cleanup phase
117
+ ## Process
84
118
 
85
- ## Output
119
+ 1. **Read the Plan**
120
+ - Read \`{PLAN_PATH}\`
121
+ - Find Task {CURRENT_TASK} specification
122
+ - Read the "Ralph Research Context" section
123
+ - Check progress log for completed tasks
124
+
125
+ 2. **Locate Key Files**
126
+ - Use the key files listed in research context
127
+ - Read necessary files before modifying
128
+
129
+ 3. **Execute Task**
130
+ - Implement the task requirements
131
+ - Follow existing code patterns
132
+ - Add appropriate error handling
133
+
134
+ 4. **Validate**
135
+ - Run typecheck
136
+ - Run lint
137
+ - Fix any issues
138
+
139
+ 5. **Update Progress**
140
+ - Add to progress log in plan:
141
+ \`\`\`markdown
142
+ ### Task {CURRENT_TASK} - [Date]
143
+ - Status: Complete
144
+ - Changes: [list of files changed]
145
+ - Notes: [any relevant notes]
146
+ \`\`\`
147
+
148
+ 6. **EXIT**
149
+ - Do not continue to next task
150
+ - Ralph will spawn a new session for the next task
86
151
 
87
- After execution, provide:
88
- - Summary of changes made
89
- - Files modified
90
- - Test results
91
- - Any issues encountered
152
+ ## Blocker Handling
153
+
154
+ If you cannot complete this task after 3 attempts:
155
+ 1. Add to plan: \`### PLAN_BLOCKED: [description of blocker]\`
156
+ 2. Include what you tried and why it failed
157
+ 3. EXIT immediately
158
+
159
+ Ralph will pause and notify for human intervention.
160
+
161
+ ## Example Progress Log Entry
162
+
163
+ \`\`\`markdown
164
+ ### Task 3 - 2026-01-22
165
+ - Status: Complete
166
+ - Changes:
167
+ - src/core/auth.ts: Added validateToken function
168
+ - src/types/auth.ts: Added TokenPayload interface
169
+ - tests/auth.test.ts: Added 5 test cases
170
+ - Notes: Used existing crypto utility for signature verification
171
+ \`\`\`
92
172
  `,
93
173
  },
94
- // ralph-cleanup.md
174
+ // ralph-cleanup.md - Cleanup phase prompt (REQ-8)
95
175
  {
96
176
  path: '.claude/prompts/ralph-cleanup.md',
97
- content: `# Ralph Cleanup Prompt
177
+ content: `# Ralph Cleanup Phase
178
+
179
+ You are verifying and finalizing plan:
180
+ \`{PLAN_PATH}\`
98
181
 
99
- ## Context
182
+ All tasks have been completed. This is the final verification phase.
100
183
 
101
- Plan ID: {{PLAN_ID}}
102
- Session Number: {{SESSION_NUMBER}}
103
- Execution Summary: {{EXECUTION_SUMMARY}}
184
+ ## Mission
104
185
 
105
- ## Instructions
186
+ Verify all work is complete, run quality checks, and finalize the plan.
106
187
 
107
- Verify and clean up after the execution session:
188
+ ## Process
108
189
 
109
- 1. **Verify Changes**
110
- - Review all modified files
111
- - Ensure changes are correct
112
- - Check for any leftover debug code
190
+ 1. **Read the Plan**
191
+ - Read \`{PLAN_PATH}\`
192
+ - Review all task progress entries
193
+ - Check acceptance criteria
113
194
 
114
- 2. **Run Tests**
115
- - Run relevant unit tests
116
- - Run integration tests if applicable
117
- - Check for regressions
195
+ 2. **Run Quality Checks**
196
+ - Run full test suite: \`npm test\`
197
+ - Run typecheck: \`npm run typecheck\`
198
+ - Run lint: \`npm run lint\`
199
+ - Run build: \`npm run build\`
118
200
 
119
- 3. **Update Documentation**
120
- - Update progress log in the plan
121
- - Check off completed acceptance criteria
122
- - Add any KB entries for learnings
201
+ 3. **Verify Acceptance Criteria**
202
+ - Go through each AC in the plan
203
+ - Mark each as verified or note issues
204
+ - Add verification section to plan
123
205
 
124
- 4. **Prepare Handoff**
125
- - Note any unfinished work
126
- - Document blockers for next session
127
- - Update plan status if complete
206
+ 4. **Final Documentation**
207
+ - Update plan status to "complete"
208
+ - Add completion timestamp
209
+ - Add any learnings to knowledge base
128
210
 
129
- ## Output Format
211
+ 5. **Cleanup**
212
+ - Remove any debug code or console.logs
213
+ - Ensure all files are properly formatted
214
+ - Check for any TODO comments that should be resolved
215
+
216
+ ## Output
217
+
218
+ Add a "## Completion Summary" section to the plan:
130
219
 
131
220
  \`\`\`markdown
132
- # Session {{SESSION_NUMBER}} Summary
221
+ ## Completion Summary
222
+
223
+ ### Verification Date
224
+ [Date]
133
225
 
134
- ## Changes Made
135
- - file1.ts: [description]
136
- - file2.ts: [description]
226
+ ### Quality Checks
227
+ - [x] All tests pass
228
+ - [x] Typecheck passes
229
+ - [x] Lint passes
230
+ - [x] Build succeeds
137
231
 
138
- ## Test Results
139
- - [x] Unit tests pass
140
- - [ ] Integration tests pass
232
+ ### Acceptance Criteria Verification
233
+ - [x] AC-1: [description] - Verified
234
+ - [x] AC-2: [description] - Verified
235
+ - [ ] AC-3: [description] - Issue: [note]
141
236
 
142
- ## Acceptance Criteria
143
- - [x] AC-1: ...
144
- - [ ] AC-2: ...
237
+ ### Files Changed
238
+ - [List all files modified during implementation]
145
239
 
146
- ## Issues
147
- - [Issue description]
240
+ ### Learnings
241
+ - [Any knowledge base entries to add]
148
242
 
149
- ## Next Session
150
- - [What to do next]
243
+ ### Status
244
+ **COMPLETE** - Ready for review
151
245
  \`\`\`
246
+
247
+ ## Rules
248
+
249
+ - Run ALL quality checks, not just some
250
+ - Be honest about any failing checks
251
+ - If there are issues, note them but don't try to fix complex problems
252
+ - Simple fixes (lint, formatting) can be done
253
+ - Complex issues should be noted for human review
254
+ - EXIT when complete
152
255
  `,
153
256
  },
154
- // ralph-plan-extraction.md
257
+ // ralph-plan-extraction.md - Extraction phase for plan mode (REQ-11)
155
258
  {
156
259
  path: '.claude/prompts/ralph-plan-extraction.md',
157
- content: `# Ralph Plan Extraction Prompt
260
+ content: `# Ralph Plan Extraction Phase
158
261
 
159
- ## Context
262
+ You are creating an implementation plan from scope:
263
+ \`{SCOPE_PATH}\`
160
264
 
161
- Scope ID: {{SCOPE_ID}}
162
- Scope Content: {{SCOPE_CONTENT}}
265
+ ## Mission
163
266
 
164
- ## Instructions
267
+ Parse the scope and identify modules for planning. Each module will be planned in a separate session.
165
268
 
166
- Extract a detailed implementation plan from the scope:
269
+ ## Process
167
270
 
168
- 1. **Analyze Requirements**
169
- - Identify all functional requirements
271
+ 1. **Read the Scope**
272
+ - Read \`{SCOPE_PATH}\`
273
+ - Understand all requirements
170
274
  - Note acceptance criteria
171
- - Understand technical constraints
275
+ - Identify technical constraints
172
276
 
173
- 2. **Plan Architecture**
174
- - Determine files to create/modify
175
- - Identify dependencies
176
- - Plan data flow
277
+ 2. **Analyze Codebase**
278
+ - Read relevant maps in \`vibe/maps/\`
279
+ - Check knowledge base for related work
280
+ - Understand existing architecture
177
281
 
178
- 3. **Break Down Steps**
179
- - Create concrete implementation steps
180
- - Order by dependencies
181
- - Estimate complexity
282
+ 3. **Identify Modules**
283
+ - Break scope into logical modules
284
+ - Each module should be independently plannable
285
+ - Note dependencies between modules
182
286
 
183
- ## Output Format
287
+ 4. **Create Plan Skeleton**
288
+ - Create plan file in \`vibe/implementation-plans/active/\`
289
+ - Add metadata and overview
290
+ - List identified modules
184
291
 
185
- Follow the PLAN_TEMPLATE.md structure.
292
+ ## Output
293
+
294
+ Create plan file at \`vibe/implementation-plans/active/PLAN-{SCOPE_ID}.md\`:
295
+
296
+ \`\`\`markdown
297
+ # PLAN-{SCOPE_ID}: [Title from scope]
298
+
299
+ ## Metadata
300
+ | Field | Value |
301
+ |-------|-------|
302
+ | Scope | {SCOPE_ID} |
303
+ | Status | planning |
304
+ | Created | [Date] |
305
+ | Modules | [count] |
306
+
307
+ ## Overview
308
+ [Brief description of what will be implemented]
309
+
310
+ ## Modules
311
+
312
+ ### Module 1: [Name]
313
+ - Description: [What this module covers]
314
+ - Requirements: [REQ-X, REQ-Y, ...]
315
+ - Dependencies: [Other modules this depends on]
316
+ - Status: pending
317
+
318
+ ### Module 2: [Name]
319
+ - Description: [...]
320
+ - Requirements: [...]
321
+ - Dependencies: [...]
322
+ - Status: pending
323
+
324
+ [Continue for all modules...]
325
+
326
+ ## Requirements Coverage
327
+ | Requirement | Module | Status |
328
+ |-------------|--------|--------|
329
+ | REQ-1 | Module 1 | planned |
330
+ | REQ-2 | Module 2 | planned |
331
+
332
+ ## Progress Log
333
+ [Will be updated as modules are planned]
334
+ \`\`\`
335
+
336
+ ## Rules
337
+
338
+ - Create 3-8 modules (too few = too complex, too many = too granular)
339
+ - Ensure ALL requirements map to at least one module
340
+ - Note dependencies to determine planning order
341
+ - EXIT when plan skeleton is created
186
342
  `,
187
343
  },
188
- // ralph-plan-module.md
344
+ // ralph-plan-module.md - Module planning prompt (REQ-12)
189
345
  {
190
346
  path: '.claude/prompts/ralph-plan-module.md',
191
- content: `# Ralph Module Plan Prompt
347
+ content: `# Ralph Module Planning
192
348
 
193
- ## Context
349
+ You are planning **Module {MODULE_INDEX}** ({MODULE_NAME}) from scope:
350
+ \`{SCOPE_PATH}\`
194
351
 
195
- Module: {{MODULE_NAME}}
196
- Requirements: {{REQUIREMENTS}}
352
+ ## Mission
197
353
 
198
- ## Instructions
354
+ Create detailed implementation steps for this module that can be executed autonomously.
199
355
 
200
- Create a focused plan for implementing this module:
356
+ ## Process
357
+
358
+ 1. **Read Context**
359
+ - Read the scope at \`{SCOPE_PATH}\`
360
+ - Read the plan file
361
+ - Focus on Module {MODULE_INDEX} requirements
201
362
 
202
- 1. **Define Interface**
203
- - Public API
204
- - Types and interfaces
205
- - Dependencies
363
+ 2. **Analyze Module**
364
+ - Understand what this module needs to accomplish
365
+ - Identify files to create or modify
366
+ - Note integration points with other modules
206
367
 
207
- 2. **Implementation Steps**
208
- - Core functionality
209
- - Edge cases
210
- - Error handling
368
+ 3. **Break Down Tasks**
369
+ - Create 3-7 concrete implementation tasks
370
+ - Each task should be completable in one session
371
+ - Order tasks by dependencies
211
372
 
212
- 3. **Testing Strategy**
213
- - Unit test scenarios
214
- - Integration points
215
- - Mock requirements
373
+ 4. **Define Acceptance Criteria**
374
+ - Create testable criteria for each task
375
+ - Map back to scope requirements
216
376
 
217
377
  ## Output
218
378
 
219
- Detailed steps for the module implementation.
379
+ Update the plan file with detailed module plan:
380
+
381
+ \`\`\`markdown
382
+ ### Module {MODULE_INDEX}: {MODULE_NAME}
383
+
384
+ #### Overview
385
+ [What this module implements]
386
+
387
+ #### Tasks
388
+
389
+ **Task 1: [Name]**
390
+ - Description: [What to implement]
391
+ - Files:
392
+ - Create: [new files]
393
+ - Modify: [existing files]
394
+ - Steps:
395
+ 1. [Specific step]
396
+ 2. [Specific step]
397
+ - AC: [Acceptance criteria]
398
+
399
+ **Task 2: [Name]**
400
+ - Description: [...]
401
+ - Files: [...]
402
+ - Steps: [...]
403
+ - AC: [...]
404
+
405
+ [Continue for all tasks...]
406
+
407
+ #### Integration Points
408
+ - [How this module connects to others]
409
+
410
+ #### Test Strategy
411
+ - [Unit tests needed]
412
+ - [Integration tests needed]
413
+ \`\`\`
414
+
415
+ ## Rules
416
+
417
+ - Be specific - list actual file paths
418
+ - Be actionable - steps should be clear enough for fresh-context execution
419
+ - Be complete - don't leave gaps for "figuring out later"
420
+ - Mark module status as "planned" when done
421
+ - EXIT when complete
220
422
  `,
221
423
  },
222
- // ralph-plan-validation.md
424
+ // ralph-plan-validation.md - Validation phase prompt (REQ-13)
223
425
  {
224
426
  path: '.claude/prompts/ralph-plan-validation.md',
225
- content: `# Ralph Plan Validation Prompt
427
+ content: `# Ralph Plan Validation
226
428
 
227
- ## Context
429
+ You are validating the implementation plan created from scope:
430
+ \`{SCOPE_PATH}\`
228
431
 
229
- Plan ID: {{PLAN_ID}}
230
- Plan Content: {{PLAN_CONTENT}}
231
- Scope Content: {{SCOPE_CONTENT}}
432
+ ## Mission
232
433
 
233
- ## Instructions
434
+ Ensure 100% requirement coverage and plan feasibility before execution begins.
234
435
 
235
- Validate that the plan adequately covers the scope:
436
+ ## Process
236
437
 
237
- 1. **Requirement Coverage**
238
- - Check each scope requirement has plan steps
239
- - Verify acceptance criteria are addressable
240
- - Note any gaps
438
+ 1. **Read Both Documents**
439
+ - Read the scope at \`{SCOPE_PATH}\`
440
+ - Read the complete plan file
241
441
 
242
- 2. **Feasibility Check**
243
- - Verify steps are concrete and actionable
244
- - Check dependencies are identified
245
- - Assess complexity estimates
442
+ 2. **Check Requirement Coverage**
443
+ - List every requirement from scope
444
+ - Verify each maps to at least one task
445
+ - Flag any gaps
246
446
 
247
- 3. **Risk Assessment**
447
+ 3. **Check Acceptance Criteria**
448
+ - Verify scope ACs can be verified by plan tasks
449
+ - Ensure test strategy covers ACs
450
+
451
+ 4. **Check Feasibility**
452
+ - Verify tasks are specific and actionable
453
+ - Check for missing dependencies
248
454
  - Identify potential blockers
249
- - Note technical risks
250
- - Suggest mitigations
455
+
456
+ 5. **Final Review**
457
+ - Update coverage table
458
+ - Mark plan ready for execution
251
459
 
252
460
  ## Output
253
461
 
254
- Validation report with any issues or suggestions.
462
+ Add validation section to plan:
463
+
464
+ \`\`\`markdown
465
+ ## Validation Report
466
+
467
+ ### Validation Date
468
+ [Date]
469
+
470
+ ### Requirement Coverage
471
+
472
+ | Requirement | Description | Tasks | Status |
473
+ |-------------|-------------|-------|--------|
474
+ | REQ-1 | [desc] | Task 1.1, 1.2 | Covered |
475
+ | REQ-2 | [desc] | Task 2.1 | Covered |
476
+ | REQ-3 | [desc] | - | GAP |
477
+
478
+ ### Acceptance Criteria Coverage
479
+
480
+ | AC | Description | Verification | Status |
481
+ |----|-------------|--------------|--------|
482
+ | AC-1 | [desc] | Task 1.3 test | Covered |
483
+ | AC-2 | [desc] | Module 2 integration test | Covered |
484
+
485
+ ### Feasibility Assessment
486
+ - [ ] All tasks are specific and actionable
487
+ - [ ] Dependencies are clearly identified
488
+ - [ ] No circular dependencies between modules
489
+ - [ ] Test strategy is complete
490
+
491
+ ### Identified Risks
492
+ - [Risk 1]: [Mitigation]
493
+ - [Risk 2]: [Mitigation]
494
+
495
+ ### Gaps Found
496
+ [List any gaps or issues, or "None - ready for execution"]
497
+
498
+ ### Recommendation
499
+ - [ ] Ready for execution
500
+ - [ ] Needs revision: [reasons]
501
+ \`\`\`
502
+
503
+ ## Rules
504
+
505
+ - Be thorough - missing coverage will cause execution failures
506
+ - Be honest - flag issues now, not during execution
507
+ - Update plan status to "ready" if validation passes
508
+ - Update plan status to "needs_revision" if gaps found
509
+ - EXIT when complete
255
510
  `,
256
511
  },
257
512
  ];
@@ -1 +1 @@
1
- {"version":3,"file":"claude-prompts.js","sourceRoot":"","sources":["../../../../src/core/repo/templates/claude-prompts.ts"],"names":[],"mappings":"AAAA;;GAEG;AAIH,MAAM,CAAC,MAAM,aAAa,GAAmB;IAC3C,oBAAoB;IACpB;QACE,IAAI,EAAE,mCAAmC;QACzC,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgDZ;KACE;IAED,qBAAqB;IACrB;QACE,IAAI,EAAE,oCAAoC;QAC1C,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+BZ;KACE;IAED,mBAAmB;IACnB;QACE,IAAI,EAAE,kCAAkC;QACxC,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAuDZ;KACE;IAED,2BAA2B;IAC3B;QACE,IAAI,EAAE,0CAA0C;QAChD,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6BZ;KACE;IAED,uBAAuB;IACvB;QACE,IAAI,EAAE,sCAAsC;QAC5C,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6BZ;KACE;IAED,2BAA2B;IAC3B;QACE,IAAI,EAAE,0CAA0C;QAChD,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8BZ;KACE;CACF,CAAC"}
1
+ {"version":3,"file":"claude-prompts.js","sourceRoot":"","sources":["../../../../src/core/repo/templates/claude-prompts.ts"],"names":[],"mappings":"AAAA;;GAEG;AAIH,MAAM,CAAC,MAAM,aAAa,GAAmB;IAC3C,oDAAoD;IACpD;QACE,IAAI,EAAE,mCAAmC;QACzC,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6EZ;KACE;IAED,qDAAqD;IACrD;QACE,IAAI,EAAE,oCAAoC;QAC1C,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAkFZ;KACE;IAED,kDAAkD;IAClD;QACE,IAAI,EAAE,kCAAkC;QACxC,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8EZ;KACE;IAED,qEAAqE;IACrE;QACE,IAAI,EAAE,0CAA0C;QAChD,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAkFZ;KACE;IAED,yDAAyD;IACzD;QACE,IAAI,EAAE,sCAAsC;QAC5C,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA2EZ;KACE;IAED,8DAA8D;IAC9D;QACE,IAAI,EAAE,0CAA0C;QAChD,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmFZ;KACE;CACF,CAAC"}
@@ -1 +1 @@
1
- {"version":3,"file":"claude-scripts.d.ts","sourceRoot":"","sources":["../../../../src/core/repo/templates/claude-scripts.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,YAAY,CAAC;AAE/C,eAAO,MAAM,aAAa,EAAE,YAAY,EA+MvC,CAAC"}
1
+ {"version":3,"file":"claude-scripts.d.ts","sourceRoot":"","sources":["../../../../src/core/repo/templates/claude-scripts.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,YAAY,CAAC;AAE/C,eAAO,MAAM,aAAa,EAAE,YAAY,EA4pBvC,CAAC"}