claude-code-workflow 7.2.15 → 7.2.16

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

@@ -1,198 +0,0 @@
-# Team Issue Resolution -- CSV Schema
-
-## Master CSV: tasks.csv
-
-### Column Definitions
-
-#### Input Columns (Set by Decomposer)
-
-| Column | Type | Required | Description | Example |
-|--------|------|----------|-------------|---------|
-| `id` | string | Yes | Unique task identifier | `"EXPLORE-001"` |
-| `title` | string | Yes | Short task title | `"Context analysis"` |
-| `description` | string | Yes | Detailed task description (self-contained) | `"Analyze issue context and map codebase impact for ISS-20260308-120000"` |
-| `role` | enum | Yes | Worker role: explorer, planner, reviewer, integrator, implementer | `"explorer"` |
-| `issue_ids` | string | Yes | Semicolon-separated issue IDs | `"ISS-20260308-120000;ISS-20260308-120001"` |
-| `exec_mode` | enum | Yes | Execution mechanism: `csv-wave` or `interactive` | `"csv-wave"` |
-| `execution_method` | string | No | CLI tool for BUILD tasks: codex, gemini, qwen, or empty | `"gemini"` |
-| `deps` | string | No | Semicolon-separated dependency task IDs | `"EXPLORE-001"` |
-| `context_from` | string | No | Semicolon-separated task IDs for context | `"EXPLORE-001"` |
-
-#### 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) | `"[EXPLORE-001] Found 5 relevant files..."` |
-
-#### Output Columns (Set by Agent)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `status` | enum | `pending` -> `completed` / `failed` / `skipped` | `"completed"` |
-| `findings` | string | Key discoveries (max 500 chars) | `"Identified 3 affected modules..."` |
-| `artifact_path` | string | Path to generated artifact file | `"explorations/context-ISS-20260308-120000.json"` |
-| `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 (review gates) |
-
-Interactive tasks appear in master CSV for dependency tracking but are NOT included in wave-{N}.csv files.
-
----
-
-### Role Values
-
-| Role | Task Prefixes | Responsibility |
-|------|---------------|----------------|
-| `explorer` | EXPLORE-* | Codebase exploration, context analysis, impact assessment |
-| `planner` | SOLVE-*, SOLVE-fix-* | Solution design, task decomposition, revision |
-| `reviewer` | AUDIT-* | Technical review with multi-dimensional scoring |
-| `integrator` | MARSHAL-* | Queue formation, conflict detection, execution ordering |
-| `implementer` | BUILD-* | Code implementation, testing, verification |
-
----
-
-### Example Data
-
-```csv
-id,title,description,role,issue_ids,exec_mode,execution_method,deps,context_from,wave,status,findings,artifact_path,error
-"EXPLORE-001","Context analysis","Analyze issue context and map codebase impact for ISS-20260308-120000","explorer","ISS-20260308-120000","csv-wave","","","","1","pending","","",""
-"SOLVE-001","Solution design","Design solution and decompose into implementation tasks for ISS-20260308-120000","planner","ISS-20260308-120000","csv-wave","","EXPLORE-001","EXPLORE-001","2","pending","","",""
-"AUDIT-001","Technical review","Review solution for feasibility risk and completeness","reviewer","ISS-20260308-120000","interactive","","SOLVE-001","SOLVE-001","3","pending","","",""
-"MARSHAL-001","Queue formation","Form execution queue with conflict detection and optimal ordering","integrator","ISS-20260308-120000","csv-wave","","AUDIT-001","SOLVE-001","4","pending","","",""
-"BUILD-001","Implementation","Implement solution plan and verify with tests","implementer","ISS-20260308-120000","csv-wave","gemini","MARSHAL-001","EXPLORE-001;SOLVE-001","5","pending","","",""
-```
-
----
-
-### Column Lifecycle
-
-```
-Decomposer (Phase 1)     Wave Engine (Phase 2)    Agent (Execution)
----------------------    --------------------     -----------------
-id          ---------->  id          ---------->  id
-title       ---------->  title       ---------->  (reads)
-description ---------->  description ---------->  (reads)
-role        ---------->  role        ---------->  (reads)
-issue_ids   ---------->  issue_ids   ---------->  (reads)
-exec_mode   ---------->  exec_mode   ---------->  (reads)
-execution_method ------>  execution_method ----->  (reads)
-deps        ---------->  deps        ---------->  (reads)
-context_from---------->  context_from---------->  (reads)
-                          wave         ---------->  (reads)
-                          prev_context ---------->  (reads)
-                                                    status
-                                                    findings
-                                                    artifact_path
-                                                    error
-```
-
----
-
-## Output Schema (JSON)
-
-Agent output via `report_agent_job_result` (csv-wave tasks):
-
-```json
-{
-  "id": "EXPLORE-001",
-  "status": "completed",
-  "findings": "Identified 5 relevant files in src/auth/. Impact scope: medium. Key dependency: shared/utils/token.ts. Existing pattern: middleware-chain in src/middleware/.",
-  "artifact_path": "explorations/context-ISS-20260308-120000.json",
-  "error": ""
-}
-```
-
-Interactive tasks output via structured text or JSON written to `interactive/{id}-result.json`.
-
----
-
-## Discovery Types
-
-| Type | Dedup Key | Data Schema | Description |
-|------|-----------|-------------|-------------|
-| `file_found` | `path` | `{path, relevance, purpose}` | Relevant file discovered during exploration |
-| `pattern_found` | `pattern+location` | `{pattern, location, description}` | Code pattern identified |
-| `dependency_found` | `from+to` | `{from, to, type}` | Dependency relationship between modules |
-| `solution_approach` | `issue_id` | `{issue_id, approach, estimated_files}` | Solution strategy chosen |
-| `conflict_found` | `files` | `{issues, files, resolution}` | File conflict between issue solutions |
-| `impl_result` | `issue_id` | `{issue_id, files_changed, tests_pass}` | Implementation outcome |
-
-### Discovery NDJSON Format
-
-```jsonl
-{"ts":"2026-03-08T10:00:00Z","worker":"EXPLORE-001","type":"file_found","data":{"path":"src/auth/handler.ts","relevance":"high","purpose":"Main auth request handler"}}
-{"ts":"2026-03-08T10:01:00Z","worker":"EXPLORE-001","type":"pattern_found","data":{"pattern":"middleware-chain","location":"src/middleware/","description":"Express middleware chain pattern used across all route handlers"}}
-{"ts":"2026-03-08T10:05:00Z","worker":"SOLVE-001","type":"solution_approach","data":{"issue_id":"ISS-20260308-120000","approach":"refactor-extract","estimated_files":5}}
-{"ts":"2026-03-08T10:15:00Z","worker":"MARSHAL-001","type":"conflict_found","data":{"issues":["ISS-20260308-120000","ISS-20260308-120001"],"files":["src/auth/handler.ts"],"resolution":"sequential"}}
-```
-
-> 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 (prev_context) |
-| Interactive task result | CSV task prev_context | Read from interactive/{id}-result.json |
-| Any agent discovery | Any agent | Shared via discoveries.ndjson |
-
----
-
-## Pipeline-Specific Schemas
-
-### Quick Pipeline (4 tasks, 4 waves)
-
-| Wave | Tasks | exec_mode |
-|------|-------|-----------|
-| 1 | EXPLORE-001 | csv-wave |
-| 2 | SOLVE-001 | csv-wave |
-| 3 | MARSHAL-001 | csv-wave |
-| 4 | BUILD-001 | csv-wave |
-
-### Full Pipeline (5 tasks, 5 waves)
-
-| Wave | Tasks | exec_mode |
-|------|-------|-----------|
-| 1 | EXPLORE-001 | csv-wave |
-| 2 | SOLVE-001 | csv-wave |
-| 3 | AUDIT-001 | interactive |
-| 4 | MARSHAL-001 | csv-wave |
-| 5 | BUILD-001 | csv-wave |
-
-### Batch Pipeline (N+N+1+1+M tasks)
-
-| Wave | Tasks | exec_mode | Parallelism |
-|------|-------|-----------|-------------|
-| 1 | EXPLORE-001..N | csv-wave | max 5 concurrent |
-| 2 | SOLVE-001..N | csv-wave | sequential |
-| 3 | AUDIT-001 | interactive | 1 |
-| 4 | MARSHAL-001 | csv-wave | 1 |
-| 5 | BUILD-001..M (deferred) | csv-wave | max 3 concurrent |
-
----
-
-## 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}" |
-| Role valid | Value in {explorer, planner, reviewer, integrator, implementer} | "Invalid role: {role}" |
-| Description non-empty | Every task has description | "Empty description for task: {id}" |
-| Status enum | status in {pending, completed, failed, skipped} | "Invalid status: {status}" |
-| Cross-mechanism deps | Interactive->CSV deps resolve correctly | "Cross-mechanism dependency unresolvable: {id}" |
-| Issue IDs non-empty | Every task has at least one issue_id | "No issue_ids for task: {id}" |

package/.codex/skills/team-iterdev/agents/gc-controller.md

@@ -1,193 +0,0 @@
-# GC Controller Agent
-
-Evaluate review severity after REVIEW wave and decide whether to trigger a DEV-fix iteration or converge the pipeline.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `agents/gc-controller.md`
-- **Responsibility**: Evaluate review severity, decide DEV-fix vs convergence
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Load review results from completed REVIEW tasks
-- Evaluate gc_signal and review_score to determine decision
-- Respect max iteration count to prevent infinite loops
-- Produce structured output with clear CONVERGE/FIX/ESCALATE decision
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Modify source code directly
-- Produce unstructured output
-- Exceed max iteration count without escalating
-- Ignore Critical findings in review results
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | builtin | Load review results and session state |
-| `Write` | builtin | Create FIX task definitions for next wave |
-| `Bash` | builtin | Query session state, count iterations |
-
-### Tool Usage Patterns
-
-**Read Pattern**: Load review results
-```
-Read("{session_folder}/artifacts/review-results.json")
-Read("{session_folder}/session-state.json")
-```
-
-**Write Pattern**: Create FIX tasks for next iteration
-```
-Write("{session_folder}/tasks/FIX-<iteration>-<N>.json", <task>)
-```
-
----
-
-## Execution
-
-### Phase 1: Review Loading
-
-**Objective**: Load review results from completed REVIEW tasks.
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| Review results | Yes | review_score, gc_signal, findings from REVIEW tasks |
-| Session state | Yes | Current iteration count, max iterations |
-| Task analysis | No | Original task-analysis.json for context |
-
-**Steps**:
-
-1. Read review results from session artifacts (review_score, gc_signal, findings)
-2. Read session state to determine current iteration number
-3. Read max_iterations from task-analysis.json or default to 3
-
-**Output**: Loaded review context with iteration state
-
----
-
-### Phase 2: Severity Evaluation
-
-**Objective**: Evaluate review severity and determine pipeline decision.
-
-**Steps**:
-
-1. **Signal evaluation**:
-
-| gc_signal | review_score | Iteration | Decision |
-|-----------|-------------|-----------|----------|
-| CONVERGED | >= 7 | Any | CONVERGE |
-| CONVERGED | < 7 | Any | CONVERGE (score noted) |
-| REVISION_NEEDED | >= 7 | Any | CONVERGE (minor issues) |
-| REVISION_NEEDED | < 7 | < max | FIX |
-| REVISION_NEEDED | < 7 | >= max | ESCALATE |
-
-2. **Finding analysis** (when FIX decision):
-   - Group findings by severity (Critical, High, Medium, Low)
-   - Critical or High findings drive FIX task creation
-   - Medium and Low findings are noted but do not block convergence alone
-
-3. **Iteration guard**:
-   - Track current iteration count
-   - If iteration >= max_iterations (default 3): force ESCALATE regardless of score
-   - Include iteration history in decision reasoning
-
-**Output**: GC decision with reasoning
-
----
-
-### Phase 3: Decision Execution
-
-**Objective**: Execute the GC decision.
-
-| Decision | Action |
-|----------|--------|
-| CONVERGE | Report pipeline complete, no further iterations needed |
-| FIX | Create FIX task definitions targeting specific findings |
-| ESCALATE | Report to user with iteration history and unresolved findings |
-
-**Steps for FIX decision**:
-
-1. Extract actionable findings (Critical and High severity)
-2. Group findings by target file or module
-3. Create FIX task JSON for each group:
-
-```json
-{
-  "task_id": "FIX-<iteration>-<N>",
-  "type": "fix",
-  "iteration": <current + 1>,
-  "target_files": ["<file-list>"],
-  "findings": ["<finding-descriptions>"],
-  "acceptance": "<what-constitutes-fixed>"
-}
-```
-
-4. Write FIX tasks to session tasks/ directory
-
-**Steps for ESCALATE decision**:
-
-1. Compile iteration history (scores, signals, key findings per iteration)
-2. List unresolved Critical/High findings
-3. Report to user with recommendation
-
-**Output**: Decision report with created tasks or escalation details
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Decision: CONVERGE | FIX | ESCALATE
-- Review score: <score>/10
-- GC signal: <signal>
-- Iteration: <current>/<max>
-
-## Review Analysis
-- Critical findings: <count>
-- High findings: <count>
-- Medium findings: <count>
-- Low findings: <count>
-
-## Decision
-- CONVERGE: Pipeline complete, code meets quality threshold
-  OR
-- FIX: Creating <N> fix tasks for iteration <next>
-  1. FIX-<id>: <description> targeting <files>
-  2. FIX-<id>: <description> targeting <files>
-  OR
-- ESCALATE: Max iterations reached, unresolved issues require user input
-  1. Unresolved: <finding-description>
-  2. Unresolved: <finding-description>
-
-## Iteration History
-- Iteration 1: score=<N>, signal=<signal>, findings=<count>
-- Iteration 2: score=<N>, signal=<signal>, findings=<count>
-
-## Reasoning
-- <Why this decision was made>
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Review results not found | Report as error, cannot make GC decision |
-| Missing gc_signal field | Infer from review_score: >= 7 treat as CONVERGED, < 7 as REVISION_NEEDED |
-| Missing review_score field | Infer from gc_signal and findings count |
-| Session state corrupted | Default to iteration 1, note uncertainty |
-| Timeout approaching | Output current decision with "PARTIAL" status |

package/.codex/skills/team-iterdev/agents/task-analyzer.md

@@ -1,206 +0,0 @@
-# Task Analyzer Agent
-
-Analyze task complexity, detect required capabilities, and select the appropriate pipeline mode for iterative development.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `agents/task-analyzer.md`
-- **Responsibility**: Analyze task complexity, detect required capabilities, select pipeline mode
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Parse user requirement to detect project type
-- Analyze complexity by file count and dependency depth
-- Select appropriate pipeline mode based on analysis
-- Produce structured output with task-analysis JSON
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Modify source code or project files
-- Produce unstructured output
-- Select pipeline mode without analyzing the codebase
-- Begin implementation work
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | builtin | Load project files, configs, package manifests |
-| `Glob` | builtin | Discover project files and estimate scope |
-| `Grep` | builtin | Detect frameworks, dependencies, patterns |
-| `Bash` | builtin | Run detection commands, count files |
-
-### Tool Usage Patterns
-
-**Glob Pattern**: Estimate scope by file discovery
-```
-Glob("src/**/*.ts")
-Glob("**/*.test.*")
-Glob("**/package.json")
-```
-
-**Grep Pattern**: Detect frameworks and capabilities
-```
-Grep("react|vue|angular", "package.json")
-Grep("jest|vitest|mocha", "package.json")
-```
-
-**Read Pattern**: Load project configuration
-```
-Read("package.json")
-Read("tsconfig.json")
-Read("pyproject.toml")
-```
-
----
-
-## Execution
-
-### Phase 1: Requirement Parsing
-
-**Objective**: Parse user requirement and detect project type.
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| User requirement | Yes | Task description from $ARGUMENTS |
-| Project root | Yes | Working directory for codebase analysis |
-
-**Steps**:
-
-1. Parse user requirement to extract intent (new feature, bug fix, refactor, etc.)
-2. Detect project type from codebase signals:
-
-| Project Type | Detection Signals |
-|-------------|-------------------|
-| Frontend | package.json with react/vue/angular, src/**/*.tsx |
-| Backend | server.ts, app.py, go.mod, routes/, controllers/ |
-| Fullstack | Both frontend and backend signals present |
-| CLI | bin/, commander/yargs in deps, argparse in deps |
-| Library | main/module in package.json, src/lib/, no app entry |
-
-3. Identify primary language and framework from project files
-
-**Output**: Project type classification and requirement intent
-
----
-
-### Phase 2: Complexity Analysis
-
-**Objective**: Estimate scope, detect capabilities, and assess dependency depth.
-
-**Steps**:
-
-1. **Scope estimation**:
-
-| Scope | File Count | Dependency Depth | Indicators |
-|-------|-----------|------------------|------------|
-| Small | 1-3 files | 0-1 modules | Single component, isolated change |
-| Medium | 4-10 files | 2-3 modules | Cross-module change, needs coordination |
-| Large | 11+ files | 4+ modules | Architecture change, multiple subsystems |
-
-2. **Capability detection**:
-   - Language: TypeScript, Python, Go, Java, etc.
-   - Testing framework: jest, vitest, pytest, go test, etc.
-   - Build system: webpack, vite, esbuild, setuptools, etc.
-   - Linting: eslint, prettier, ruff, etc.
-   - Type checking: tsc, mypy, etc.
-
-3. **Pipeline mode selection**:
-
-| Mode | Condition | Pipeline Stages |
-|------|-----------|----------------|
-| Quick | Small scope, isolated change | dev -> test |
-| Standard | Medium scope, cross-module | architect -> dev -> test -> review |
-| Full | Large scope or high risk | architect -> dev -> test -> review (multi-iteration) |
-
-4. **Risk assessment**:
-   - Breaking change potential (public API modifications)
-   - Test coverage gaps (areas without existing tests)
-   - Dependency complexity (shared modules, circular refs)
-
-**Output**: Scope, capabilities, pipeline mode, and risk assessment
-
----
-
-### Phase 3: Analysis Report
-
-**Objective**: Write task-analysis result as structured JSON.
-
-**Steps**:
-
-1. Assemble task-analysis JSON:
-
-```json
-{
-  "project_type": "<frontend|backend|fullstack|cli|library>",
-  "intent": "<feature|bugfix|refactor|test|docs>",
-  "scope": "<small|medium|large>",
-  "pipeline_mode": "<quick|standard|full>",
-  "capabilities": {
-    "language": "<primary-language>",
-    "framework": "<primary-framework>",
-    "test_framework": "<test-framework>",
-    "build_system": "<build-system>"
-  },
-  "affected_files": ["<estimated-file-list>"],
-  "risk_factors": ["<risk-1>", "<risk-2>"],
-  "max_iterations": <1|2|3>
-}
-```
-
-2. Report analysis summary to user
-
-**Output**: task-analysis.json written to session artifacts
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Project: <project-type> (<language>/<framework>)
-- Scope: <small|medium|large> (~<N> files)
-- Pipeline: <quick|standard|full>
-
-## Capabilities Detected
-- Language: <language>
-- Framework: <framework>
-- Testing: <test-framework>
-- Build: <build-system>
-
-## Complexity Assessment
-- File count: <N> files affected
-- Dependency depth: <N> modules
-- Risk factors: <list>
-
-## Pipeline Selection
-- Mode: <mode> — <rationale>
-- Stages: <stage-1> -> <stage-2> -> ...
-- Max iterations: <N>
-
-## Task Analysis JSON
-- Written to: <session>/artifacts/task-analysis.json
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Empty project directory | Report as unknown project type, default to standard pipeline |
-| No package manifest found | Infer from file extensions, note reduced confidence |
-| Ambiguous project type | Report both candidates, select most likely |
-| Cannot determine scope | Default to medium, note uncertainty |
-| Timeout approaching | Output current analysis with "PARTIAL" status |