claude-code-workflow 7.2.9 → 7.2.11

package/.claude/skills/workflow-tune/templates/synthesis-prompt.md

@@ -0,0 +1,90 @@
+# Synthesis Prompt Template
+
+Phase 04 使用此模板构造 ccw cli 提示词，让 Gemini 综合所有步骤分析，产出跨步骤优化建议。
+
+## Template
+
+```
+PURPOSE: Synthesize all step analyses into a holistic workflow optimization assessment. Evaluate cross-step concerns: ordering, handoff quality, redundancy, bottlenecks, and overall workflow coherence.
+
+WORKFLOW OVERVIEW:
+Name: ${workflowName}
+Goal: ${workflowContext}
+Steps: ${stepCount}
+Average Quality: ${avgScore}/100
+Weakest Step: ${minScore}/100
+Total Issues: ${totalIssues} (${totalHighIssues} high severity)
+
+SCORE SUMMARY:
+${scoreSummary}
+
+COMPLETE PROCESS LOG:
+${processLog}
+
+DETAILED STEP ANALYSES:
+${stepAnalyses}
+
+TASK:
+1. **Workflow Coherence**: Do steps form a logical sequence? Any missing steps?
+2. **Handoff Quality**: Are step outputs well-consumed by subsequent steps? Data format mismatches?
+3. **Redundancy Detection**: Do any steps duplicate work? Overlapping concerns?
+4. **Bottleneck Identification**: Which steps are bottlenecks (lowest quality, longest duration)?
+5. **Step Ordering**: Would reordering steps improve outcomes?
+6. **Missing Steps**: Are there gaps in the pipeline that need additional steps?
+7. **Per-Step Optimization**: Top 3 improvements per underperforming step
+8. **Workflow-Level Optimization**: Structural changes to the overall pipeline
+
+EXPECTED OUTPUT (strict JSON, no markdown):
+{
+  "workflow_score": <0-100>,
+  "coherence": {
+    "score": <0-100>,
+    "assessment": "<logical flow evaluation>",
+    "gaps": ["<missing step or transition>"]
+  },
+  "handoff_quality": {
+    "score": <0-100>,
+    "issues": [
+      { "from_step": "<step name>", "to_step": "<step name>", "issue": "<description>", "fix": "<suggestion>" }
+    ]
+  },
+  "redundancy": {
+    "found": <true|false>,
+    "items": [
+      { "steps": ["<step1>", "<step2>"], "description": "<what overlaps>", "recommendation": "<merge or remove>" }
+    ]
+  },
+  "bottlenecks": [
+    { "step": "<step name>", "reason": "<why it's a bottleneck>", "impact": "high|medium|low", "fix": "<suggestion>" }
+  ],
+  "ordering_suggestions": [
+    { "current": "<current order description>", "proposed": "<new order>", "rationale": "<why>" }
+  ],
+  "per_step_improvements": [
+    { "step": "<step name>", "improvements": [
+      { "priority": "high|medium|low", "description": "<what to change>", "rationale": "<why>" }
+    ]}
+  ],
+  "workflow_improvements": [
+    { "priority": "high|medium|low", "category": "structure|handoff|performance|quality", "description": "<change>", "rationale": "<why>", "affected_steps": ["<step names>"] }
+  ],
+  "summary": "<2-3 sentence executive summary of workflow health and top recommendations>"
+}
+
+CONSTRAINTS: Be specific, reference step names and artifact details, output ONLY JSON
+```
+
+## Variable Substitution
+
+| Variable | Source | Description |
+|----------|--------|-------------|
+| `${workflowName}` | workflow-state.json | Workflow 名称 |
+| `${workflowContext}` | workflow-state.json | Workflow 目标 |
+| `${stepCount}` | workflow-state.json | 总步骤数 |
+| `${avgScore}` | Phase 04 computes | 所有步骤平均分 |
+| `${minScore}` | Phase 04 computes | 最低步骤分 |
+| `${totalIssues}` | Phase 04 computes | 总问题数 |
+| `${totalHighIssues}` | Phase 04 computes | 高优先级问题数 |
+| `${scoreSummary}` | Phase 04 builds | 每步分数一行 |
+| `${processLog}` | process-log.md | 完整过程日志 |
+| `${stepAnalyses}` | Phase 04 reads | 所有 step-N-analysis.md 内容 |

package/.codex/skills/analyze-with-file/SKILL.md

@@ -10,14 +10,14 @@ argument-hint: "TOPIC=\"<question or topic>\" [--depth=quick|standard|deep] [--c
 
 Interactive collaborative analysis workflow with **documented discussion process**. Records understanding evolution, facilitates multi-round Q&A, and uses inline search tools for deep exploration.
 
-**Core workflow**: Topic → Explore → Discuss → Document → Refine → Conclude → (Optional) Quick Execute
+**Core workflow**: Topic → Explore → Discuss → Document → Refine → Conclude → Plan Checklist
 
 **Key features**:
 - **Documented discussion timeline**: Captures understanding evolution across all phases
 - **Decision recording at every critical point**: Mandatory recording of key findings, direction changes, and trade-offs
 - **Multi-perspective analysis**: Supports up to 4 analysis perspectives (serial, inline)
 - **Interactive discussion**: Multi-round Q&A with user feedback and direction adjustments
-- **Quick execute**: Convert conclusions directly to executable tasks
+- **Plan output**: Generate structured plan checklist for downstream execution (e.g., `$csv-wave-pipeline`)
 
 ### Decision Recording Protocol
 
@@ -96,6 +96,7 @@ Step 1: Topic Understanding
 Step 2: Exploration (Inline, No Agents)
    ├─ Detect codebase → search relevant modules, patterns
    │   ├─ Run `ccw spec load --category exploration` (if spec system available)
+   │   ├─ Run `ccw spec load --category debug` (known issues and root-cause notes)
    │   └─ Use Grep, Glob, Read, mcp__ace-tool__search_context
    ├─ Multi-perspective analysis (if selected, serial)
    │   ├─ Single: Comprehensive analysis
@@ -128,17 +129,11 @@ Step 4: Synthesis & Conclusion
    ├─ Consolidate all insights → conclusions.json (with steps[] per recommendation)
    ├─ Update discussion.md with final synthesis
    ├─ Interactive Recommendation Review (per-recommendation confirm/modify/reject)
-   └─ Offer options: quick execute / create issue / generate task / export / done
-
-Step 5: Execute (Optional - user selects, routes by complexity)
-   ├─ Simple (≤2 recs): Direct inline execution → summary in discussion.md
-   └─ Complex (≥3 recs): EXECUTE.md pipeline
-      ├─ Enrich recommendations → generate .task/TASK-*.json
-      ├─ Pre-execution analysis (dependencies, file conflicts, execution order)
-      ├─ User confirmation
-      ├─ Direct inline execution (Read/Edit/Write/Grep/Glob/Bash)
-      ├─ Record events → execution-events.md, update execution.md
-      └─ Report completion summary
+   └─ Offer options: generate plan / create issue / export / done
+
+Step 5: Plan Generation (Optional - produces plan only, NO code modifications)
+   ├─ Generate inline plan checklist → appended to discussion.md
+   └─ Remind user to execute via $csv-wave-pipeline
 ```
 
 ## Configuration
@@ -326,6 +321,7 @@ const hasCodebase = Bash(`
 if (hasCodebase !== 'none') {
   // 1. Read project metadata (if exists)
   //    - Run `ccw spec load --category exploration` (load project specs)
+  //    - Run `ccw spec load --category debug` (known issues and root-cause notes)
   //    - .workflow/specs/*.md (project conventions)
 
   // 2. Search codebase for relevant content
@@ -817,7 +813,7 @@ for (const [index, rec] of sortedRecs.entries()) {
 
 ##### Step 4.4: Post-Completion Options
 
-**Complexity Assessment** — determine whether .task/*.json generation is warranted:
+**Complexity Assessment** — determine available options:
 
 ```javascript
 // Assess recommendation complexity to decide available options
@@ -833,9 +829,9 @@ function assessComplexity(recs) {
 
 // Complexity → available options mapping:
 //   none:    Done | Create Issue | Export Report
-//   simple:  Done | Create Issue | Export Report (no task generation — overkill)
-//   moderate: Done | Generate Task | Create Issue | Export Report
-//   complex:  Quick Execute | Generate Task | Create Issue | Export Report | Done
+//   simple:  Done | Create Issue | Export Report
+//   moderate: Generate Plan | Create Issue | Export Report | Done
+//   complex:  Generate Plan | Create Issue | Export Report | Done
 ```
 
 ```javascript
@@ -850,9 +846,9 @@ if (!autoYes) {
     }]
   })
 } else {
-  // Auto mode: generate .task/*.json only for moderate/complex, skip for simple/none
+  // Auto mode: generate plan only for moderate/complex, skip for simple/none
   if (complexity === 'complex' || complexity === 'moderate') {
-    // → Phase 5 Step 5.1-5.2 (task generation only, no execution)
+    // → Phase 5 (plan generation only, NO code modifications)
   } else {
     // → Done (conclusions.json is sufficient output)
   }
@@ -865,14 +861,13 @@ if (!autoYes) {
 |------------|-------------------|-----------|
 | `none` | Done, Create Issue, Export Report | No actionable recommendations |
 | `simple` | Done, Create Issue, Export Report | 1-2 low-priority items don't warrant formal task JSON |
-| `moderate` | Generate Task, Create Issue, Export Report, Done | Task structure helpful but execution not urgent |
-| `complex` | Quick Execute, Generate Task, Create Issue, Export Report, Done | Full pipeline justified |
+| `moderate` | Generate Plan, Create Issue, Export Report, Done | Task structure helpful for downstream execution |
+| `complex` | Generate Plan, Create Issue, Export Report, Done | Full plan generation justified |
 
 | Selection | Action |
 |-----------|--------|
-| Quick Execute | Jump to Phase 5 (only reviewed recs with status accepted/modified) |
+| Generate Plan | Jump to Phase 5 (plan generation only, NO code modifications) |
 | Create Issue | `Skill(skill="issue:new", args="...")` (only reviewed recs) |
-| Generate Task | Jump to Phase 5 Step 5.1-5.2 only (generate .task/*.json, no execution) |
 | Export Report | Copy discussion.md + conclusions.json to user-specified location |
 | Done | Display artifact paths, end |
 
@@ -883,96 +878,64 @@ if (!autoYes) {
 - User offered meaningful next step options
 - **Complete decision trail** documented and traceable from initial scoping to final conclusions
 
-### Phase 5: Execute (Optional)
-
-**Objective**: Execute analysis recommendations — route by complexity.
-
-**Trigger**: User selects "Quick Execute" in Phase 4. In auto mode, triggered only for `moderate`/`complex` recommendations.
+### Phase 5: Plan Generation (Optional — NO code modifications)
 
-**Routing Logic**:
-
-```
-complexity assessment (from Phase 4.3)
-  ├─ simple/moderate (≤2 recommendations, clear changes)
-  │   └─ Direct inline execution — no .task/*.json overhead
-  └─ complex (≥3 recommendations, or high-priority with dependencies)
-      └─ Route to EXECUTE.md — full pipeline (task generation → execution)
-```
+**Objective**: Generate structured plan checklist from analysis recommendations. **This phase produces plans only — it does NOT modify any source code.**
 
-##### Step 5.1: Route by Complexity
+**Trigger**: User selects "Generate Plan" in Phase 4. In auto mode, triggered only for `moderate`/`complex` recommendations.
 
 ```javascript
 const recs = conclusions.recommendations || []
 
-if (recs.length >= 3 || recs.some(r => r.priority === 'high')) {
-  // COMPLEX PATH → EXECUTE.md pipeline
-  // Full specification: EXECUTE.md
-  // Flow: load all context → generate .task/*.json → pre-execution analysis → serial execution → finalize
-} else {
-  // SIMPLE PATH → direct inline execution (below)
-}
-```
+// Build plan checklist from all accepted/modified recommendations
+const planChecklist = recs
+  .filter(r => r.review_status !== 'rejected')
+  .map((rec, index) => {
+    const files = rec.evidence_refs
+      ?.filter(ref => ref.includes(':'))
+      .map(ref => ref.split(':')[0]) || []
 
-##### Step 5.2: Simple Path — Direct Inline Execution
+    return `### ${index + 1}. ${rec.action}
+- **Priority**: ${rec.priority}
+- **Rationale**: ${rec.rationale}
+- **Target files**: ${files.join(', ') || 'TBD'}
+- **Evidence**: ${rec.evidence_refs?.join(', ') || 'N/A'}
+- [ ] Ready for execution`
+  }).join('\n\n')
 
-For simple/moderate recommendations, execute directly without .task/*.json ceremony:
+// Append plan checklist to discussion.md
+appendToDiscussion(`
+## Plan Checklist
 
-```javascript
-// For each recommendation:
-recs.forEach((rec, index) => {
-  // 1. Locate relevant files from evidence_refs or codebase search
-  const files = rec.evidence_refs
-    ?.filter(ref => ref.includes(':'))
-    .map(ref => ref.split(':')[0]) || []
+> **This is a plan only — no code was modified.**
+> To execute, use: \`$csv-wave-pipeline "<requirement summary>"\`
 
-  // 2. Read each target file
-  files.forEach(filePath => Read(filePath))
+- **Recommendations**: ${recs.length}
+- **Generated**: ${getUtc8ISOString()}
 
-  // 3. Apply changes based on rec.action + rec.rationale
-  //    Use Edit (preferred) for modifications, Write for new files
+${planChecklist}
 
-  // 4. Log to discussion.md — append execution summary
-})
+---
 
-// Append execution summary to discussion.md
-appendToDiscussion(`
-## Quick Execution Summary
+### Next Step: Execute
 
-- **Recommendations executed**: ${recs.length}
-- **Completed**: ${getUtc8ISOString()}
+Run \`$csv-wave-pipeline\` to execute these recommendations as wave-based batch tasks:
 
-${recs.map((rec, i) => `### ${i+1}. ${rec.action}
-- **Status**: completed/failed
-- **Rationale**: ${rec.rationale}
-- **Evidence**: ${rec.evidence_refs?.join(', ') || 'N/A'}
-`).join('\n')}
+\`\`\`bash
+$csv-wave-pipeline "${topic}"
+\`\`\`
 `)
 ```
 
-**Simple path characteristics**:
-- No `.task/*.json` generation
-- No `execution.md` / `execution-events.md`
-- Execution summary appended directly to `discussion.md`
-- Suitable for 1-2 clear, low-risk recommendations
-
-##### Step 5.3: Complex Path — EXECUTE.md Pipeline
-
-For complex recommendations, follow the full specification in `EXECUTE.md`:
-
-1. **Load context sources**: Reuse in-memory artifacts or read from disk
-2. **Enrich recommendations**: Resolve target files, generate implementation steps, build convergence criteria
-3. **Generate `.task/*.json`**: Individual task files with full execution context
-4. **Pre-execution analysis**: Dependency validation, file conflicts, topological sort
-5. **User confirmation**: Present task list, allow adjustment
-6. **Serial execution**: Execute each task following generated implementation steps
-7. **Finalize**: Update task states, write execution artifacts
-
-**Full specification**: `EXECUTE.md`
+**Characteristics**:
+- Plan checklist appended directly to `discussion.md`
+- **No code modifications** — plan output only
+- Reminds user to use `$csv-wave-pipeline` for execution
 
 **Success Criteria**:
-- Simple path: recommendations executed, summary in discussion.md
-- Complex path: `.task/*.json` generated with quality validation, execution tracked via execution.md + execution-events.md
-- Execution route chosen correctly based on complexity assessment
+- Plan checklist in discussion.md with all accepted recommendations
+- User reminded about `$csv-wave-pipeline` for execution
+- **No source code modified** — strictly plan output
 
 ## Output Structure
 
@@ -989,11 +952,11 @@ For complex recommendations, follow the full specification in `EXECUTE.md`:
 └── conclusions.json           # Phase 4: Final synthesis with recommendations
 ```
 
-> **Phase 5 complex path** adds `.task/`, `execution.md`, `execution-events.md` — see `EXECUTE.md` for structure.
+> **Phase 5** appends a plan checklist to `discussion.md`. No additional files are generated.
 
 | File | Phase | Description |
 |------|-------|-------------|
-| `discussion.md` | 1-4 | Session metadata → discussion timeline → conclusions. Simple execution summary appended here. |
+| `discussion.md` | 1-5 | Session metadata → discussion timeline → conclusions. Plan checklist appended here (simple path). |
 | `exploration-codebase.json` | 2 | Codebase context: relevant files, patterns, constraints |
 | `explorations/*.json` | 2 | Per-perspective exploration results (multi only) |
 | `explorations.json` | 2 | Single perspective aggregated findings |
@@ -1158,16 +1121,13 @@ Remaining questions or areas for investigation
 | User timeout in discussion | Save state, show resume command | Use `--continue` to resume |
 | Max rounds reached (5) | Force synthesis phase | Highlight remaining questions in conclusions |
 | Session folder conflict | Append timestamp suffix | Create unique folder and continue |
-| Quick execute: task fails | Record failure, ask user | Retry, skip, or abort (see EXECUTE.md) |
-| Quick execute: verification fails | Mark as unverified | Note in events, manual check |
-| Quick execute: no recommendations | Cannot generate .task/*.json | Inform user, suggest lite-plan |
-| Quick execute: simple recommendations | Complexity too low for .task/*.json | Direct inline execution (no task generation) |
+| Plan generation: no recommendations | No plan to generate | Inform user, suggest lite-plan |
 
 ## Best Practices
 
 ### Core Principles
 
-1. **Explicit user confirmation required before code modifications**: The analysis phase is strictly read-only. Any code changes (Phase 5 quick execute) require user approval.
+1. **No code modifications**: This skill is strictly read-only and plan-only. Phase 5 generates plan checklists in `discussion.md` but does NOT modify source code. Use `$csv-wave-pipeline` for execution.
 
 ### Before Starting Analysis
 
@@ -1204,10 +1164,11 @@ Remaining questions or areas for investigation
 - Building shared understanding before implementation
 - Want to document how understanding evolved
 
-**Use Quick Execute (Phase 5) when:**
+**Use Plan Generation (Phase 5) when:**
 - Analysis conclusions contain clear, actionable recommendations
-- Simple: 1-2 clear changes → direct inline execution (no .task/ overhead)
-- Complex: 3+ recommendations with dependencies → EXECUTE.md pipeline (.task/*.json → serial execution)
+- Simple: 1-2 items → inline plan checklist in discussion.md
+- Complex: 3+ recommendations → detailed plan checklist
+- **Then execute via**: `$csv-wave-pipeline` for wave-based batch execution
 
 **Consider alternatives when:**
 - Specific bug diagnosis needed → use `debug-with-file`

package/.codex/skills/debug-with-file/SKILL.md

@@ -22,6 +22,10 @@ Enhanced evidence-based debugging with **documented exploration process**. Recor
 
 **$BUG**
 
+## Project Context
+
+Run `ccw spec load --category debug` for known issues, workarounds, and root-cause notes.
+
 ## Execution Process
 
 ```

package/.codex/skills/issue-discover/SKILL.md

@@ -232,6 +232,7 @@ const agentId = spawn_agent({
 ### MANDATORY FIRST STEPS (Agent Execute)
 1. **Read role definition**: ~/.codex/agents/{agent-type}.md (MUST read first)
 2. Execute: ccw spec load --category exploration
+3. Execute: ccw spec load --category debug (known issues cross-reference)
 
 ## TASK CONTEXT
 ${taskContext}

package/.codex/skills/review-cycle/phases/02-parallel-review.md

@@ -95,6 +95,7 @@ dimensions.forEach(dimension => {
 4. Validate file access: bash(ls -la ${targetFiles.join(' ')})
 5. Execute: cat ~/.ccw/workflows/cli-templates/schemas/review-dimension-results-schema.json (get output schema reference)
 6. Execute: ccw spec load --category "exploration execution" (technology stack and constraints)
+7. Execute: ccw spec load --category review (review standards and checklists)
 
 ---
 
@@ -217,6 +218,7 @@ dimensions.forEach(dimension => {
 5. Read review state: ${reviewStateJsonPath}
 6. Execute: cat ~/.ccw/workflows/cli-templates/schemas/review-dimension-results-schema.json (get output schema reference)
 7. Execute: ccw spec load --category "exploration execution" (technology stack and constraints)
+8. Execute: ccw spec load --category review (review standards and checklists)
 
 ---
 
@@ -335,6 +337,7 @@ const deepDiveAgentId = spawn_agent({
 5. Read test files: bash(find ${projectDir}/tests -name "*${basename(file, '.ts')}*" -type f)
 6. Execute: cat ~/.ccw/workflows/cli-templates/schemas/review-deep-dive-results-schema.json (get output schema reference)
 7. Execute: ccw spec load --category "exploration execution" (technology stack and constraints for remediation)
+8. Execute: ccw spec load --category review (review standards and checklists)
 
 ---
 

package/.codex/skills/roadmap-with-file/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: roadmap-with-file
-description: Strategic requirement roadmap with iterative decomposition and issue creation. Outputs roadmap.md (human-readable, single source) + issues.jsonl (machine-executable). Handoff to team-planex.
+description: Strategic requirement roadmap with iterative decomposition and issue creation. Outputs roadmap.md (human-readable, single source) + issues.jsonl (machine-executable). Handoff to csv-wave-pipeline.
 argument-hint: "[-y|--yes] [-c|--continue] [-m progressive|direct|auto] \"requirement description\""
 ---
 
@@ -101,8 +101,8 @@ close_agent({ id: agentId })
 
 | Artifact | Purpose | Consumer |
 |----------|---------|----------|
-| `roadmap.md` | ⭐ Human-readable strategic roadmap with all context | Human review, team-planex handoff |
-| `.workflow/issues/issues.jsonl` | Global issue store (appended) | team-planex, issue commands |
+| `roadmap.md` | ⭐ Human-readable strategic roadmap with all context | Human review, csv-wave-pipeline handoff |
+| `.workflow/issues/issues.jsonl` | Global issue store (appended) | csv-wave-pipeline, issue commands |
 
 ### Why No Separate JSON Files?
 
@@ -145,7 +145,7 @@ Strategic requirement roadmap with **iterative decomposition**. Creates a single
 │                                                                          │
 │  Phase 4: Handoff                                                        │
 │     ├─ Final roadmap.md with Issue ID references                         │
-│     ├─ Options: team-planex | first wave | view issues | done            │
+│     ├─ Options: csv-wave-pipeline | view issues | done                   │
 │     └─ Issues ready in .workflow/issues/issues.jsonl                     │
 │                                                                          │
 └─────────────────────────────────────────────────────────────────────────┘
@@ -180,7 +180,7 @@ Strategic requirement roadmap with **iterative decomposition**. Creates a single
 
 .workflow/issues/issues.jsonl   # Global issue store (appended)
                                 #   - One JSON object per line
-                                #   - Consumed by team-planex, issue commands
+                                #   - Consumed by csv-wave-pipeline, issue commands
 ```
 
 ---
@@ -799,8 +799,7 @@ ${selectedMode === 'progressive' ? `**Progressive Mode**:
          type: "choice",
          prompt: `${issueIds.length} issues ready. Next step:`,
          options: [
-           { value: "planex", label: "Execute with team-planex (Recommended)", description: `Run all ${issueIds.length} issues via team-planex` },
-           { value: "wave1", label: "Execute first wave", description: "Run wave-1 issues only" },
+           { value: "csv-wave", label: "Execute with csv-wave-pipeline (Recommended)", description: `Run all ${issueIds.length} issues via wave-based batch execution` },
            { value: "view", label: "View issues", description: "Display issue details" },
            { value: "done", label: "Done", description: "Save and exit" }
          ]
@@ -814,14 +813,9 @@ ${selectedMode === 'progressive' ? `**Progressive Mode**:
 3. **Execute Selection**
    ```javascript
    switch (nextStep) {
-     case 'planex':
-       // Launch team-planex with all issue IDs
-       Bash(`ccw skill team-planex ${issueIds.join(' ')}`)
-       break
-
-     case 'wave1':
-       // Filter issues by wave-1 tag
-       Bash(`ccw skill team-planex --tag wave-1 --session ${sessionId}`)
+     case 'csv-wave':
+       // Launch csv-wave-pipeline for wave-based batch execution
+       console.log(`\nTo execute, run:\n\n  $csv-wave-pipeline "${requirement}"\n`)
        break
 
      case 'view':
@@ -836,7 +830,7 @@ ${selectedMode === 'progressive' ? `**Progressive Mode**:
          `Issues created: ${issueIds.length}`,
          '',
          'To execute later:',
-         `  $team-planex ${issueIds.slice(0, 3).join(' ')}...`,
+         `  $csv-wave-pipeline "${requirement}"`,
          `  ccw issue list --session ${sessionId}`
        ].join('\n'))
        break
@@ -872,7 +866,7 @@ ${selectedMode === 'progressive' ? `**Progressive Mode**:
 4. **Testable Convergence**: criteria = assertions, DoD = business language
 5. **Explicit Lifecycle**: Always close_agent after wait completes to free resources
 6. **DO NOT STOP**: Continuous workflow until handoff complete
-7. **Plan-Only Modifications**: Interactive feedback (Phase 3) MUST only update `roadmap.md` and `issues.jsonl`. NEVER modify source code, configuration files, or any project files during interactive rounds. Code changes happen only after handoff (Phase 4) via team-planex or other execution skills
+7. **Plan-Only Modifications**: Interactive feedback (Phase 3) MUST only update `roadmap.md` and `issues.jsonl`. NEVER modify source code, configuration files, or any project files during interactive rounds. Code changes happen only after handoff (Phase 4) via `$csv-wave-pipeline` or other execution skills
 
 ---