claude-code-workflow 7.2.24 → 7.2.26

package/.claude/skills/team-iterdev/roles/coordinator/commands/dispatch.md

@@ -1,234 +0,0 @@
-# Command: Dispatch
-
-Create the iterative development task chain with correct dependencies and structured task descriptions.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| User requirement | From coordinator Phase 1 | Yes |
-| Session folder | From coordinator Phase 2 | Yes |
-| Pipeline definition | From SKILL.md Pipeline Definitions | Yes |
-| Pipeline mode | From session.json `pipeline` | Yes |
-
-1. Load user requirement and scope from session.json
-2. Load pipeline stage definitions from SKILL.md Task Metadata Registry
-3. Read `pipeline` mode from session.json (patch / sprint / multi-sprint)
-
-## Phase 3: Task Chain Creation
-
-### Task Description Template
-
-Every task description uses structured format for clarity:
-
-```
-TaskCreate({
-  subject: "<TASK-ID>",
-  description: "PURPOSE: <what this task achieves> | Success: <measurable completion criteria>
-TASK:
-  - <step 1: specific action>
-  - <step 2: specific action>
-  - <step 3: specific action>
-CONTEXT:
-  - Session: <session-folder>
-  - Scope: <task-scope>
-  - Upstream artifacts: <artifact-1>, <artifact-2>
-  - Shared memory: <session>/.msg/meta.json
-EXPECTED: <deliverable path> + <quality criteria>
-CONSTRAINTS: <scope limits, focus areas>
----
-InnerLoop: <true|false>"
-})
-TaskUpdate({ taskId: "<TASK-ID>", addBlockedBy: [<dependency-list>], owner: "<role>" })
-```
-
-### Mode Router
-
-| Mode | Action |
-|------|--------|
-| `patch` | Create DEV-001 + VERIFY-001 |
-| `sprint` | Create DESIGN-001 + DEV-001 + VERIFY-001 + REVIEW-001 |
-| `multi-sprint` | Create Sprint 1 chain, subsequent sprints created dynamically |
-
----
-
-### Patch Pipeline
-
-**DEV-001** (developer):
-```
-TaskCreate({
-  subject: "DEV-001",
-  description: "PURPOSE: Implement fix | Success: Fix applied, syntax clean
-TASK:
-  - Load target files and understand context
-  - Apply fix changes
-  - Validate syntax
-CONTEXT:
-  - Session: <session-folder>
-  - Scope: <task-scope>
-  - Shared memory: <session>/.msg/meta.json
-EXPECTED: Modified source files + <session>/code/dev-log.md | Syntax clean
-CONSTRAINTS: Minimal changes | Preserve existing behavior
----
-InnerLoop: true"
-})
-TaskUpdate({ taskId: "DEV-001", owner: "developer" })
-```
-
-**VERIFY-001** (tester):
-```
-TaskCreate({
-  subject: "VERIFY-001",
-  description: "PURPOSE: Verify fix correctness | Success: Tests pass, no regressions
-TASK:
-  - Detect test framework
-  - Run targeted tests for changed files
-  - Run regression test suite
-CONTEXT:
-  - Session: <session-folder>
-  - Scope: <task-scope>
-  - Upstream artifacts: code/dev-log.md
-  - Shared memory: <session>/.msg/meta.json
-EXPECTED: <session>/verify/verify-001.json | Pass rate >= 95%
-CONSTRAINTS: Focus on changed files | Report any regressions
----
-InnerLoop: false"
-})
-TaskUpdate({ taskId: "VERIFY-001", addBlockedBy: ["DEV-001"], owner: "tester" })
-```
-
----
-
-### Sprint Pipeline
-
-**DESIGN-001** (architect):
-```
-TaskCreate({
-  subject: "DESIGN-001",
-  description: "PURPOSE: Technical design and task breakdown | Success: Design document + task breakdown ready
-TASK:
-  - Explore codebase for patterns and dependencies
-  - Create component design with integration points
-  - Break down into implementable tasks with acceptance criteria
-CONTEXT:
-  - Session: <session-folder>
-  - Scope: <task-scope>
-  - Shared memory: <session>/.msg/meta.json
-EXPECTED: <session>/design/design-001.md + <session>/design/task-breakdown.json | Components defined, tasks actionable
-CONSTRAINTS: Focus on <task-scope> | Risk assessment required
----
-InnerLoop: false"
-})
-TaskUpdate({ taskId: "DESIGN-001", owner: "architect" })
-```
-
-**DEV-001** (developer):
-```
-TaskCreate({
-  subject: "DEV-001",
-  description: "PURPOSE: Implement design | Success: All design tasks implemented, syntax clean
-TASK:
-  - Load design and task breakdown
-  - Implement tasks in execution order
-  - Validate syntax after changes
-CONTEXT:
-  - Session: <session-folder>
-  - Scope: <task-scope>
-  - Upstream artifacts: design/design-001.md, design/task-breakdown.json
-  - Shared memory: <session>/.msg/meta.json
-EXPECTED: Modified source files + <session>/code/dev-log.md | Syntax clean, all tasks done
-CONSTRAINTS: Follow design | Preserve existing behavior | Follow code conventions
----
-InnerLoop: true"
-})
-TaskUpdate({ taskId: "DEV-001", addBlockedBy: ["DESIGN-001"], owner: "developer" })
-```
-
-**VERIFY-001** (tester, parallel with REVIEW-001):
-```
-TaskCreate({
-  subject: "VERIFY-001",
-  description: "PURPOSE: Verify implementation | Success: Tests pass, no regressions
-TASK:
-  - Detect test framework
-  - Run tests for changed files
-  - Run regression test suite
-CONTEXT:
-  - Session: <session-folder>
-  - Scope: <task-scope>
-  - Upstream artifacts: code/dev-log.md
-  - Shared memory: <session>/.msg/meta.json
-EXPECTED: <session>/verify/verify-001.json | Pass rate >= 95%
-CONSTRAINTS: Focus on changed files | Report regressions
----
-InnerLoop: false"
-})
-TaskUpdate({ taskId: "VERIFY-001", addBlockedBy: ["DEV-001"], owner: "tester" })
-```
-
-**REVIEW-001** (reviewer, parallel with VERIFY-001):
-```
-TaskCreate({
-  subject: "REVIEW-001",
-  description: "PURPOSE: Code review for correctness and quality | Success: All dimensions reviewed, verdict issued
-TASK:
-  - Load changed files and design document
-  - Review across 4 dimensions: correctness, completeness, maintainability, security
-  - Score quality (1-10) and issue verdict
-CONTEXT:
-  - Session: <session-folder>
-  - Scope: <task-scope>
-  - Upstream artifacts: design/design-001.md, code/dev-log.md
-  - Shared memory: <session>/.msg/meta.json
-EXPECTED: <session>/review/review-001.md | Per-dimension findings with severity
-CONSTRAINTS: Focus on implementation changes | Provide file:line references
----
-InnerLoop: false"
-})
-TaskUpdate({ taskId: "REVIEW-001", addBlockedBy: ["DEV-001"], owner: "reviewer" })
-```
-
----
-
-### Multi-Sprint Pipeline
-
-Sprint 1: DESIGN-001 -> DEV-001 -> DEV-002(incremental) -> VERIFY-001 -> DEV-fix -> REVIEW-001
-
-Create Sprint 1 tasks using sprint templates above, plus:
-
-**DEV-002** (developer, incremental):
-```
-TaskCreate({
-  subject: "DEV-002",
-  description: "PURPOSE: Incremental implementation | Success: Remaining tasks implemented
-TASK:
-  - Load remaining tasks from breakdown
-  - Implement incrementally
-  - Validate syntax
-CONTEXT:
-  - Session: <session-folder>
-  - Scope: <task-scope>
-  - Upstream artifacts: design/task-breakdown.json, code/dev-log.md
-  - Shared memory: <session>/.msg/meta.json
-EXPECTED: Modified source files + updated dev-log.md
-CONSTRAINTS: Incremental delivery | Follow existing patterns
----
-InnerLoop: true"
-})
-TaskUpdate({ taskId: "DEV-002", addBlockedBy: ["DEV-001"], owner: "developer" })
-```
-
-Subsequent sprints created dynamically after Sprint N completes.
-
-## Phase 4: Validation
-
-Verify task chain integrity:
-
-| Check | Method | Expected |
-|-------|--------|----------|
-| Task count correct | TaskList count | patch: 2, sprint: 4, multi: 5+ |
-| Dependencies correct | Trace addBlockedBy graph | Acyclic, correct ordering |
-| No circular dependencies | Trace full graph | Acyclic |
-| Structured descriptions | Each has PURPOSE/TASK/CONTEXT/EXPECTED | All present |
-
-If validation fails, fix the specific task and re-validate.

package/.claude/skills/team-iterdev/roles/coordinator/commands/monitor.md

@@ -1,182 +0,0 @@
-# Command: Monitor
-
-Event-driven pipeline coordination. Beat model: coordinator wake -> process -> spawn -> STOP.
-
-## Constants
-
-- SPAWN_MODE: background
-- ONE_STEP_PER_INVOCATION: true
-- FAST_ADVANCE_AWARE: true
-- WORKER_AGENT: team-worker
-- MAX_GC_ROUNDS: 3
-
-## Handler Router
-
-| Source | Handler |
-|--------|---------|
-| Message contains [architect], [developer], [tester], [reviewer] | handleCallback |
-| "capability_gap" | handleAdapt |
-| "check" or "status" | handleCheck |
-| "resume" or "continue" | handleResume |
-| All tasks completed | handleComplete |
-| Default | handleSpawnNext |
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Session state | <session>/session.json | Yes |
-| Task list | TaskList() | Yes |
-| Trigger event | From Entry Router detection | Yes |
-| Meta state | <session>/.msg/meta.json | Yes |
-| Task ledger | <session>/task-ledger.json | No |
-
-1. Load session.json for current state, pipeline mode, gc_round, max_gc_rounds
-2. Run TaskList() to get current task statuses
-3. Identify trigger event type from Entry Router
-
-## Phase 3: Event Handlers
-
-### handleCallback
-
-Triggered when a worker sends completion message.
-
-1. Parse message to identify role and task ID:
-
-| Message Pattern | Role Detection |
-|----------------|---------------|
-| `[architect]` or task ID `DESIGN-*` | architect |
-| `[developer]` or task ID `DEV-*` | developer |
-| `[tester]` or task ID `VERIFY-*` | tester |
-| `[reviewer]` or task ID `REVIEW-*` | reviewer |
-
-2. Mark task as completed:
-
-```
-TaskUpdate({ taskId: "<task-id>", status: "completed" })
-```
-
-3. Record completion in session state and update task-ledger.json metrics
-
-4. **Generator-Critic check** (when reviewer completes):
-   - If completed task is REVIEW-* AND pipeline is sprint or multi-sprint:
-   - Read review report for GC signal (critical_count, score)
-   - Read session.json for gc_round
-
-   | GC Signal | gc_round < max | Action |
-   |-----------|----------------|--------|
-   | review.critical_count > 0 OR review.score < 7 | Yes | Increment gc_round, create DEV-fix task blocked by this REVIEW, log `gc_loop_trigger` |
-   | review.critical_count > 0 OR review.score < 7 | No (>= max) | Force convergence, accept with warning, log to wisdom/issues.md |
-   | review.critical_count == 0 AND review.score >= 7 | - | Review passed, proceed to handleComplete check |
-
-   - Log team_msg with type "gc_loop_trigger" or "task_unblocked"
-
-5. Proceed to handleSpawnNext
-
-### handleSpawnNext
-
-Find and spawn the next ready tasks.
-
-1. Scan task list for tasks where:
-   - Status is "pending"
-   - All blockedBy tasks have status "completed"
-
-2. For each ready task, determine role from task prefix:
-
-| Task Prefix | Role | Inner Loop |
-|-------------|------|------------|
-| DESIGN-* | architect | false |
-| DEV-* | developer | true |
-| VERIFY-* | tester | false |
-| REVIEW-* | reviewer | false |
-
-3. Spawn team-worker:
-
-```
-Agent({
-  subagent_type: "team-worker",
-  description: "Spawn <role> worker for <task-id>",
-  team_name: "iterdev",
-  name: "<role>",
-  run_in_background: true,
-  prompt: `## Role Assignment
-role: <role>
-role_spec: ~  or <project>/.claude/skills/team-iterdev/roles/<role>/role.md
-session: <session-folder>
-session_id: <session-id>
-team_name: iterdev
-requirement: <task-description>
-inner_loop: <true|false>
-
-Read role_spec file to load Phase 2-4 domain instructions.
-Execute built-in Phase 1 -> role-spec Phase 2-4 -> built-in Phase 5.`
-})
-```
-
-4. **Parallel spawn rules**:
-
-| Pipeline | Scenario | Spawn Behavior |
-|----------|----------|---------------|
-| Patch | DEV -> VERIFY | One worker at a time |
-| Sprint | VERIFY + REVIEW both unblocked | Spawn BOTH in parallel |
-| Sprint | Other stages | One worker at a time |
-| Multi-Sprint | VERIFY + DEV-fix both unblocked | Spawn BOTH in parallel |
-| Multi-Sprint | Other stages | One worker at a time |
-
-5. STOP after spawning -- wait for next callback
-
-### handleCheck
-
-Output current pipeline status. Do NOT advance pipeline.
-
-```
-Pipeline Status (<pipeline-mode>):
-  [DONE]  DESIGN-001  (architect)   -> design/design-001.md
-  [DONE]  DEV-001     (developer)   -> code/dev-log.md
-  [RUN]   VERIFY-001  (tester)      -> verifying...
-  [RUN]   REVIEW-001  (reviewer)    -> reviewing...
-  [WAIT]  DEV-fix     (developer)   -> blocked by REVIEW-001
-
-GC Rounds: <gc_round>/<max_gc_rounds>
-Sprint: <sprint_id>
-Session: <session-id>
-```
-
-### handleResume
-
-Resume pipeline after user pause or interruption.
-
-1. Audit task list for inconsistencies:
-   - Tasks stuck in "in_progress" -> reset to "pending"
-   - Tasks with completed blockers but still "pending" -> include in spawn list
-2. Proceed to handleSpawnNext
-
-### handleComplete
-
-Triggered when all pipeline tasks are completed.
-
-**Completion check by mode**:
-
-| Mode | Completion Condition |
-|------|---------------------|
-| patch | DEV-001 + VERIFY-001 completed |
-| sprint | DESIGN-001 + DEV-001 + VERIFY-001 + REVIEW-001 (+ any GC tasks) completed |
-| multi-sprint | All sprint tasks (+ any GC tasks) completed |
-
-1. Verify all tasks completed via TaskList()
-2. If any tasks not completed, return to handleSpawnNext
-3. **Multi-sprint check**: If multi-sprint AND more sprints planned:
-   - Record sprint metrics to .msg/meta.json sprint_history
-   - Evaluate downgrade eligibility (velocity >= expected, review avg >= 8)
-   - Pause for user confirmation before Sprint N+1
-4. If all completed, transition to coordinator Phase 5 (Report + Completion Action)
-
-## Phase 4: State Persistence
-
-After every handler execution:
-
-1. Update session.json with current state (gc_round, last event, active tasks)
-2. Update task-ledger.json metrics (completed count, in_progress count, velocity)
-3. Update .msg/meta.json gc_round if changed
-4. Verify task list consistency
-5. STOP and wait for next event

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