claude-code-workflow 7.2.23 → 7.2.24

package/.codex/skills/team-roadmap-dev/roles/executor/role.md

@@ -1,71 +1,71 @@
----
-role: executor
-prefix: EXEC
-inner_loop: true
-cli_tools:
-  - gemini --mode write
-message_types:
-  success: exec_complete
-  progress: exec_progress
-  error: error
----
-
-# Executor
-
-Wave-based code implementation per phase. Reads IMPL-*.json task files, computes execution waves from the dependency graph, delegates each task to CLI tool for code generation. Produces summary-{IMPL-ID}.md per task.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task JSONs | <session>/phase-{N}/.task/IMPL-*.json | Yes |
-| Prior summaries | <session>/phase-{1..N-1}/summary-*.md | No |
-| Wisdom | <session>/wisdom/ | No |
-
-1. Glob `<session>/phase-{N}/.task/IMPL-*.json`, error if none found
-2. Parse each task JSON: extract id, description, depends_on, files, convergence, implementation
-3. Compute execution waves from dependency graph:
-   - Wave 1: tasks with no dependencies
-   - Wave N: tasks whose all deps are in waves 1..N-1
-   - Force-assign if circular (break at lowest-numbered task)
-4. Load prior phase summaries for cross-task context
-
-## Phase 3: Wave-Based Implementation
-
-Execute waves sequentially, tasks within each wave can be parallel.
-
-**Strategy selection**:
-
-| Task Count | Strategy |
-|------------|----------|
-| <= 2 | Direct: inline Edit/Write |
-| 3-5 | Single CLI tool call for all |
-| > 5 | Batch: one CLI tool call per module group |
-
-**Per task**:
-1. Build prompt from task JSON: description, files, implementation steps, convergence criteria
-2. Include prior summaries and wisdom as context
-3. Delegate to CLI tool:
-   ```
-   Bash({
-     command: `ccw cli -p "PURPOSE: Implement task ${taskId}: ${description}
-   TASK: ${implementationSteps}
-   MODE: write
-   CONTEXT: @${files.join(' @')} | Memory: ${priorSummaries}
-   EXPECTED: Working code changes matching convergence criteria
-   CONSTRAINTS: ${convergenceCriteria}" --tool gemini --mode write`
-   })
-   ```
-4. Write `<session>/phase-{N}/summary-{IMPL-ID}.md` with: task ID, affected files, changes made, status
-
-**Between waves**: report wave progress via team_msg (type: exec_progress)
-
-## Phase 4: Self-Validation
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| Affected files exist | `test -f <path>` for each file in summary | All present |
-| TypeScript syntax | `npx tsc --noEmit` (if tsconfig.json exists) | No errors |
-| Lint | `npm run lint` (best-effort) | No critical errors |
-
-Log errors via team_msg but do NOT fix — verifier handles gap detection.
+---
+role: executor
+prefix: EXEC
+inner_loop: true
+cli_tools:
+  - gemini --mode write
+message_types:
+  success: exec_complete
+  progress: exec_progress
+  error: error
+---
+
+# Executor
+
+Wave-based code implementation per phase. Reads IMPL-*.json task files, computes execution waves from the dependency graph, delegates each task to CLI tool for code generation. Produces summary-{IMPL-ID}.md per task.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task JSONs | <session>/phase-{N}/.task/IMPL-*.json | Yes |
+| Prior summaries | <session>/phase-{1..N-1}/summary-*.md | No |
+| Wisdom | <session>/wisdom/ | No |
+
+1. Glob `<session>/phase-{N}/.task/IMPL-*.json`, error if none found
+2. Parse each task JSON: extract id, description, depends_on, files, convergence, implementation
+3. Compute execution waves from dependency graph:
+   - Wave 1: tasks with no dependencies
+   - Wave N: tasks whose all deps are in waves 1..N-1
+   - Force-assign if circular (break at lowest-numbered task)
+4. Load prior phase summaries for cross-task context
+
+## Phase 3: Wave-Based Implementation
+
+Execute waves sequentially, tasks within each wave can be parallel.
+
+**Strategy selection**:
+
+| Task Count | Strategy |
+|------------|----------|
+| <= 2 | Direct: inline Edit/Write |
+| 3-5 | Single CLI tool call for all |
+| > 5 | Batch: one CLI tool call per module group |
+
+**Per task**:
+1. Build prompt from task JSON: description, files, implementation steps, convergence criteria
+2. Include prior summaries and wisdom as context
+3. Delegate to CLI tool:
+   ```
+   Bash({
+     command: `ccw cli -p "PURPOSE: Implement task ${taskId}: ${description}
+   TASK: ${implementationSteps}
+   MODE: write
+   CONTEXT: @${files.join(' @')} | Memory: ${priorSummaries}
+   EXPECTED: Working code changes matching convergence criteria
+   CONSTRAINTS: ${convergenceCriteria}" --tool gemini --mode write`
+   })
+   ```
+4. Write `<session>/phase-{N}/summary-{IMPL-ID}.md` with: task ID, affected files, changes made, status
+
+**Between waves**: report wave progress via team_msg (type: exec_progress)
+
+## Phase 4: Self-Validation
+
+| Check | Method | Pass Criteria |
+|-------|--------|---------------|
+| Affected files exist | `test -f <path>` for each file in summary | All present |
+| TypeScript syntax | `npx tsc --noEmit` (if tsconfig.json exists) | No errors |
+| Lint | `npm run lint` (best-effort) | No critical errors |
+
+Log errors via team_msg but do NOT fix — verifier handles gap detection.

package/.codex/skills/team-roadmap-dev/roles/planner/role.md

@@ -1,76 +1,76 @@
----
-role: planner
-prefix: PLAN
-inner_loop: true
-cli_tools:
-  - gemini --mode analysis
-message_types:
-  success: plan_ready
-  progress: plan_progress
-  error: error
----
-
-# Planner
-
-Research and plan creation per roadmap phase. Gathers codebase context via CLI exploration, then generates wave-based execution plans with convergence criteria via CLI planning tool.
-
-## Phase 2: Context Loading + Research
-
-| Input | Source | Required |
-|-------|--------|----------|
-| roadmap.md | <session>/roadmap.md | Yes |
-| config.json | <session>/config.json | Yes |
-| Prior summaries | <session>/phase-{1..N-1}/summary-*.md | No |
-| Wisdom | <session>/wisdom/ | No |
-
-1. Read roadmap.md, extract phase goal, requirements (REQ-IDs), success criteria
-2. Read config.json for depth setting (quick/standard/comprehensive)
-3. Load prior phase summaries for dependency context
-4. Detect gap closure mode (task description contains "Gap closure")
-5. Launch CLI exploration with phase requirements as exploration query:
-   ```
-   Bash({
-     command: `ccw cli -p "PURPOSE: Explore codebase for phase requirements
-   TASK: • Identify files needing modification • Map patterns and dependencies • Assess test infrastructure • Identify risks
-   MODE: analysis
-   CONTEXT: @**/* | Memory: Phase goal: ${phaseGoal}
-   EXPECTED: Structured exploration results with file lists, patterns, risks
-   CONSTRAINTS: Read-only analysis" --tool gemini --mode analysis`
-   })
-   ```
-   - Target: files needing modification, patterns, dependencies, test infrastructure, risks
-6. If depth=comprehensive: run Gemini CLI analysis (`--mode analysis --rule analysis-analyze-code-patterns`)
-7. Write `<session>/phase-{N}/context.md` combining roadmap requirements + exploration results
-
-## Phase 3: Plan Creation
-
-1. Load context.md from Phase 2
-2. Create output directory: `<session>/phase-{N}/.task/`
-3. Delegate to CLI planning tool with:
-   ```
-   Bash({
-     command: `ccw cli -p "PURPOSE: Generate wave-based execution plan for phase ${phaseNum}
-   TASK: • Break down requirements into tasks • Define convergence criteria • Build dependency graph • Assign waves
-   MODE: write
-   CONTEXT: @${contextMd} | Memory: ${priorSummaries}
-   EXPECTED: IMPL_PLAN.md + IMPL-*.json files + TODO_LIST.md
-   CONSTRAINTS: <= 10 tasks | Valid DAG | Measurable convergence criteria" --tool gemini --mode write`
-   })
-   ```
-4. CLI tool produces: `IMPL_PLAN.md`, `.task/IMPL-*.json`, `TODO_LIST.md`
-5. If gap closure: only create tasks for gaps, starting from next available ID
-
-## Phase 4: Self-Validation
-
-| Check | Pass Criteria | Action on Failure |
-|-------|---------------|-------------------|
-| Task JSON files exist | >= 1 IMPL-*.json found | Error to coordinator |
-| Required fields | id, title, description, files, implementation, convergence | Log warning |
-| Convergence criteria | Each task has >= 1 criterion | Log warning |
-| No self-dependency | task.id not in task.depends_on | Log error, remove cycle |
-| All deps valid | Every depends_on ID exists | Log warning |
-| IMPL_PLAN.md exists | File present | Generate minimal version from task JSONs |
-
-After validation, compute wave structure from dependency graph for reporting:
-- Wave count = topological layers of DAG
-- Report: task count, wave count, file list
+---
+role: planner
+prefix: PLAN
+inner_loop: true
+cli_tools:
+  - gemini --mode analysis
+message_types:
+  success: plan_ready
+  progress: plan_progress
+  error: error
+---
+
+# Planner
+
+Research and plan creation per roadmap phase. Gathers codebase context via CLI exploration, then generates wave-based execution plans with convergence criteria via CLI planning tool.
+
+## Phase 2: Context Loading + Research
+
+| Input | Source | Required |
+|-------|--------|----------|
+| roadmap.md | <session>/roadmap.md | Yes |
+| config.json | <session>/config.json | Yes |
+| Prior summaries | <session>/phase-{1..N-1}/summary-*.md | No |
+| Wisdom | <session>/wisdom/ | No |
+
+1. Read roadmap.md, extract phase goal, requirements (REQ-IDs), success criteria
+2. Read config.json for depth setting (quick/standard/comprehensive)
+3. Load prior phase summaries for dependency context
+4. Detect gap closure mode (task description contains "Gap closure")
+5. Launch CLI exploration with phase requirements as exploration query:
+   ```
+   Bash({
+     command: `ccw cli -p "PURPOSE: Explore codebase for phase requirements
+   TASK: • Identify files needing modification • Map patterns and dependencies • Assess test infrastructure • Identify risks
+   MODE: analysis
+   CONTEXT: @**/* | Memory: Phase goal: ${phaseGoal}
+   EXPECTED: Structured exploration results with file lists, patterns, risks
+   CONSTRAINTS: Read-only analysis" --tool gemini --mode analysis`
+   })
+   ```
+   - Target: files needing modification, patterns, dependencies, test infrastructure, risks
+6. If depth=comprehensive: run Gemini CLI analysis (`--mode analysis --rule analysis-analyze-code-patterns`)
+7. Write `<session>/phase-{N}/context.md` combining roadmap requirements + exploration results
+
+## Phase 3: Plan Creation
+
+1. Load context.md from Phase 2
+2. Create output directory: `<session>/phase-{N}/.task/`
+3. Delegate to CLI planning tool with:
+   ```
+   Bash({
+     command: `ccw cli -p "PURPOSE: Generate wave-based execution plan for phase ${phaseNum}
+   TASK: • Break down requirements into tasks • Define convergence criteria • Build dependency graph • Assign waves
+   MODE: write
+   CONTEXT: @${contextMd} | Memory: ${priorSummaries}
+   EXPECTED: IMPL_PLAN.md + IMPL-*.json files + TODO_LIST.md
+   CONSTRAINTS: <= 10 tasks | Valid DAG | Measurable convergence criteria" --tool gemini --mode write`
+   })
+   ```
+4. CLI tool produces: `IMPL_PLAN.md`, `.task/IMPL-*.json`, `TODO_LIST.md`
+5. If gap closure: only create tasks for gaps, starting from next available ID
+
+## Phase 4: Self-Validation
+
+| Check | Pass Criteria | Action on Failure |
+|-------|---------------|-------------------|
+| Task JSON files exist | >= 1 IMPL-*.json found | Error to coordinator |
+| Required fields | id, title, description, files, implementation, convergence | Log warning |
+| Convergence criteria | Each task has >= 1 criterion | Log warning |
+| No self-dependency | task.id not in task.depends_on | Log error, remove cycle |
+| All deps valid | Every depends_on ID exists | Log warning |
+| IMPL_PLAN.md exists | File present | Generate minimal version from task JSONs |
+
+After validation, compute wave structure from dependency graph for reporting:
+- Wave count = topological layers of DAG
+- Report: task count, wave count, file list

package/.codex/skills/team-roadmap-dev/roles/verifier/role.md

@@ -1,74 +1,74 @@
----
-role: verifier
-prefix: VERIFY
-inner_loop: true
-cli_tools:
-  - gemini --mode analysis
-message_types:
-  success: verify_passed
-  failure: gaps_found
-  error: error
----
-
-# Verifier
-
-Goal-backward verification per phase. Reads convergence criteria from IMPL-*.json task files and checks against actual codebase state. Read-only — never modifies code. Produces verification.md with pass/fail and structured gap lists.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task JSONs | <session>/phase-{N}/.task/IMPL-*.json | Yes |
-| Summaries | <session>/phase-{N}/summary-*.md | Yes |
-| Wisdom | <session>/wisdom/ | No |
-
-1. Glob IMPL-*.json files, extract convergence criteria from each task
-2. Glob summary-*.md files, parse frontmatter (task, affects, provides)
-3. If no task JSONs or summaries found → error to coordinator
-
-## Phase 3: Goal-Backward Verification
-
-For each task's convergence criteria, execute appropriate check:
-
-| Criteria Type | Method |
-|---------------|--------|
-| File existence | `test -f <path>` |
-| Command execution | Run command, check exit code |
-| Pattern match | Grep for pattern in specified files |
-| Semantic check | Optional: Gemini CLI (`--mode analysis --rule analysis-review-code-quality`) |
-
-**Per task scoring**:
-
-| Result | Condition |
-|--------|-----------|
-| pass | All criteria met |
-| partial | Some criteria met |
-| fail | No criteria met or critical check failed |
-
-Collect all gaps from partial/failed tasks with structured format:
-- task ID, criteria type, expected value, actual value
-
-## Phase 4: Compile Results
-
-1. Aggregate per-task results: count passed, partial, failed
-2. Determine overall status:
-   - `passed` if gaps.length === 0
-   - `gaps_found` otherwise
-3. Write `<session>/phase-{N}/verification.md`:
-
-```yaml
----
-phase: <N>
-status: passed | gaps_found
-tasks_checked: <count>
-tasks_passed: <count>
-gaps:
-  - task: "<task-id>"
-    type: "<criteria-type>"
-    item: "<description>"
-    expected: "<expected>"
-    actual: "<actual>"
----
-```
-
-4. Update .msg/meta.json with verification summary
+---
+role: verifier
+prefix: VERIFY
+inner_loop: true
+cli_tools:
+  - gemini --mode analysis
+message_types:
+  success: verify_passed
+  failure: gaps_found
+  error: error
+---
+
+# Verifier
+
+Goal-backward verification per phase. Reads convergence criteria from IMPL-*.json task files and checks against actual codebase state. Read-only — never modifies code. Produces verification.md with pass/fail and structured gap lists.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task JSONs | <session>/phase-{N}/.task/IMPL-*.json | Yes |
+| Summaries | <session>/phase-{N}/summary-*.md | Yes |
+| Wisdom | <session>/wisdom/ | No |
+
+1. Glob IMPL-*.json files, extract convergence criteria from each task
+2. Glob summary-*.md files, parse frontmatter (task, affects, provides)
+3. If no task JSONs or summaries found → error to coordinator
+
+## Phase 3: Goal-Backward Verification
+
+For each task's convergence criteria, execute appropriate check:
+
+| Criteria Type | Method |
+|---------------|--------|
+| File existence | `test -f <path>` |
+| Command execution | Run command, check exit code |
+| Pattern match | Grep for pattern in specified files |
+| Semantic check | Optional: Gemini CLI (`--mode analysis --rule analysis-review-code-quality`) |
+
+**Per task scoring**:
+
+| Result | Condition |
+|--------|-----------|
+| pass | All criteria met |
+| partial | Some criteria met |
+| fail | No criteria met or critical check failed |
+
+Collect all gaps from partial/failed tasks with structured format:
+- task ID, criteria type, expected value, actual value
+
+## Phase 4: Compile Results
+
+1. Aggregate per-task results: count passed, partial, failed
+2. Determine overall status:
+   - `passed` if gaps.length === 0
+   - `gaps_found` otherwise
+3. Write `<session>/phase-{N}/verification.md`:
+
+```yaml
+---
+phase: <N>
+status: passed | gaps_found
+tasks_checked: <count>
+tasks_passed: <count>
+gaps:
+  - task: "<task-id>"
+    type: "<criteria-type>"
+    item: "<description>"
+    expected: "<expected>"
+    actual: "<actual>"
+---
+```
+
+4. Update .msg/meta.json with verification summary

package/.codex/skills/team-roadmap-dev/specs/pipelines.md

@@ -1,93 +1,93 @@
-# Pipeline Definitions — Team Roadmap Dev
-
-## Pipeline Mode
-
-### Single Phase Pipeline
-
-```
-PLAN-101 --> EXEC-101 --> VERIFY-101
-[planner]    [executor]   [verifier]
-                              |
-                         gap found?
-                         YES (< 3x)
-                              |
-                         PLAN-102 --> EXEC-102 --> VERIFY-102
-                              |
-                         gap found?
-                         YES (>= 3x) -> AskUser: continue/retry/stop
-                         NO -> Complete
-```
-
-### Multi-Phase Pipeline
-
-```
-Phase 1: PLAN-101 --> EXEC-101 --> VERIFY-101
-                                      |
-                               [gap closure loop]
-                                      |
-                               Phase 1 passed
-                                      |
-Phase 2: PLAN-201 --> EXEC-201 --> VERIFY-201
-                                      |
-                               [gap closure loop]
-                                      |
-                               Phase 2 passed
-                                      |
-Phase N: PLAN-N01 --> EXEC-N01 --> VERIFY-N01
-                                      |
-                               [gap closure loop]
-                                      |
-                               All phases done -> Complete
-```
-
-## Task Metadata Registry
-
-| Task ID | Role | Phase | Dependencies | Description |
-|---------|------|-------|-------------|-------------|
-| PLAN-N01 | planner | phase N | (none or previous VERIFY) | Context research + IMPL-*.json task generation |
-| EXEC-N01 | executor | phase N | PLAN-N01 | Wave-based code implementation following IMPL-*.json plans |
-| VERIFY-N01 | verifier | phase N | EXEC-N01 | Convergence criteria check + gap detection |
-| PLAN-N02 | planner | phase N (gap closure 1) | VERIFY-N01 | Gap-targeted re-plan |
-| EXEC-N02 | executor | phase N (gap closure 1) | PLAN-N02 | Gap fix execution |
-| VERIFY-N02 | verifier | phase N (gap closure 1) | EXEC-N02 | Re-verify after gap fixes |
-
-## Task Naming Rules
-
-| Type | Pattern | Example |
-|------|---------|---------|
-| Plan | `PLAN-{phase}01` | PLAN-101, PLAN-201 |
-| Execute | `EXEC-{phase}01` | EXEC-101, EXEC-201 |
-| Verify | `VERIFY-{phase}01` | VERIFY-101 |
-| Gap Plan | `PLAN-{phase}{iteration+1}` | PLAN-102 (gap 1), PLAN-103 (gap 2) |
-| Gap Execute | `EXEC-{phase}{iteration+1}` | EXEC-102, EXEC-103 |
-| Gap Verify | `VERIFY-{phase}{iteration+1}` | VERIFY-102, VERIFY-103 |
-
-## Checkpoints
-
-| Checkpoint | Trigger | Behavior |
-|------------|---------|----------|
-| Plan gate (optional) | PLAN-N01 complete | If `config.gates.plan_check=true`: AskUser to approve/revise/skip |
-| Phase transition | VERIFY-N01 complete, no gaps | If `config.mode=interactive`: AskUser to proceed/review/stop |
-| Gap closure | VERIFY-N01 complete, gaps found | Auto-create PLAN-N02/EXEC-N02/VERIFY-N02 (max 3 iterations) |
-| Gap limit | gap_iteration >= 3 | AskUser: continue anyway / retry once more / stop |
-| Pipeline complete | All phases passed | AskUser: archive & clean / keep active / export results |
-
-## State Machine Coordinates
-
-```json
-{
-  "current_phase": 1,
-  "total_phases": 3,
-  "gap_iteration": 0,
-  "step": "plan | exec | verify | gap_closure | transition",
-  "status": "running | paused | complete"
-}
-```
-
-## Role-Worker Map
-
-| Prefix | Role | Role Spec | Inner Loop |
-|--------|------|-----------|------------|
-| PLAN | planner | `~  or <project>/.claude/skills/team-roadmap-dev/roles/planner/role.md` | true |
-| EXEC | executor | `~  or <project>/.claude/skills/team-roadmap-dev/roles/executor/role.md` | true |
-| VERIFY | verifier | `~  or <project>/.claude/skills/team-roadmap-dev/roles/verifier/role.md` | true |
+# Pipeline Definitions — Team Roadmap Dev
+
+## Pipeline Mode
+
+### Single Phase Pipeline
+
+```
+PLAN-101 --> EXEC-101 --> VERIFY-101
+[planner]    [executor]   [verifier]
+                              |
+                         gap found?
+                         YES (< 3x)
+                              |
+                         PLAN-102 --> EXEC-102 --> VERIFY-102
+                              |
+                         gap found?
+                         YES (>= 3x) -> AskUser: continue/retry/stop
+                         NO -> Complete
+```
+
+### Multi-Phase Pipeline
+
+```
+Phase 1: PLAN-101 --> EXEC-101 --> VERIFY-101
+                                      |
+                               [gap closure loop]
+                                      |
+                               Phase 1 passed
+                                      |
+Phase 2: PLAN-201 --> EXEC-201 --> VERIFY-201
+                                      |
+                               [gap closure loop]
+                                      |
+                               Phase 2 passed
+                                      |
+Phase N: PLAN-N01 --> EXEC-N01 --> VERIFY-N01
+                                      |
+                               [gap closure loop]
+                                      |
+                               All phases done -> Complete
+```
+
+## Task Metadata Registry
+
+| Task ID | Role | Phase | Dependencies | Description |
+|---------|------|-------|-------------|-------------|
+| PLAN-N01 | planner | phase N | (none or previous VERIFY) | Context research + IMPL-*.json task generation |
+| EXEC-N01 | executor | phase N | PLAN-N01 | Wave-based code implementation following IMPL-*.json plans |
+| VERIFY-N01 | verifier | phase N | EXEC-N01 | Convergence criteria check + gap detection |
+| PLAN-N02 | planner | phase N (gap closure 1) | VERIFY-N01 | Gap-targeted re-plan |
+| EXEC-N02 | executor | phase N (gap closure 1) | PLAN-N02 | Gap fix execution |
+| VERIFY-N02 | verifier | phase N (gap closure 1) | EXEC-N02 | Re-verify after gap fixes |
+
+## Task Naming Rules
+
+| Type | Pattern | Example |
+|------|---------|---------|
+| Plan | `PLAN-{phase}01` | PLAN-101, PLAN-201 |
+| Execute | `EXEC-{phase}01` | EXEC-101, EXEC-201 |
+| Verify | `VERIFY-{phase}01` | VERIFY-101 |
+| Gap Plan | `PLAN-{phase}{iteration+1}` | PLAN-102 (gap 1), PLAN-103 (gap 2) |
+| Gap Execute | `EXEC-{phase}{iteration+1}` | EXEC-102, EXEC-103 |
+| Gap Verify | `VERIFY-{phase}{iteration+1}` | VERIFY-102, VERIFY-103 |
+
+## Checkpoints
+
+| Checkpoint | Trigger | Behavior |
+|------------|---------|----------|
+| Plan gate (optional) | PLAN-N01 complete | If `config.gates.plan_check=true`: AskUser to approve/revise/skip |
+| Phase transition | VERIFY-N01 complete, no gaps | If `config.mode=interactive`: AskUser to proceed/review/stop |
+| Gap closure | VERIFY-N01 complete, gaps found | Auto-create PLAN-N02/EXEC-N02/VERIFY-N02 (max 3 iterations) |
+| Gap limit | gap_iteration >= 3 | AskUser: continue anyway / retry once more / stop |
+| Pipeline complete | All phases passed | AskUser: archive & clean / keep active / export results |
+
+## State Machine Coordinates
+
+```json
+{
+  "current_phase": 1,
+  "total_phases": 3,
+  "gap_iteration": 0,
+  "step": "plan | exec | verify | gap_closure | transition",
+  "status": "running | paused | complete"
+}
+```
+
+## Role-Worker Map
+
+| Prefix | Role | Role Spec | Inner Loop |
+|--------|------|-----------|------------|
+| PLAN | planner | `~  or <project>/.claude/skills/team-roadmap-dev/roles/planner/role.md` | true |
+| EXEC | executor | `~  or <project>/.claude/skills/team-roadmap-dev/roles/executor/role.md` | true |
+| VERIFY | verifier | `~  or <project>/.claude/skills/team-roadmap-dev/roles/verifier/role.md` | true |