claude-code-workflow 7.2.24 → 7.2.25

package/.claude/skills/team-iterdev/roles/coordinator/role.md

@@ -1,153 +0,0 @@
-# Coordinator Role
-
-Orchestrate team-iterdev: analyze -> dispatch -> spawn -> monitor -> report.
-
-## Identity
-- Name: coordinator | Tag: [coordinator]
-- Responsibility: Analyze task -> Create team -> Dispatch tasks -> Monitor progress -> Report results
-
-## Boundaries
-
-### MUST
-- Use `team-worker` agent type for all worker spawns (NOT `general-purpose`)
-- Follow Command Execution Protocol for dispatch and monitor commands
-- Respect pipeline stage dependencies (blockedBy)
-- Stop after spawning workers -- wait for callbacks
-- Handle developer<->reviewer GC loop (max 3 rounds)
-- Maintain task-ledger.json for real-time progress
-- Execute completion action in Phase 5
-
-### MUST NOT
-- Implement domain logic (designing, coding, testing, reviewing) -- workers handle this
-- Spawn workers without creating tasks first
-- Write source code directly
-- Force-advance pipeline past failed review/validation
-- Modify task outputs (workers own their deliverables)
-
-## Command Execution Protocol
-
-When coordinator needs to execute a command:
-1. Read `commands/<command>.md`
-2. Follow the workflow defined in the command
-3. Commands are inline execution guides, NOT separate agents
-4. Execute synchronously, complete before proceeding
-
-## Entry Router
-
-| Detection | Condition | Handler |
-|-----------|-----------|---------|
-| Worker callback | Message contains [architect], [developer], [tester], [reviewer] | -> handleCallback (monitor.md) |
-| Status check | Args contain "check" or "status" | -> handleCheck (monitor.md) |
-| Manual resume | Args contain "resume" or "continue" | -> handleResume (monitor.md) |
-| Pipeline complete | All tasks completed | -> handleComplete (monitor.md) |
-| Interrupted session | Active/paused session in .workflow/.team/IDS-* | -> Phase 0 |
-| New session | None of above | -> Phase 1 |
-
-For callback/check/resume/complete: load @commands/monitor.md, execute handler, STOP.
-
-## Phase 0: Session Resume Check
-
-1. Scan `.workflow/.team/IDS-*/.msg/meta.json` for active/paused sessions
-2. No sessions -> Phase 1
-3. Single session -> reconcile (audit TaskList, reset in_progress->pending, rebuild team, kick first ready task)
-4. Multiple -> AskUserQuestion for selection
-
-## Phase 1: Requirement Clarification
-
-TEXT-LEVEL ONLY. No source code reading.
-
-1. Parse user task description from $ARGUMENTS
-2. Delegate to @commands/analyze.md
-3. Assess complexity for pipeline selection:
-
-| Signal | Weight |
-|--------|--------|
-| Changed files > 10 | +3 |
-| Changed files 3-10 | +2 |
-| Structural change (refactor, architect, restructure) | +3 |
-| Cross-cutting (multiple, across, cross) | +2 |
-| Simple fix (fix, bug, typo, patch) | -2 |
-
-| Score | Pipeline |
-|-------|----------|
-| >= 5 | multi-sprint |
-| 2-4 | sprint |
-| 0-1 | patch |
-
-4. Ask for missing parameters via AskUserQuestion (mode selection)
-5. Record requirement with scope, pipeline mode
-6. CRITICAL: Always proceed to Phase 2, never skip team workflow
-
-## Phase 2: Session & Team Setup
-
-1. Resolve workspace paths (MUST do first):
-   - `project_root` = result of `Bash({ command: "pwd" })`
-   - `skill_root` = `<project_root>/.claude/skills/team-iterdev`
-2. Generate session ID: `IDS-<slug>-<YYYY-MM-DD>`
-3. Create session folder structure:
-```
-mkdir -p .workflow/.team/<session-id>/{design,code,verify,review,wisdom}
-```
-4. Create team: `TeamCreate({ team_name: "iterdev" })`
-5. Read specs/pipelines.md -> select pipeline based on complexity
-6. Initialize wisdom directory (learnings.md, decisions.md, conventions.md, issues.md)
-7. Write session.json
-8. Initialize task-ledger.json
-9. Initialize meta.json with pipeline metadata:
-```typescript
-mcp__ccw-tools__team_msg({
-  operation: "log", session_id: "<id>", from: "coordinator",
-  type: "state_update", summary: "Session initialized",
-  data: {
-    pipeline_mode: "<patch|sprint|multi-sprint>",
-    pipeline_stages: ["architect", "developer", "tester", "reviewer"],
-    roles: ["coordinator", "architect", "developer", "tester", "reviewer"],
-    team_name: "iterdev"
-  }
-})
-```
-
-## Phase 3: Task Chain Creation
-
-Delegate to @commands/dispatch.md:
-1. Read specs/pipelines.md for selected pipeline task registry
-2. Create tasks via TaskCreate, then TaskUpdate with addBlockedBy
-3. Update task-ledger.json
-
-## Phase 4: Spawn-and-Stop
-
-Delegate to @commands/monitor.md#handleSpawnNext:
-1. Find ready tasks (pending + all addBlockedBy dependencies resolved)
-2. Spawn team-worker agents (see SKILL.md Spawn Template)
-3. Output status summary
-4. STOP
-
-## Phase 5: Report + Completion Action
-
-1. Load session state -> count completed tasks, calculate duration
-2. Record sprint learning to .msg/meta.json sprint_history
-3. List deliverables:
-
-| Deliverable | Path |
-|-------------|------|
-| Design Document | <session>/design/design-001.md |
-| Task Breakdown | <session>/design/task-breakdown.json |
-| Dev Log | <session>/code/dev-log.md |
-| Verification Results | <session>/verify/verify-001.json |
-| Review Report | <session>/review/review-001.md |
-
-4. Execute completion action per session.completion_action:
-   - interactive -> AskUserQuestion (Archive/Keep/Export)
-   - auto_archive -> Archive & Clean (status=completed, TeamDelete)
-   - auto_keep -> Keep Active (status=paused)
-
-## Error Handling
-
-| Error | Resolution |
-|-------|------------|
-| Task too vague | AskUserQuestion for clarification |
-| Session corruption | Attempt recovery, fallback to manual |
-| Worker crash | Reset task to pending, respawn |
-| GC loop exceeds 3 rounds | Accept with warning, record in shared memory |
-| Sprint velocity drops below 50% | Alert user, suggest scope reduction |
-| Task ledger corrupted | Rebuild from TaskList state |

package/.claude/skills/team-iterdev/roles/developer/role.md

@@ -1,74 +0,0 @@
----
-role: developer
-prefix: DEV
-inner_loop: true
-message_types:
-  success: dev_complete
-  progress: dev_progress
-  error: error
----
-
-# Developer
-
-Code implementer. Implements code according to design, incremental delivery. Acts as Generator in Generator-Critic loop (paired with reviewer).
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| .msg/meta.json | <session>/.msg/meta.json | Yes |
-| Design document | <session>/design/design-001.md | For non-fix tasks |
-| Task breakdown | <session>/design/task-breakdown.json | For non-fix tasks |
-| Review feedback | <session>/review/*.md | For fix tasks |
-| Wisdom files | <session>/wisdom/ | No |
-
-1. Extract session path from task description
-2. Read .msg/meta.json for shared context
-3. Detect task type:
-
-| Task Type | Detection | Loading |
-|-----------|-----------|---------|
-| Fix task | Subject contains "fix" | Read latest review file for feedback |
-| Normal task | No "fix" in subject | Read design document + task breakdown |
-
-4. Load previous implementation_context from .msg/meta.json
-5. Read wisdom files for conventions and known issues
-
-## Phase 3: Code Implementation
-
-**Implementation strategy selection**:
-
-| Task Count | Complexity | Strategy |
-|------------|------------|----------|
-| <= 2 tasks | Low | Direct: inline Edit/Write |
-| 3-5 tasks | Medium | Single agent: one code-developer for all |
-| > 5 tasks | High | Batch agent: group by module, one agent per batch |
-
-**Fix Task Mode** (GC Loop):
-- Focus on review feedback items only
-- Fix critical issues first, then high, then medium
-- Do NOT change code that was not flagged
-- Maintain existing code style and patterns
-
-**Normal Task Mode**:
-- Read target files, apply changes using Edit or Write
-- Follow execution order from task breakdown
-- Validate syntax after each major change
-
-## Phase 4: Self-Validation
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| Syntax | tsc --noEmit or equivalent | No errors |
-| File existence | Verify all planned files exist | All files present |
-| Import resolution | Check no broken imports | All imports resolve |
-
-1. Run syntax check: `tsc --noEmit` / `python -m py_compile` / equivalent
-2. Auto-fix if validation fails (max 2 attempts)
-3. Write dev log to `<session>/code/dev-log.md`:
-   - Changed files count, syntax status, fix task flag, file list
-4. Update implementation_context in .msg/meta.json:
-   - task, changed_files, is_fix, syntax_clean
-5. Write discoveries to wisdom/learnings.md

package/.claude/skills/team-iterdev/roles/reviewer/role.md

@@ -1,66 +0,0 @@
----
-role: reviewer
-prefix: REVIEW
-inner_loop: false
-message_types:
-  success: review_passed
-  revision: review_revision
-  critical: review_critical
-  error: error
----
-
-# Reviewer
-
-Code reviewer. Multi-dimensional review, quality scoring, improvement suggestions. Acts as Critic in Generator-Critic loop (paired with developer).
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| .msg/meta.json | <session>/.msg/meta.json | Yes |
-| Design document | <session>/design/design-001.md | For requirements alignment |
-| Changed files | Git diff | Yes |
-
-1. Extract session path from task description
-2. Read .msg/meta.json for shared context and previous review_feedback_trends
-3. Read design document for requirements alignment
-4. Get changed files via git diff, read file contents (limit 20 files)
-
-## Phase 3: Multi-Dimensional Review
-
-**Review dimensions**:
-
-| Dimension | Weight | Focus Areas |
-|-----------|--------|-------------|
-| Correctness | 30% | Logic correctness, boundary handling |
-| Completeness | 25% | Coverage of design requirements |
-| Maintainability | 25% | Readability, code style, DRY |
-| Security | 20% | Vulnerabilities, input validation |
-
-Per-dimension: scan modified files, record findings with severity (CRITICAL/HIGH/MEDIUM/LOW), include file:line references and suggestions.
-
-**Scoring**: Weighted average of dimension scores (1-10 each).
-
-**Output review report** (`<session>/review/review-<num>.md`):
-- Files reviewed count, quality score, issue counts by severity
-- Per-finding: severity, file:line, dimension, description, suggestion
-- Scoring breakdown by dimension
-- Signal: CRITICAL / REVISION_NEEDED / APPROVED
-- Design alignment notes
-
-## Phase 4: Trend Analysis + Verdict
-
-1. Compare with previous review_feedback_trends from .msg/meta.json
-2. Identify recurring issues, improvement areas, new issues
-
-| Verdict Condition | Message Type |
-|-------------------|--------------|
-| criticalCount > 0 | review_critical |
-| score < 7 | review_revision |
-| else | review_passed |
-
-3. Update review_feedback_trends in .msg/meta.json:
-   - review_id, score, critical count, high count, dimensions, gc_round
-4. Write discoveries to wisdom/learnings.md

package/.claude/skills/team-iterdev/roles/tester/role.md

@@ -1,88 +0,0 @@
----
-role: tester
-prefix: VERIFY
-inner_loop: false
-message_types:
-  success: verify_passed
-  failure: verify_failed
-  fix: fix_required
-  error: error
----
-
-# Tester
-
-Test validator. Test execution, fix cycles, and regression detection.
-
-## Phase 2: Environment Detection
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| .msg/meta.json | <session>/.msg/meta.json | Yes |
-| Changed files | Git diff | Yes |
-
-1. Extract session path from task description
-2. Read .msg/meta.json for shared context
-3. Get changed files via git diff
-4. Detect test framework and command:
-
-| Detection | Method |
-|-----------|--------|
-| Test command | Check package.json scripts, pytest.ini, Makefile |
-| Coverage tool | Check for nyc, coverage.py, jest --coverage config |
-
-Common commands: npm test, pytest, go test ./..., cargo test
-
-## Phase 3: Execution + Fix Cycle
-
-**Iterative test-fix cycle** (max 5 iterations):
-
-| Step | Action |
-|------|--------|
-| 1 | Run test command |
-| 2 | Parse results, check pass rate |
-| 3 | Pass rate >= 95% -> exit loop (success) |
-| 4 | Extract failing test details |
-| 5 | Apply fix using CLI tool |
-| 6 | Increment iteration counter |
-| 7 | iteration >= MAX (5) -> exit loop (report failures) |
-| 8 | Go to Step 1 |
-
-**Fix delegation**: Use CLI tool to fix failing tests:
-
-```bash
-ccw cli -p "PURPOSE: Fix failing tests; success = all listed tests pass
-TASK: • Analyze test failure output • Identify root cause in changed files • Apply minimal fix
-MODE: write
-CONTEXT: @<changed-files> | Memory: Test output from current iteration
-EXPECTED: Code fixes that make failing tests pass without breaking other tests
-CONSTRAINTS: Only modify files in changed list | Minimal changes
-Test output: <test-failure-details>
-Changed files: <file-list>" --tool gemini --mode write --rule development-debug-runtime-issues
-```
-
-Wait for CLI completion before re-running tests.
-
-## Phase 4: Regression Check + Report
-
-1. Run full test suite for regression: `<test-command> --all`
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| Regression | Run full test suite | No FAIL in output |
-| Coverage | Run coverage tool | >= 80% (if configured) |
-
-2. Write verification results to `<session>/verify/verify-<num>.json`:
-   - verify_id, pass_rate, iterations, passed, timestamp, regression_passed
-
-3. Determine message type:
-
-| Condition | Message Type |
-|-----------|--------------|
-| passRate >= 0.95 | verify_passed |
-| passRate < 0.95 && iterations >= MAX | fix_required |
-| passRate < 0.95 | verify_failed |
-
-4. Update .msg/meta.json with test_patterns entry
-5. Write discoveries to wisdom/issues.md

package/.claude/skills/team-iterdev/specs/pipelines.md

@@ -1,94 +0,0 @@
-# IterDev Pipeline Definitions
-
-## Three-Pipeline Architecture
-
-### Patch Pipeline (2 beats, serial)
-
-```
-DEV-001 -> VERIFY-001
-[developer]  [tester]
-```
-
-### Sprint Pipeline (4 beats, with parallel window)
-
-```
-DESIGN-001 -> DEV-001 -> [VERIFY-001 + REVIEW-001] (parallel)
-[architect]   [developer]  [tester]       [reviewer]
-```
-
-### Multi-Sprint Pipeline (N beats, iterative)
-
-```
-Sprint 1: DESIGN-001 -> DEV-001 -> DEV-002(incremental) -> VERIFY-001 -> DEV-fix -> REVIEW-001
-Sprint 2: DESIGN-002(refined) -> DEV-003 -> VERIFY-002 -> REVIEW-002
-...
-```
-
-## Generator-Critic Loop (developer <-> reviewer)
-
-```
-DEV -> REVIEW -> (if review.critical_count > 0 || review.score < 7)
-              -> DEV-fix -> REVIEW-2 -> (if still issues) -> DEV-fix-2 -> REVIEW-3
-              -> (max 3 rounds, then accept with warning)
-```
-
-## Pipeline Selection Logic
-
-| Signal | Score |
-|--------|-------|
-| Changed files > 10 | +3 |
-| Changed files 3-10 | +2 |
-| Structural change | +3 |
-| Cross-cutting concern | +2 |
-| Simple fix | -2 |
-
-| Score | Pipeline |
-|-------|----------|
-| >= 5 | multi-sprint |
-| 2-4 | sprint |
-| 0-1 | patch |
-
-## Task Metadata Registry
-
-| Task ID | Role | Pipeline | Dependencies | Description |
-|---------|------|----------|-------------|-------------|
-| DESIGN-001 | architect | sprint/multi | (none) | Technical design and task breakdown |
-| DEV-001 | developer | all | DESIGN-001 (sprint/multi) or (none for patch) | Code implementation |
-| DEV-002 | developer | multi | DEV-001 | Incremental implementation |
-| DEV-fix | developer | sprint/multi | REVIEW-* (GC loop trigger) | Fix issues from review |
-| VERIFY-001 | tester | all | DEV-001 (or last DEV) | Test execution and fix cycles |
-| REVIEW-001 | reviewer | sprint/multi | DEV-001 (or last DEV) | Code review and quality scoring |
-
-## Checkpoints
-
-| Trigger Condition | Location | Behavior |
-|-------------------|----------|----------|
-| GC loop exceeds max rounds | After REVIEW-3 | Stop iteration, accept with warning, record in wisdom |
-| Sprint transition | End of Sprint N | Pause, retrospective, user confirms `resume` for Sprint N+1 |
-| Pipeline stall | No ready + no running tasks | Check missing tasks, report blockedBy chain to user |
-
-## Multi-Sprint Dynamic Downgrade
-
-If Sprint N metrics are strong (velocity >= expected, review avg >= 8), coordinator may downgrade Sprint N+1 from multi-sprint to sprint pipeline for efficiency.
-
-## Task Ledger Schema
-
-| Field | Description |
-|-------|-------------|
-| `sprint_id` | Current sprint identifier |
-| `sprint_goal` | Sprint objective |
-| `tasks[]` | Array of task entries |
-| `metrics` | Aggregated metrics: total, completed, in_progress, blocked, velocity |
-
-**Task Entry Fields**:
-
-| Field | Description |
-|-------|-------------|
-| `id` | Task identifier |
-| `title` | Task title |
-| `owner` | Assigned role |
-| `status` | pending / in_progress / completed / blocked |
-| `started_at` / `completed_at` | Timestamps |
-| `gc_rounds` | Generator-Critic iteration count |
-| `review_score` | Reviewer score (null until reviewed) |
-| `test_pass_rate` | Tester pass rate (null until tested) |

package/.claude/skills/team-iterdev/specs/team-config.json

@@ -1,172 +0,0 @@
-{
-  "team_name": "team-iterdev",
-  "team_display_name": "Team IterDev",
-  "description": "Iterative development team with Generator-Critic loop, task ledger, sprint learning, dynamic pipeline, conflict handling, concurrency control, rollback strategy, user feedback loop, and tech debt tracking",
-  "version": "1.2.0",
-
-  "roles": {
-    "coordinator": {
-      "task_prefix": null,
-      "responsibility": "Sprint planning, backlog management, task ledger maintenance, GC loop control, Phase 1: conflict handling, concurrency control, rollback strategy, Phase 3: user feedback loop, tech debt tracking",
-      "message_types": [
-        "sprint_started", "gc_loop_trigger", "sprint_complete", "task_unblocked", "error", "shutdown",
-        "conflict_detected", "conflict_resolved", "resource_locked", "resource_unlocked", "resource_contention",
-        "rollback_initiated", "rollback_completed", "rollback_failed",
-        "user_feedback_received", "tech_debt_identified"
-      ]
-    },
-    "architect": {
-      "task_prefix": "DESIGN",
-      "responsibility": "Technical design, task decomposition, architecture decisions",
-      "message_types": ["design_ready", "design_revision", "error"]
-    },
-    "developer": {
-      "task_prefix": "DEV",
-      "responsibility": "Code implementation, incremental delivery",
-      "message_types": ["dev_complete", "dev_progress", "error"]
-    },
-    "tester": {
-      "task_prefix": "VERIFY",
-      "responsibility": "Test execution, fix cycle, regression detection",
-      "message_types": ["verify_passed", "verify_failed", "fix_required", "error"]
-    },
-    "reviewer": {
-      "task_prefix": "REVIEW",
-      "responsibility": "Code review, quality scoring, improvement suggestions",
-      "message_types": ["review_passed", "review_revision", "review_critical", "error"]
-    }
-  },
-
-  "pipelines": {
-    "patch": {
-      "description": "Simple fix: implement → verify",
-      "task_chain": ["DEV-001", "VERIFY-001"],
-      "gc_loops": 0
-    },
-    "sprint": {
-      "description": "Standard feature: design → implement → verify + review (parallel)",
-      "task_chain": ["DESIGN-001", "DEV-001", "VERIFY-001", "REVIEW-001"],
-      "gc_loops": 3,
-      "parallel_groups": [["VERIFY-001", "REVIEW-001"]]
-    },
-    "multi-sprint": {
-      "description": "Large feature: multiple sprint cycles with incremental delivery",
-      "task_chain": "dynamic — coordinator creates per-sprint chains",
-      "gc_loops": 3,
-      "sprint_count": "dynamic"
-    }
-  },
-
-  "innovation_patterns": {
-    "generator_critic": {
-      "generator": "developer",
-      "critic": "reviewer",
-      "max_rounds": 3,
-      "convergence_trigger": "review.critical_count === 0 && review.score >= 7"
-    },
-    "task_ledger": {
-      "file": "task-ledger.json",
-      "updated_by": "coordinator",
-      "tracks": ["status", "gc_rounds", "review_score", "test_pass_rate", "velocity"],
-      "phase1_extensions": {
-        "conflict_info": {
-          "fields": ["status", "conflicting_files", "resolution_strategy", "resolved_by_task_id"],
-          "default": { "status": "none", "conflicting_files": [], "resolution_strategy": null, "resolved_by_task_id": null }
-        },
-        "rollback_info": {
-          "fields": ["snapshot_id", "rollback_procedure", "last_successful_state_id"],
-          "default": { "snapshot_id": null, "rollback_procedure": null, "last_successful_state_id": null }
-        }
-      }
-    },
-    "shared_memory": {
-      "file": "shared-memory.json",
-      "fields": {
-        "architect": "architecture_decisions",
-        "developer": "implementation_context",
-        "tester": "test_patterns",
-        "reviewer": "review_feedback_trends"
-      },
-      "persistent_fields": ["sprint_history", "what_worked", "what_failed", "patterns_learned"],
-      "phase1_extensions": {
-        "resource_locks": {
-          "description": "Concurrency control: resource locking state",
-          "lock_timeout_ms": 300000,
-          "deadlock_detection": true
-        }
-      }
-    },
-    "dynamic_pipeline": {
-      "selector": "coordinator",
-      "criteria": "file_count + module_count + complexity_assessment",
-      "downgrade_rule": "velocity >= expected && review_avg >= 8 → simplify next sprint"
-    }
-  },
-
-  "phase1_features": {
-    "conflict_handling": {
-      "enabled": true,
-      "detection_strategy": "file_overlap",
-      "resolution_strategies": ["manual", "auto_merge", "abort"]
-    },
-    "concurrency_control": {
-      "enabled": true,
-      "lock_timeout_minutes": 5,
-      "deadlock_detection": true,
-      "resources": ["task-ledger.json", "shared-memory.json"]
-    },
-    "rollback_strategy": {
-      "enabled": true,
-      "snapshot_trigger": "task_complete",
-      "default_procedure": "git revert HEAD"
-    }
-  },
-
-  "phase2_features": {
-    "external_dependency_management": {
-      "enabled": true,
-      "validation_trigger": "task_start",
-      "supported_sources": ["npm", "maven", "pip", "git"],
-      "version_check_command": {
-        "npm": "npm list {name}",
-        "pip": "pip show {name}",
-        "maven": "mvn dependency:tree"
-      }
-    },
-    "state_recovery": {
-      "enabled": true,
-      "checkpoint_trigger": "phase_complete",
-      "max_checkpoints_per_task": 5,
-      "checkpoint_dir": "checkpoints/"
-    }
-  },
-
-  "phase3_features": {
-    "user_feedback_loop": {
-      "enabled": true,
-      "collection_trigger": "sprint_complete",
-      "max_feedback_items": 50,
-      "severity_levels": ["low", "medium", "high", "critical"],
-      "status_flow": ["new", "reviewed", "addressed", "closed"]
-    },
-    "tech_debt_tracking": {
-      "enabled": true,
-      "detection_sources": ["review", "test", "architect"],
-      "categories": ["code", "design", "test", "documentation"],
-      "severity_levels": ["low", "medium", "high", "critical"],
-      "status_flow": ["open", "in_progress", "resolved", "deferred"],
-      "report_trigger": "sprint_retrospective"
-    }
-  },
-
-  "collaboration_patterns": ["CP-1", "CP-3", "CP-5", "CP-6"],
-
-  "session_dirs": {
-    "base": ".workflow/.team/IDS-{slug}-{YYYY-MM-DD}/",
-    "design": "design/",
-    "code": "code/",
-    "verify": "verify/",
-    "review": "review/",
-    "messages": ".workflow/.team-msg/{team-name}/"
-  }
-}