claude-code-workflow 7.2.15 → 7.2.16

package/.codex/skills/team-brainstorm/schemas/tasks-schema.md

@@ -1,171 +0,0 @@
-# Team Brainstorm — CSV Schema
-
-## Master CSV: tasks.csv
-
-### Column Definitions
-
-#### Input Columns (Set by Decomposer)
-
-| Column | Type | Required | Description | Example |
-|--------|------|----------|-------------|---------|
-| `id` | string | Yes | Unique task identifier | `"IDEA-001"` |
-| `title` | string | Yes | Short task title | `"Multi-angle idea generation"` |
-| `description` | string | Yes | Detailed task description (self-contained) | `"Generate 3+ ideas per angle..."` |
-| `role` | string | Yes | Worker role: ideator, challenger, synthesizer, evaluator | `"ideator"` |
-| `angle` | string | No | Brainstorming angle(s) for ideator tasks (semicolon-separated) | `"Technical;Product;Innovation"` |
-| `gc_round` | integer | Yes | Generator-Critic round number (0 = initial, 1+ = revision) | `"0"` |
-| `deps` | string | No | Semicolon-separated dependency task IDs | `"IDEA-001"` |
-| `context_from` | string | No | Semicolon-separated task IDs for context | `"IDEA-001"` |
-| `exec_mode` | enum | Yes | Execution mechanism: `csv-wave` or `interactive` | `"csv-wave"` |
-
-#### Computed Columns (Set by Wave Engine)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `wave` | integer | Wave number (1-based, from topological sort) | `2` |
-| `prev_context` | string | Aggregated findings from context_from tasks (per-wave CSV only) | `"[Task IDEA-001] Generated 8 ideas..."` |
-
-#### Output Columns (Set by Agent)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `status` | enum | `pending` → `completed` / `failed` / `skipped` | `"completed"` |
-| `findings` | string | Key discoveries (max 500 chars) | `"Generated 8 ideas across 3 angles..."` |
-| `gc_signal` | string | Generator-Critic signal (challenger only): `REVISION_NEEDED` or `CONVERGED` | `"REVISION_NEEDED"` |
-| `severity_summary` | string | Severity count summary (challenger only) | `"CRITICAL:0 HIGH:2 MEDIUM:3 LOW:1"` |
-| `error` | string | Error message if failed | `""` |
-
----
-
-### exec_mode Values
-
-| Value | Mechanism | Description |
-|-------|-----------|-------------|
-| `csv-wave` | `spawn_agents_on_csv` | One-shot batch execution within wave |
-| `interactive` | `spawn_agent`/`wait`/`send_input`/`close_agent` | Multi-round individual execution |
-
-Interactive tasks appear in master CSV for dependency tracking but are NOT included in wave-{N}.csv files.
-
----
-
-### Example Data
-
-```csv
-id,title,description,role,angle,gc_round,deps,context_from,exec_mode,wave,status,findings,gc_signal,severity_summary,error
-"IDEA-001","Multi-angle idea generation","Generate 3+ ideas per angle with title, description, assumption, and potential impact. Cover all assigned angles comprehensively.","ideator","Technical;Product;Innovation","0","","","csv-wave","1","pending","","","",""
-"IDEA-002","Parallel angle generation (Risk)","Generate 3+ ideas focused on Risk angle with title, description, assumption, and potential impact.","ideator","Risk","0","","","csv-wave","1","pending","","","",""
-"CHALLENGE-001","Critique generated ideas","Read all idea artifacts. Challenge each idea across assumption validity, feasibility, risk, and competition dimensions. Assign severity (CRITICAL/HIGH/MEDIUM/LOW) per idea. Output GC signal.","challenger","","0","IDEA-001;IDEA-002","IDEA-001;IDEA-002","csv-wave","2","pending","","","",""
-"GC-CHECK-001","GC loop decision","Evaluate critique severity counts. If any HIGH/CRITICAL: REVISION_NEEDED. Else: CONVERGED.","gc-controller","","1","CHALLENGE-001","CHALLENGE-001","interactive","3","pending","","","",""
-"IDEA-003","Revise ideas (GC Round 1)","Address HIGH/CRITICAL challenges from critique. Retain unchallenged ideas intact. Replace unsalvageable ideas.","ideator","","1","GC-CHECK-001","CHALLENGE-001","csv-wave","4","pending","","","",""
-"SYNTH-001","Synthesize proposals","Extract themes from ideas and critiques. Resolve conflicts. Generate 1-3 integrated proposals with feasibility and innovation scores.","synthesizer","","0","IDEA-003","IDEA-001;IDEA-002;IDEA-003;CHALLENGE-001","csv-wave","5","pending","","","",""
-"EVAL-001","Score and rank proposals","Score each proposal: Feasibility 30%, Innovation 25%, Impact 25%, Cost 20%. Generate final ranking and recommendation.","evaluator","","0","SYNTH-001","SYNTH-001","csv-wave","6","pending","","","",""
-```
-
----
-
-### Column Lifecycle
-
-```
-Decomposer (Phase 1)     Wave Engine (Phase 2)    Agent (Execution)
-─────────────────────    ────────────────────     ─────────────────
-id          ───────────►  id          ──────────►  id
-title       ───────────►  title       ──────────►  (reads)
-description ───────────►  description ──────────►  (reads)
-role        ───────────►  role        ──────────►  (reads)
-angle       ───────────►  angle       ──────────►  (reads)
-gc_round    ───────────►  gc_round    ──────────►  (reads)
-deps        ───────────►  deps        ──────────►  (reads)
-context_from───────────►  context_from──────────►  (reads)
-exec_mode   ───────────►  exec_mode   ──────────►  (reads)
-                          wave         ──────────►  (reads)
-                          prev_context ──────────►  (reads)
-                                                    status
-                                                    findings
-                                                    gc_signal
-                                                    severity_summary
-                                                    error
-```
-
----
-
-## Output Schema (JSON)
-
-Agent output via `report_agent_job_result` (csv-wave tasks):
-
-```json
-{
-  "id": "IDEA-001",
-  "status": "completed",
-  "findings": "Generated 8 ideas across Technical, Product, Innovation angles. Key themes: API gateway pattern, event-driven architecture, developer experience tools.",
-  "gc_signal": "",
-  "severity_summary": "",
-  "error": ""
-}
-```
-
-Challenger-specific output:
-
-```json
-{
-  "id": "CHALLENGE-001",
-  "status": "completed",
-  "findings": "Challenged 8 ideas. 2 HIGH severity (require revision), 3 MEDIUM, 3 LOW.",
-  "gc_signal": "REVISION_NEEDED",
-  "severity_summary": "CRITICAL:0 HIGH:2 MEDIUM:3 LOW:3",
-  "error": ""
-}
-```
-
-Interactive tasks output via structured text or JSON written to `interactive/{id}-result.json`.
-
----
-
-## Discovery Types
-
-| Type | Dedup Key | Data Schema | Description |
-|------|-----------|-------------|-------------|
-| `idea` | `data.title` | `{title, angle, description, assumption, impact}` | Generated brainstorm idea |
-| `critique` | `data.idea_title` | `{idea_title, dimension, severity, challenge, rationale}` | Critique of an idea |
-| `theme` | `data.name` | `{name, strength, supporting_ideas[]}` | Extracted theme from synthesis |
-| `proposal` | `data.title` | `{title, source_ideas[], feasibility, innovation, description}` | Integrated proposal |
-| `evaluation` | `data.proposal_title` | `{proposal_title, weighted_score, rank, recommendation}` | Scored proposal |
-| `gc_decision` | `data.round` | `{round, signal, severity_counts}` | GC loop decision record |
-
-### Discovery NDJSON Format
-
-```jsonl
-{"ts":"2026-03-08T10:00:00+08:00","worker":"IDEA-001","type":"idea","data":{"title":"API Gateway Pattern","angle":"Technical","description":"Centralized API gateway for microservice routing","assumption":"Services need unified entry point","impact":"Simplifies client integration"}}
-{"ts":"2026-03-08T10:01:00+08:00","worker":"IDEA-001","type":"idea","data":{"title":"Event Sourcing Migration","angle":"Technical","description":"Adopt event sourcing for service state management","assumption":"Current state is hard to trace across services","impact":"Full audit trail and temporal queries"}}
-{"ts":"2026-03-08T10:05:00+08:00","worker":"CHALLENGE-001","type":"critique","data":{"idea_title":"API Gateway Pattern","dimension":"feasibility","severity":"MEDIUM","challenge":"Single point of failure risk","rationale":"Requires HA design with circuit breakers"}}
-{"ts":"2026-03-08T10:10:00+08:00","worker":"SYNTH-001","type":"theme","data":{"name":"Infrastructure Modernization","strength":8,"supporting_ideas":["API Gateway Pattern","Event Sourcing Migration"]}}
-```
-
-> Both csv-wave and interactive agents read/write the same discoveries.ndjson file.
-
----
-
-## Cross-Mechanism Context Flow
-
-| Source | Target | Mechanism |
-|--------|--------|-----------|
-| CSV task findings | Interactive task | Injected via spawn message or send_input |
-| Interactive task result | CSV task prev_context | Read from interactive/{id}-result.json |
-| Any agent discovery | Any agent | Shared via discoveries.ndjson |
-
----
-
-## Validation Rules
-
-| Rule | Check | Error |
-|------|-------|-------|
-| Unique IDs | No duplicate `id` values | "Duplicate task ID: {id}" |
-| Valid deps | All dep IDs exist in tasks | "Unknown dependency: {dep_id}" |
-| No self-deps | Task cannot depend on itself | "Self-dependency: {id}" |
-| No circular deps | Topological sort completes | "Circular dependency detected involving: {ids}" |
-| context_from valid | All context IDs exist and in earlier waves | "Invalid context_from: {id}" |
-| exec_mode valid | Value is `csv-wave` or `interactive` | "Invalid exec_mode: {value}" |
-| Description non-empty | Every task has description | "Empty description for task: {id}" |
-| Status enum | status in {pending, completed, failed, skipped} | "Invalid status: {status}" |
-| Valid role | role in {ideator, challenger, synthesizer, evaluator, gc-controller} | "Invalid role: {role}" |
-| GC round non-negative | gc_round >= 0 | "Invalid gc_round: {value}" |
-| Cross-mechanism deps | Interactive→CSV deps resolve correctly | "Cross-mechanism dependency unresolvable: {id}" |

package/.codex/skills/team-coordinate/agents/completion-handler.md

@@ -1,127 +0,0 @@
-# Completion Handler Agent
-
-Interactive agent for handling pipeline completion actions. Presents results summary and manages Archive/Keep/Export choices.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `agents/completion-handler.md`
-- **Responsibility**: Pipeline completion reporting and cleanup action
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Read final tasks.csv to compile completion summary
-- Present deliverables list with paths
-- Execute chosen completion action
-- Produce structured output following template
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Delete session data without user confirmation
-- Produce unstructured output
-- Modify task artifacts
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | built-in | Load tasks.csv, artifacts |
-| `request_user_input` | built-in | Get completion choice |
-| `Write` | built-in | Store completion result |
-| `Bash` | built-in | Archive or export operations |
-
----
-
-## Execution
-
-### Phase 1: Summary Generation
-
-**Objective**: Compile pipeline completion summary
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| tasks.csv | Yes | Master state with all results |
-| artifacts/ | No | Deliverable files |
-| discoveries.ndjson | No | Shared discoveries |
-
-**Steps**:
-
-1. Read tasks.csv, count completed/failed/skipped
-2. List all produced artifacts with paths
-3. Summarize discoveries
-4. Calculate pipeline duration if timestamps available
-
-**Output**: Completion summary
-
----
-
-### Phase 2: Completion Choice
-
-**Objective**: Execute user's chosen completion action
-
-**Steps**:
-
-1. Present completion choice:
-
-```javascript
-request_user_input({
-  questions: [{
-    question: "Team pipeline complete. What would you like to do?",
-    header: "Completion",
-    id: "completion_action",
-    options: [
-      { label: "Archive & Clean (Recommended)", description: "Mark session complete, output final summary" },
-      { label: "Keep Active", description: "Keep session for follow-up work" },
-      { label: "Export Results", description: "Export deliverables to target directory" }
-    ]
-  }]
-})
-```
-
-2. Handle choice:
-
-| Choice | Steps |
-|--------|-------|
-| Archive & Clean | Write completion status, output artifact paths |
-| Keep Active | Keep session files, output resume instructions |
-| Export Results | Ask target path, copy artifacts, then archive |
-
-**Output**: Completion action result
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Pipeline status: completed
-- Tasks: <completed>/<total>
-
-## Deliverables
-- <artifact-path-1> (produced by <role>)
-- <artifact-path-2> (produced by <role>)
-
-## Action Taken
-- Choice: <archive|keep|export>
-- Details: <action-specific details>
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| tasks.csv not found | Report error, suggest manual review |
-| Export target path invalid | Ask user for valid path |
-| Processing failure | Default to Keep Active, log warning |

package/.codex/skills/team-coordinate/agents/plan-reviewer.md

@@ -1,145 +0,0 @@
-# Plan Reviewer Agent
-
-Interactive agent for reviewing and approving plans before execution waves. Used when a task requires user confirmation checkpoint before proceeding.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `agents/plan-reviewer.md`
-- **Responsibility**: Review generated plans, seek user approval, handle revision requests
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Read the plan artifact being reviewed
-- Present a clear summary to the user
-- Wait for user approval before reporting complete
-- Produce structured output following template
-- Include file:line references in findings
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Approve plans without user confirmation
-- Modify the plan artifact directly
-- Produce unstructured output
-- Exceed defined scope boundaries
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | built-in | Load plan artifacts and context |
-| `request_user_input` | built-in | Get user approval or revision feedback |
-| `Write` | built-in | Store review result |
-
-### Tool Usage Patterns
-
-**Read Pattern**: Load context files before review
-```
-Read("<session>/artifacts/<plan>.md")
-Read("<session>/discoveries.ndjson")
-```
-
-**Write Pattern**: Store review result
-```
-Write("<session>/interactive/<task-id>-result.json", <result>)
-```
-
----
-
-## Execution
-
-### Phase 1: Context Loading
-
-**Objective**: Load the plan artifact and supporting context
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| Plan artifact | Yes | The plan document to review |
-| discoveries.ndjson | No | Shared discoveries for context |
-| Previous task findings | No | Upstream task results |
-
-**Steps**:
-
-1. Extract session path from task assignment
-2. Read the plan artifact referenced in the task description
-3. Read discoveries.ndjson for additional context
-4. Summarize key aspects of the plan
-
-**Output**: Plan summary ready for user review
-
----
-
-### Phase 2: User Review
-
-**Objective**: Present plan to user and get approval
-
-**Steps**:
-
-1. Display plan summary with key decisions and trade-offs
-2. Present approval choice:
-
-```javascript
-request_user_input({
-  questions: [{
-    question: "Review the plan and decide:",
-    header: "Plan Review",
-    id: "plan_review",
-    options: [
-      { label: "Approve (Recommended)", description: "Proceed with execution" },
-      { label: "Revise", description: "Request changes to the plan" },
-      { label: "Abort", description: "Cancel the pipeline" }
-    ]
-  }]
-})
-```
-
-3. Handle response:
-
-| Response | Action |
-|----------|--------|
-| Approve | Report approved status |
-| Revise | Collect revision feedback, report revision needed |
-| Abort | Report abort status |
-
-**Output**: Review decision with details
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Plan reviewed: <plan-name>
-- Decision: <approved|revision-needed|aborted>
-
-## Findings
-- Key strength 1: description
-- Key concern 1: description
-
-## Decision Details
-- User choice: <choice>
-- Feedback: <user feedback if revision>
-
-## Open Questions
-1. Any unresolved items from review
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Plan artifact not found | Report in Open Questions, ask user for path |
-| User does not respond | Timeout, report partial with "awaiting-review" status |
-| Processing failure | Output partial results with clear status indicator |

package/.codex/skills/team-coordinate/instructions/agent-instruction.md

@@ -1,184 +0,0 @@
-# Agent Instruction Template -- Team Coordinate
-
-Base instruction template for CSV wave agents. The orchestrator dynamically customizes this per role during Phase 1, writing role-specific versions to `role-instructions/{role-name}.md`.
-
-## Purpose
-
-| Phase | Usage |
-|-------|-------|
-| Phase 1 | Coordinator generates per-role instruction from this template |
-| Phase 2 | Injected as `instruction` parameter to `spawn_agents_on_csv` |
-
----
-
-## Base Instruction Template
-
-```markdown
-## TASK ASSIGNMENT -- Team Coordinate
-
-### MANDATORY FIRST STEPS
-1. Read shared discoveries: <session-folder>/discoveries.ndjson (if exists, skip if not)
-2. Read project context: .workflow/project-tech.json (if exists)
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Role**: {role}
-**Responsibility**: {responsibility_type}
-**Output Type**: {output_type}
-
-### Task Description
-{description}
-
-### Previous Tasks' Findings (Context)
-{prev_context}
-
----
-
-## Execution Protocol
-
-1. **Read discoveries**: Load <session-folder>/discoveries.ndjson for shared exploration findings
-2. **Use context**: Apply previous tasks' findings from prev_context above
-3. **Execute task**:
-   - Read target files referenced in description
-   - Follow the execution steps outlined in the TASK section of description
-   - Produce deliverables matching the EXPECTED section of description
-   - Verify output matches success criteria
-4. **Share discoveries**: Append exploration findings to shared board:
-   ```bash
-   echo '{"ts":"<ISO8601>","worker":"{id}","type":"<type>","data":{...}}' >> <session-folder>/discoveries.ndjson
-   ```
-5. **Report result**: Return JSON via report_agent_job_result
-
-### Discovery Types to Share
-- `pattern_found`: {pattern_name, location, description} -- Design pattern identified in codebase
-- `file_modified`: {file, change, lines_added} -- File change performed by this agent
-- `dependency_found`: {from, to, type} -- Dependency relationship between components
-- `issue_found`: {file, line, severity, description} -- Issue or bug discovered
-- `decision_made`: {decision, rationale, impact} -- Design decision made during execution
-- `artifact_produced`: {name, path, producer, type} -- Deliverable file created
-
----
-
-## Output (report_agent_job_result)
-
-Return JSON:
-{
-  "id": "{id}",
-  "status": "completed" | "failed",
-  "findings": "Key discoveries and implementation notes (max 500 chars)",
-  "artifacts_produced": "semicolon-separated paths of produced files",
-  "error": ""
-}
-```
-
----
-
-## Role-Specific Customization
-
-The coordinator generates per-role instruction variants during Phase 1. Each variant adds role-specific execution guidance to Step 3.
-
-### For Research / Exploration Roles
-
-Add to execution protocol step 3:
-```
-3. **Execute**:
-   - Define exploration scope from description
-   - Use code search tools to find relevant patterns and implementations
-   - Survey approaches, compare alternatives
-   - Document findings with file:line references
-   - Write research artifact to <session-folder>/artifacts/
-```
-
-### For Code Implementation Roles
-
-Add to execution protocol step 3:
-```
-3. **Execute**:
-   - Read upstream design/spec artifacts referenced in description
-   - Read target files listed in description
-   - Apply code changes following project conventions
-   - Validate changes compile/lint correctly
-   - Run relevant tests if available
-   - Write implementation summary to <session-folder>/artifacts/
-```
-
-### For Analysis / Audit Roles
-
-Add to execution protocol step 3:
-```
-3. **Execute**:
-   - Read target files/modules for analysis
-   - Apply analysis criteria systematically
-   - Classify findings by severity (critical, high, medium, low)
-   - Include file:line references in findings
-   - Write analysis report to <session-folder>/artifacts/
-```
-
-### For Test / Validation Roles
-
-Add to execution protocol step 3:
-```
-3. **Execute**:
-   - Read source files to understand implementation
-   - Identify test cases from description
-   - Generate test files following project test conventions
-   - Run tests and capture results
-   - Write test report to <session-folder>/artifacts/
-```
-
-### For Documentation / Writing Roles
-
-Add to execution protocol step 3:
-```
-3. **Execute**:
-   - Read source code and existing documentation
-   - Generate documentation following template in description
-   - Ensure accuracy against current implementation
-   - Include code examples where appropriate
-   - Write document to <session-folder>/artifacts/
-```
-
-### For Design / Architecture Roles
-
-Add to execution protocol step 3:
-```
-3. **Execute**:
-   - Read upstream research findings
-   - Analyze existing codebase structure
-   - Design component interactions and data flow
-   - Document architecture decisions with rationale
-   - Write design document to <session-folder>/artifacts/
-```
-
----
-
-## Quality Requirements
-
-All agents must verify before reporting complete:
-
-| Requirement | Criteria |
-|-------------|----------|
-| Files produced | Verify all claimed artifacts exist via Read |
-| Files modified | Verify content actually changed |
-| Findings accuracy | Findings reflect actual work done |
-| Discovery sharing | At least 1 discovery shared to board |
-| Error reporting | Non-empty error field if status is failed |
-
----
-
-## Placeholder Reference
-
-| Placeholder | Resolved By | When |
-|-------------|------------|------|
-| `<session-folder>` | Skill designer (Phase 1) | Literal path baked into instruction |
-| `{id}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{title}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{description}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{role}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{responsibility_type}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{output_type}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{prev_context}` | spawn_agents_on_csv | Runtime from CSV row |