claude-code-workflow 7.2.23 → 7.2.24

package/.codex/skills/team-coordinate/specs/knowledge-transfer.md

@@ -1,111 +1,111 @@
-# Knowledge Transfer Protocols
-
-## 1. Transfer Channels
-
-| Channel | Scope | Mechanism | When to Use |
-|---------|-------|-----------|-------------|
-| **Artifacts** | Producer -> Consumer | Write to `<session>/artifacts/<name>.md`, consumer reads in Phase 2 | Structured deliverables (reports, plans, specs) |
-| **State Updates** | Cross-role | `team_msg(operation="log", type="state_update", data={...})` / `team_msg(operation="get_state", session_id=<session-id>)` | Key findings, decisions, metadata (small, structured data) |
-| **Wisdom** | Cross-task | Append to `<session>/wisdom/{learnings,decisions,conventions,issues}.md` | Patterns, conventions, risks discovered during execution |
-| **Context Accumulator** | Intra-role (inner loop) | In-memory array, passed to each subsequent task in same-prefix loop | Prior task summaries within same role's inner loop |
-| **Exploration Cache** | Cross-role | `<session>/explorations/cache-index.json` + per-angle JSON | Codebase discovery results, prevents duplicate exploration |
-
-## 2. Context Loading Protocol (Phase 2)
-
-Every role MUST load context in this order before starting work.
-
-| Step | Action | Required |
-|------|--------|----------|
-| 1 | Extract session path from task description | Yes |
-| 2 | `team_msg(operation="get_state", session_id=<session-id>)` | Yes |
-| 3 | Read artifact files from upstream state's `ref` paths | Yes |
-| 4 | Read `<session>/wisdom/*.md` if exists | Yes |
-| 5 | Check `<session>/explorations/cache-index.json` before new exploration | If exploring |
-| 6 | For inner_loop roles: load context_accumulator from prior tasks | If inner_loop |
-
-**Loading rules**:
-- Never skip step 2 -- state contains key decisions and findings
-- If `ref` path in state does not exist, log warning and continue
-- Wisdom files are append-only -- read all entries, newest last
-
-## 3. Context Publishing Protocol (Phase 4)
-
-| Step | Action | Required |
-|------|--------|----------|
-| 1 | Write deliverable to `<session>/artifacts/<task-id>-<name>.md` | Yes |
-| 2 | Send `team_msg(type="state_update")` with payload (see schema below) | Yes |
-| 3 | Append wisdom entries for learnings, decisions, issues found | If applicable |
-
-## 4. State Update Schema
-
-Sent via `team_msg(type="state_update")` on task completion.
-
-```json
-{
-  "status": "task_complete",
-  "task_id": "<TASK-NNN>",
-  "ref": "<session>/artifacts/<filename>",
-  "key_findings": [
-    "Finding 1",
-    "Finding 2"
-  ],
-  "decisions": [
-    "Decision with rationale"
-  ],
-  "files_modified": [
-    "path/to/file.ts"
-  ],
-  "verification": "self-validated | peer-reviewed | tested"
-}
-```
-
-**Field rules**:
-- `ref`: Always an artifact path, never inline content
-- `key_findings`: Max 5 items, each under 100 chars
-- `decisions`: Include rationale, not just the choice
-- `files_modified`: Only for implementation tasks
-- `verification`: One of `self-validated`, `peer-reviewed`, `tested`
-
-**Write state** (namespaced by role):
-```
-team_msg(operation="log", session_id=<session-id>, from=<role>, type="state_update", data={
-  "<role_name>": { "key_findings": [...], "scope": "..." }
-})
-```
-
-**Read state**:
-```
-team_msg(operation="get_state", session_id=<session-id>)
-// Returns merged state from all state_update messages
-```
-
-## 5. Exploration Cache Protocol
-
-Prevents redundant research across tasks and discussion rounds.
-
-| Step | Action |
-|------|--------|
-| 1 | Read `<session>/explorations/cache-index.json` |
-| 2 | If angle already explored, read cached result from `explore-<angle>.json` |
-| 3 | If not cached, perform exploration |
-| 4 | Write result to `<session>/explorations/explore-<angle>.json` |
-| 5 | Update `cache-index.json` with new entry |
-
-**cache-index.json format**:
-```json
-{
-  "entries": [
-    {
-      "angle": "competitor-analysis",
-      "file": "explore-competitor-analysis.json",
-      "created_by": "RESEARCH-001",
-      "timestamp": "2026-01-15T10:30:00Z"
-    }
-  ]
-}
-```
-
-**Rules**:
-- Cache key is the exploration `angle` (normalized to kebab-case)
-- Cache entries never expire within a session
-- Any role can read cached explorations; only the creator updates them
+# Knowledge Transfer Protocols
+
+## 1. Transfer Channels
+
+| Channel | Scope | Mechanism | When to Use |
+|---------|-------|-----------|-------------|
+| **Artifacts** | Producer -> Consumer | Write to `<session>/artifacts/<name>.md`, consumer reads in Phase 2 | Structured deliverables (reports, plans, specs) |
+| **State Updates** | Cross-role | `team_msg(operation="log", type="state_update", data={...})` / `team_msg(operation="get_state", session_id=<session-id>)` | Key findings, decisions, metadata (small, structured data) |
+| **Wisdom** | Cross-task | Append to `<session>/wisdom/{learnings,decisions,conventions,issues}.md` | Patterns, conventions, risks discovered during execution |
+| **Context Accumulator** | Intra-role (inner loop) | In-memory array, passed to each subsequent task in same-prefix loop | Prior task summaries within same role's inner loop |
+| **Exploration Cache** | Cross-role | `<session>/explorations/cache-index.json` + per-angle JSON | Codebase discovery results, prevents duplicate exploration |
+
+## 2. Context Loading Protocol (Phase 2)
+
+Every role MUST load context in this order before starting work.
+
+| Step | Action | Required |
+|------|--------|----------|
+| 1 | Extract session path from task description | Yes |
+| 2 | `team_msg(operation="get_state", session_id=<session-id>)` | Yes |
+| 3 | Read artifact files from upstream state's `ref` paths | Yes |
+| 4 | Read `<session>/wisdom/*.md` if exists | Yes |
+| 5 | Check `<session>/explorations/cache-index.json` before new exploration | If exploring |
+| 6 | For inner_loop roles: load context_accumulator from prior tasks | If inner_loop |
+
+**Loading rules**:
+- Never skip step 2 -- state contains key decisions and findings
+- If `ref` path in state does not exist, log warning and continue
+- Wisdom files are append-only -- read all entries, newest last
+
+## 3. Context Publishing Protocol (Phase 4)
+
+| Step | Action | Required |
+|------|--------|----------|
+| 1 | Write deliverable to `<session>/artifacts/<task-id>-<name>.md` | Yes |
+| 2 | Send `team_msg(type="state_update")` with payload (see schema below) | Yes |
+| 3 | Append wisdom entries for learnings, decisions, issues found | If applicable |
+
+## 4. State Update Schema
+
+Sent via `team_msg(type="state_update")` on task completion.
+
+```json
+{
+  "status": "task_complete",
+  "task_id": "<TASK-NNN>",
+  "ref": "<session>/artifacts/<filename>",
+  "key_findings": [
+    "Finding 1",
+    "Finding 2"
+  ],
+  "decisions": [
+    "Decision with rationale"
+  ],
+  "files_modified": [
+    "path/to/file.ts"
+  ],
+  "verification": "self-validated | peer-reviewed | tested"
+}
+```
+
+**Field rules**:
+- `ref`: Always an artifact path, never inline content
+- `key_findings`: Max 5 items, each under 100 chars
+- `decisions`: Include rationale, not just the choice
+- `files_modified`: Only for implementation tasks
+- `verification`: One of `self-validated`, `peer-reviewed`, `tested`
+
+**Write state** (namespaced by role):
+```
+team_msg(operation="log", session_id=<session-id>, from=<role>, type="state_update", data={
+  "<role_name>": { "key_findings": [...], "scope": "..." }
+})
+```
+
+**Read state**:
+```
+team_msg(operation="get_state", session_id=<session-id>)
+// Returns merged state from all state_update messages
+```
+
+## 5. Exploration Cache Protocol
+
+Prevents redundant research across tasks and discussion rounds.
+
+| Step | Action |
+|------|--------|
+| 1 | Read `<session>/explorations/cache-index.json` |
+| 2 | If angle already explored, read cached result from `explore-<angle>.json` |
+| 3 | If not cached, perform exploration |
+| 4 | Write result to `<session>/explorations/explore-<angle>.json` |
+| 5 | Update `cache-index.json` with new entry |
+
+**cache-index.json format**:
+```json
+{
+  "entries": [
+    {
+      "angle": "competitor-analysis",
+      "file": "explore-competitor-analysis.json",
+      "created_by": "RESEARCH-001",
+      "timestamp": "2026-01-15T10:30:00Z"
+    }
+  ]
+}
+```
+
+**Rules**:
+- Cache key is the exploration `angle` (normalized to kebab-case)
+- Cache entries never expire within a session
+- Any role can read cached explorations; only the creator updates them

package/.codex/skills/team-coordinate/specs/pipelines.md

@@ -1,97 +1,97 @@
-# Pipeline Definitions — Team Coordinate
-
-## Dynamic Pipeline Model
-
-team-coordinate does NOT have a static pipeline. All pipelines are generated at runtime from task-analysis.json based on the user's task description.
-
-## Pipeline Generation Process
-
-```
-Phase 1: analyze-task.md
-  -> Signal detection -> capability mapping -> dependency graph
-  -> Output: task-analysis.json
-
-Phase 2: dispatch.md
-  -> Read task-analysis.json dependency graph
-  -> Create tasks.json entries per dependency node
-  -> Set deps chains from graph edges
-  -> Output: tasks.json with correct DAG
-
-Phase 3-N: monitor.md
-  -> handleSpawnNext: spawn ready tasks as team-worker agents
-  -> handleCallback: mark completed, advance pipeline
-  -> Repeat until all tasks done
-```
-
-## Dynamic Task Naming
-
-| Capability | Prefix | Example |
-|------------|--------|---------|
-| researcher | RESEARCH | RESEARCH-001 |
-| developer | IMPL | IMPL-001 |
-| analyst | ANALYSIS | ANALYSIS-001 |
-| designer | DESIGN | DESIGN-001 |
-| tester | TEST | TEST-001 |
-| writer | DRAFT | DRAFT-001 |
-| planner | PLAN | PLAN-001 |
-| (default) | TASK | TASK-001 |
-
-## Dependency Graph Structure
-
-task-analysis.json encodes the pipeline:
-
-```json
-{
-  "dependency_graph": {
-    "RESEARCH-001": { "role": "researcher", "blockedBy": [], "priority": "P0" },
-    "IMPL-001":     { "role": "developer",  "blockedBy": ["RESEARCH-001"], "priority": "P1" },
-    "TEST-001":     { "role": "tester",     "blockedBy": ["IMPL-001"], "priority": "P2" }
-  }
-}
-```
-
-## Role-Worker Map
-
-Dynamic — loaded from session role-specs at runtime:
-
-```
-<session>/role-specs/<role-name>.md -> team-worker agent
-```
-
-Role-spec files contain YAML frontmatter:
-```yaml
----
-role: <role-name>
-prefix: <PREFIX>
-inner_loop: <true|false>
-message_types:
-  success: <type>
-  error: error
----
-```
-
-## Checkpoint
-
-| Trigger | Behavior |
-|---------|----------|
-| capability_gap reported | handleAdapt: generate new role-spec, spawn new worker |
-| consensus_blocked HIGH | Create REVISION task or pause for user |
-| All tasks complete | handleComplete: interactive completion action |
-
-## Specs Reference
-
-- [role-spec-template.md](role-spec-template.md) — Template for generating dynamic role-specs
-- [quality-gates.md](quality-gates.md) — Quality thresholds and scoring dimensions
-- [knowledge-transfer.md](knowledge-transfer.md) — Context transfer protocols between roles
-
-## Quality Gate Integration
-
-Dynamic pipelines reference quality thresholds from [specs/quality-gates.md](quality-gates.md).
-
-| Gate Point | Trigger | Criteria Source |
-|------------|---------|----------------|
-| After artifact production | Producer role Phase 4 | Behavioral Traits in role-spec |
-| After validation tasks | Tester/analyst completion | quality-gates.md thresholds |
-| Pipeline completion | All tasks done | Aggregate scoring |
-
-Issue classification: Error (blocks) > Warning (proceed with justification) > Info (log for future).
+# Pipeline Definitions — Team Coordinate
+
+## Dynamic Pipeline Model
+
+team-coordinate does NOT have a static pipeline. All pipelines are generated at runtime from task-analysis.json based on the user's task description.
+
+## Pipeline Generation Process
+
+```
+Phase 1: analyze-task.md
+  -> Signal detection -> capability mapping -> dependency graph
+  -> Output: task-analysis.json
+
+Phase 2: dispatch.md
+  -> Read task-analysis.json dependency graph
+  -> Create tasks.json entries per dependency node
+  -> Set deps chains from graph edges
+  -> Output: tasks.json with correct DAG
+
+Phase 3-N: monitor.md
+  -> handleSpawnNext: spawn ready tasks as team-worker agents
+  -> handleCallback: mark completed, advance pipeline
+  -> Repeat until all tasks done
+```
+
+## Dynamic Task Naming
+
+| Capability | Prefix | Example |
+|------------|--------|---------|
+| researcher | RESEARCH | RESEARCH-001 |
+| developer | IMPL | IMPL-001 |
+| analyst | ANALYSIS | ANALYSIS-001 |
+| designer | DESIGN | DESIGN-001 |
+| tester | TEST | TEST-001 |
+| writer | DRAFT | DRAFT-001 |
+| planner | PLAN | PLAN-001 |
+| (default) | TASK | TASK-001 |
+
+## Dependency Graph Structure
+
+task-analysis.json encodes the pipeline:
+
+```json
+{
+  "dependency_graph": {
+    "RESEARCH-001": { "role": "researcher", "blockedBy": [], "priority": "P0" },
+    "IMPL-001":     { "role": "developer",  "blockedBy": ["RESEARCH-001"], "priority": "P1" },
+    "TEST-001":     { "role": "tester",     "blockedBy": ["IMPL-001"], "priority": "P2" }
+  }
+}
+```
+
+## Role-Worker Map
+
+Dynamic — loaded from session role-specs at runtime:
+
+```
+<session>/role-specs/<role-name>.md -> team-worker agent
+```
+
+Role-spec files contain YAML frontmatter:
+```yaml
+---
+role: <role-name>
+prefix: <PREFIX>
+inner_loop: <true|false>
+message_types:
+  success: <type>
+  error: error
+---
+```
+
+## Checkpoint
+
+| Trigger | Behavior |
+|---------|----------|
+| capability_gap reported | handleAdapt: generate new role-spec, spawn new worker |
+| consensus_blocked HIGH | Create REVISION task or pause for user |
+| All tasks complete | handleComplete: interactive completion action |
+
+## Specs Reference
+
+- [role-spec-template.md](role-spec-template.md) — Template for generating dynamic role-specs
+- [quality-gates.md](quality-gates.md) — Quality thresholds and scoring dimensions
+- [knowledge-transfer.md](knowledge-transfer.md) — Context transfer protocols between roles
+
+## Quality Gate Integration
+
+Dynamic pipelines reference quality thresholds from [specs/quality-gates.md](quality-gates.md).
+
+| Gate Point | Trigger | Criteria Source |
+|------------|---------|----------------|
+| After artifact production | Producer role Phase 4 | Behavioral Traits in role-spec |
+| After validation tasks | Tester/analyst completion | quality-gates.md thresholds |
+| Pipeline completion | All tasks done | Aggregate scoring |
+
+Issue classification: Error (blocks) > Warning (proceed with justification) > Info (log for future).

package/.codex/skills/team-coordinate/specs/quality-gates.md

@@ -1,112 +1,112 @@
-# Quality Gates
-
-## 1. Quality Thresholds
-
-| Result | Score | Action |
-|--------|-------|--------|
-| Pass | >= 80% | Report completed |
-| Review | 60-79% | Report completed with warnings |
-| Fail | < 60% | Retry Phase 3 (max 2 retries) |
-
-## 2. Scoring Dimensions
-
-| Dimension | Weight | Criteria |
-|-----------|--------|----------|
-| Completeness | 25% | All required outputs present with substantive content |
-| Consistency | 25% | Terminology, formatting, cross-references are uniform |
-| Accuracy | 25% | Outputs are factually correct and verifiable against sources |
-| Depth | 25% | Sufficient detail for downstream consumers to act on deliverables |
-
-**Score** = weighted average of all dimensions (0-100 per dimension).
-
-## 3. Dynamic Role Quality Checks
-
-Quality checks vary by `output_type` (from task-analysis.json role metadata).
-
-### output_type: artifact
-
-| Check | Pass Criteria |
-|-------|---------------|
-| Artifact exists | File written to `<session>/artifacts/` |
-| Content non-empty | Substantive content, not just headers |
-| Format correct | Expected format (MD, JSON) matches deliverable |
-| Cross-references | All references to upstream artifacts resolve |
-
-### output_type: codebase
-
-| Check | Pass Criteria |
-|-------|---------------|
-| Files modified | Claimed files actually changed (Read to confirm) |
-| Syntax valid | No syntax errors in modified files |
-| No regressions | Existing functionality preserved |
-| Summary artifact | Implementation summary written to artifacts/ |
-
-### output_type: mixed
-
-All checks from both `artifact` and `codebase` apply.
-
-## 4. Verification Protocol
-
-Derived from Behavioral Traits in [role-spec-template.md](role-spec-template.md).
-
-| Step | Action | Required |
-|------|--------|----------|
-| 1 | Verify all claimed files exist via Read | Yes |
-| 2 | Confirm artifact written to `<session>/artifacts/` | Yes |
-| 3 | Check verification summary fields present | Yes |
-| 4 | Score against quality dimensions | Yes |
-| 5 | Apply threshold -> Pass/Review/Fail | Yes |
-
-**On Fail**: Retry Phase 3 (max 2 retries). After 2 retries, report `partial_completion`.
-
-**On Review**: Proceed with warnings logged to `<session>/wisdom/issues.md`.
-
-## 5. Code Review Dimensions
-
-For REVIEW-* or validation tasks during implementation pipelines.
-
-### Quality
-
-| Check | Severity |
-|-------|----------|
-| Empty catch blocks | Error |
-| `as any` type casts | Warning |
-| `@ts-ignore` / `@ts-expect-error` | Warning |
-| `console.log` in production code | Warning |
-| Unused imports/variables | Info |
-
-### Security
-
-| Check | Severity |
-|-------|----------|
-| Hardcoded secrets/credentials | Error |
-| SQL injection vectors | Error |
-| `eval()` or `Function()` usage | Error |
-| `innerHTML` assignment | Warning |
-| Missing input validation | Warning |
-
-### Architecture
-
-| Check | Severity |
-|-------|----------|
-| Circular dependencies | Error |
-| Deep cross-boundary imports (3+ levels) | Warning |
-| Files > 500 lines | Warning |
-| Functions > 50 lines | Info |
-
-### Requirements Coverage
-
-| Check | Severity |
-|-------|----------|
-| Core functionality implemented | Error if missing |
-| Acceptance criteria covered | Error if missing |
-| Edge cases handled | Warning |
-| Error states handled | Warning |
-
-## 6. Issue Classification
-
-| Class | Label | Action |
-|-------|-------|--------|
-| Error | Must fix | Blocks progression, must resolve before proceeding |
-| Warning | Should fix | Should resolve, can proceed with justification |
-| Info | Nice to have | Optional improvement, log for future |
+# Quality Gates
+
+## 1. Quality Thresholds
+
+| Result | Score | Action |
+|--------|-------|--------|
+| Pass | >= 80% | Report completed |
+| Review | 60-79% | Report completed with warnings |
+| Fail | < 60% | Retry Phase 3 (max 2 retries) |
+
+## 2. Scoring Dimensions
+
+| Dimension | Weight | Criteria |
+|-----------|--------|----------|
+| Completeness | 25% | All required outputs present with substantive content |
+| Consistency | 25% | Terminology, formatting, cross-references are uniform |
+| Accuracy | 25% | Outputs are factually correct and verifiable against sources |
+| Depth | 25% | Sufficient detail for downstream consumers to act on deliverables |
+
+**Score** = weighted average of all dimensions (0-100 per dimension).
+
+## 3. Dynamic Role Quality Checks
+
+Quality checks vary by `output_type` (from task-analysis.json role metadata).
+
+### output_type: artifact
+
+| Check | Pass Criteria |
+|-------|---------------|
+| Artifact exists | File written to `<session>/artifacts/` |
+| Content non-empty | Substantive content, not just headers |
+| Format correct | Expected format (MD, JSON) matches deliverable |
+| Cross-references | All references to upstream artifacts resolve |
+
+### output_type: codebase
+
+| Check | Pass Criteria |
+|-------|---------------|
+| Files modified | Claimed files actually changed (Read to confirm) |
+| Syntax valid | No syntax errors in modified files |
+| No regressions | Existing functionality preserved |
+| Summary artifact | Implementation summary written to artifacts/ |
+
+### output_type: mixed
+
+All checks from both `artifact` and `codebase` apply.
+
+## 4. Verification Protocol
+
+Derived from Behavioral Traits in [role-spec-template.md](role-spec-template.md).
+
+| Step | Action | Required |
+|------|--------|----------|
+| 1 | Verify all claimed files exist via Read | Yes |
+| 2 | Confirm artifact written to `<session>/artifacts/` | Yes |
+| 3 | Check verification summary fields present | Yes |
+| 4 | Score against quality dimensions | Yes |
+| 5 | Apply threshold -> Pass/Review/Fail | Yes |
+
+**On Fail**: Retry Phase 3 (max 2 retries). After 2 retries, report `partial_completion`.
+
+**On Review**: Proceed with warnings logged to `<session>/wisdom/issues.md`.
+
+## 5. Code Review Dimensions
+
+For REVIEW-* or validation tasks during implementation pipelines.
+
+### Quality
+
+| Check | Severity |
+|-------|----------|
+| Empty catch blocks | Error |
+| `as any` type casts | Warning |
+| `@ts-ignore` / `@ts-expect-error` | Warning |
+| `console.log` in production code | Warning |
+| Unused imports/variables | Info |
+
+### Security
+
+| Check | Severity |
+|-------|----------|
+| Hardcoded secrets/credentials | Error |
+| SQL injection vectors | Error |
+| `eval()` or `Function()` usage | Error |
+| `innerHTML` assignment | Warning |
+| Missing input validation | Warning |
+
+### Architecture
+
+| Check | Severity |
+|-------|----------|
+| Circular dependencies | Error |
+| Deep cross-boundary imports (3+ levels) | Warning |
+| Files > 500 lines | Warning |
+| Functions > 50 lines | Info |
+
+### Requirements Coverage
+
+| Check | Severity |
+|-------|----------|
+| Core functionality implemented | Error if missing |
+| Acceptance criteria covered | Error if missing |
+| Edge cases handled | Warning |
+| Error states handled | Warning |
+
+## 6. Issue Classification
+
+| Class | Label | Action |
+|-------|-------|--------|
+| Error | Must fix | Blocks progression, must resolve before proceeding |
+| Warning | Should fix | Should resolve, can proceed with justification |
+| Info | Nice to have | Optional improvement, log for future |