claude-code-workflow 7.2.15 → 7.2.16

package/.codex/skills/team-planex-v2/instructions/agent-instruction.md

@@ -1,193 +0,0 @@
-# Agent Instruction -- Team PlanEx
-
-CSV agent instruction template for `spawn_agents_on_csv`. Each agent receives this template with its row's column values substituted via `{column_name}` placeholders.
-
----
-
-## TASK ASSIGNMENT
-
-### MANDATORY FIRST STEPS
-1. Read shared discoveries: `.workflow/.csv-wave/{session_id}/discoveries.ndjson` (if exists, skip if not)
-2. Read project context: `.workflow/project-tech.json` (if exists)
-3. Read wisdom files: `.workflow/.csv-wave/{session_id}/wisdom/` (conventions, learnings)
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Description**: {description}
-**Role**: {role}
-**Issue IDs**: {issue_ids}
-**Input Type**: {input_type}
-**Raw Input**: {raw_input}
-**Execution Method**: {execution_method}
-
-### Previous Tasks' Findings (Context)
-{prev_context}
-
----
-
-## Execution Protocol
-
-### Role Router
-
-Determine your execution steps based on `{role}`:
-
-| Role | Execution Steps |
-|------|----------------|
-| planner | Step A: Solution Planning |
-| executor | Step B: Implementation |
-
----
-
-### Step A: Solution Planning (planner role)
-
-1. Parse issue ID from `{issue_ids}`
-2. Determine input source from `{input_type}`:
-
-| Input Type | Action |
-|------------|--------|
-| `issues` | Load issue details: `Bash("ccw issue status {issue_ids} --json")` |
-| `text` | Create issue from text: `Bash("ccw issue create --title '<derived>' --context '{raw_input}'")` |
-| `plan` | Read plan file: `Read("{raw_input}")`, parse into issue requirements |
-
-3. Generate solution via CLI:
-   ```bash
-   ccw cli -p "PURPOSE: Generate implementation solution for issue <issueId>; success = actionable task breakdown with file paths
-   TASK: * Load issue details * Analyze requirements * Design solution approach * Break down into implementation tasks * Identify files to modify/create
-   MODE: analysis
-   CONTEXT: @**/* | Memory: Session wisdom
-   EXPECTED: JSON solution with: title, description, tasks array (each with description, files_touched), estimated_complexity
-   CONSTRAINTS: Follow project patterns | Reference existing implementations
-   " --tool gemini --mode analysis --rule planning-breakdown-task-steps
-   ```
-
-4. Parse CLI output to extract solution JSON
-
-5. Write solution artifact:
-   ```javascript
-   Write("<session>/artifacts/solutions/<issueId>.json", JSON.stringify({
-     session_id: "<session-id>",
-     issue_id: "<issueId>",
-     solution: solutionFromCli,
-     planned_at: new Date().toISOString()
-   }))
-   ```
-
-6. Check for file conflicts with other solutions in session:
-   - Read other solution files in `<session>/artifacts/solutions/`
-   - Compare `files_touched` lists
-   - If overlapping files found, log warning to discoveries.ndjson
-
-7. Share discoveries to board:
-   ```bash
-   echo '{"ts":"<ISO8601>","worker":"{id}","type":"solution_designed","data":{"issue_id":"<issueId>","approach":"<approach>","task_count":<N>,"estimated_files":<M>}}' >> <session>/discoveries.ndjson
-   ```
-
----
-
-### Step B: Implementation (executor role)
-
-1. Parse issue ID from `{issue_ids}`
-
-2. Load solution artifact:
-   - Primary: Read file from prev_context artifact_path
-   - Fallback: `Read("<session>/artifacts/solutions/<issueId>.json")`
-   - Last resort: `Bash("ccw issue solutions <issueId> --json")`
-
-3. Load wisdom files for conventions and patterns
-
-4. Determine execution backend from `{execution_method}`:
-
-| Method | CLI Command |
-|--------|-------------|
-| codex | `ccw cli --tool codex --mode write --id exec-<issueId>` |
-| gemini | `ccw cli --tool gemini --mode write --id exec-<issueId>` |
-| qwen | `ccw cli --tool qwen --mode write --id exec-<issueId>` |
-
-5. Execute implementation via CLI:
-   ```bash
-   ccw cli -p "PURPOSE: Implement solution for issue <issueId>; success = all tasks completed, tests pass
-   TASK: <solution.tasks as bullet points>
-   MODE: write
-   CONTEXT: @**/* | Memory: Solution plan, session wisdom
-   EXPECTED: Working implementation with code changes, test updates, no syntax errors
-   CONSTRAINTS: Follow existing patterns | Maintain backward compatibility
-   Issue: <issueId>
-   Title: <solution.title>
-   Solution: <solution JSON>" --tool <execution_method> --mode write --rule development-implement-feature
-   ```
-
-6. Verify implementation:
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| Tests | Detect and run project test command | All pass |
-| Syntax | IDE diagnostics or `tsc --noEmit` | No errors |
-
-   If tests fail: retry implementation once, then report as failed.
-
-7. Commit changes:
-   ```bash
-   git add -A
-   git commit -m "feat(<issueId>): <solution.title>"
-   ```
-
-8. Update issue status:
-   ```bash
-   ccw issue update <issueId> --status completed
-   ```
-
-9. Share discoveries to board:
-   ```bash
-   echo '{"ts":"<ISO8601>","worker":"{id}","type":"impl_result","data":{"issue_id":"<issueId>","files_changed":<N>,"tests_pass":<bool>,"commit":"<hash>"}}' >> <session>/discoveries.ndjson
-   ```
-
----
-
-## Share Discoveries (ALL ROLES)
-
-After completing your work, append findings to the shared discovery board:
-
-```bash
-echo '{"ts":"<ISO8601>","worker":"{id}","type":"<type>","data":{...}}' >> <session>/discoveries.ndjson
-```
-
-**Discovery Types to Share**:
-
-| Type | Data Schema | When to Use |
-|------|-------------|-------------|
-| `solution_designed` | `{issue_id, approach, task_count, estimated_files}` | Planner: solution plan completed |
-| `conflict_warning` | `{issue_ids, overlapping_files}` | Planner: file overlap between issues |
-| `pattern_found` | `{pattern, location, description}` | Any: code pattern identified |
-| `impl_result` | `{issue_id, files_changed, tests_pass, commit}` | Executor: implementation outcome |
-| `test_failure` | `{issue_id, test_file, error_msg}` | Executor: test failure |
-
----
-
-## Output (report_agent_job_result)
-
-Return JSON:
-```json
-{
-  "id": "{id}",
-  "status": "completed | failed",
-  "findings": "Key discoveries and implementation notes (max 500 chars)",
-  "artifact_path": "relative path to main artifact (e.g., artifacts/solutions/ISS-xxx.json or builds/ISS-xxx.json)",
-  "error": ""
-}
-```
-
----
-
-## Quality Checklist
-
-Before reporting complete:
-- [ ] Mandatory first steps completed (discoveries, project context, wisdom)
-- [ ] Role-specific execution steps followed
-- [ ] At least 1 discovery shared to board
-- [ ] Artifact file written to session folder
-- [ ] Findings include actionable details (file paths, task counts, etc.)
-- [ ] prev_context findings were incorporated where available

package/.codex/skills/team-planex-v2/schemas/tasks-schema.md

@@ -1,206 +0,0 @@
-# Team PlanEx -- CSV Schema
-
-## Master CSV: tasks.csv
-
-### Column Definitions
-
-#### Input Columns (Set by Decomposer)
-
-| Column | Type | Required | Description | Example |
-|--------|------|----------|-------------|---------|
-| `id` | string | Yes | Unique task identifier | `"PLAN-001"` |
-| `title` | string | Yes | Short task title | `"Plan ISS-20260308-120000"` |
-| `description` | string | Yes | Detailed task description (self-contained) | `"Generate implementation solution for issue ISS-20260308-120000"` |
-| `role` | enum | Yes | Worker role: `planner` or `executor` | `"planner"` |
-| `issue_ids` | string | Yes | Semicolon-separated issue IDs | `"ISS-20260308-120000"` |
-| `input_type` | string | No | Input source type (planner only): `issues`, `text`, or `plan` | `"issues"` |
-| `raw_input` | string | No | Raw input text (planner only) | `"ISS-20260308-120000"` |
-| `exec_mode` | enum | Yes | Execution mechanism: `csv-wave` or `interactive` | `"csv-wave"` |
-| `execution_method` | string | No | CLI tool for EXEC tasks: codex, gemini, qwen, or empty | `"gemini"` |
-| `deps` | string | No | Semicolon-separated dependency task IDs | `"PLAN-001"` |
-| `context_from` | string | No | Semicolon-separated task IDs for context | `"PLAN-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) | `"[PLAN-001] Designed 4-task solution..."` |
-
-#### Output Columns (Set by Agent)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `status` | enum | `pending` -> `completed` / `failed` / `skipped` | `"completed"` |
-| `findings` | string | Key discoveries (max 500 chars) | `"Solution designed with 4 implementation tasks..."` |
-| `artifact_path` | string | Path to generated artifact file | `"artifacts/solutions/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 (edge cases) |
-
-> In standard PlanEx, all tasks use `csv-wave`. Interactive mode is reserved for rare multi-round coordination scenarios.
-
----
-
-### Role Values
-
-| Role | Task Prefixes | Responsibility |
-|------|---------------|----------------|
-| `planner` | PLAN-* | Requirement decomposition, solution design, issue creation |
-| `executor` | EXEC-* | Solution implementation, testing, verification, commit |
-
----
-
-### Example Data
-
-```csv
-id,title,description,role,issue_ids,input_type,raw_input,exec_mode,execution_method,deps,context_from,wave,status,findings,artifact_path,error
-"PLAN-001","Plan issue-1","Generate solution for ISS-20260308-120000","planner","ISS-20260308-120000","issues","ISS-20260308-120000","csv-wave","","","","1","pending","","",""
-"PLAN-002","Plan issue-2","Generate solution for ISS-20260308-120001","planner","ISS-20260308-120001","issues","ISS-20260308-120001","csv-wave","","","","1","pending","","",""
-"EXEC-001","Implement issue-1","Implement solution for ISS-20260308-120000","executor","ISS-20260308-120000","","","csv-wave","gemini","PLAN-001","PLAN-001","2","pending","","",""
-"EXEC-002","Implement issue-2","Implement solution for ISS-20260308-120001","executor","ISS-20260308-120001","","","csv-wave","gemini","PLAN-002","PLAN-002","2","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)
-input_type  ---------->  input_type  ---------->  (reads, planner)
-raw_input   ---------->  raw_input   ---------->  (reads, planner)
-exec_mode   ---------->  exec_mode   ---------->  (reads)
-execution_method ------>  execution_method ----->  (reads, executor)
-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": "PLAN-001",
-  "status": "completed",
-  "findings": "Designed solution for ISS-20260308-120000: 4 implementation tasks, 6 files affected. Approach: refactor authentication handler to support token refresh.",
-  "artifact_path": "artifacts/solutions/ISS-20260308-120000.json",
-  "error": ""
-}
-```
-
----
-
-## Discovery Types
-
-| Type | Dedup Key | Data Schema | Description |
-|------|-----------|-------------|-------------|
-| `solution_designed` | `issue_id` | `{issue_id, approach, task_count, estimated_files}` | Planner: solution plan completed |
-| `conflict_warning` | `issue_ids` | `{issue_ids, overlapping_files}` | Planner: file overlap between issues |
-| `pattern_found` | `pattern+location` | `{pattern, location, description}` | Any: code pattern identified |
-| `impl_result` | `issue_id` | `{issue_id, files_changed, tests_pass, commit}` | Executor: implementation outcome |
-| `test_failure` | `issue_id` | `{issue_id, test_file, error_msg}` | Executor: test failure details |
-
-### Discovery NDJSON Format
-
-```jsonl
-{"ts":"2026-03-08T10:00:00Z","worker":"PLAN-001","type":"solution_designed","data":{"issue_id":"ISS-20260308-120000","approach":"refactor","task_count":4,"estimated_files":6}}
-{"ts":"2026-03-08T10:05:00Z","worker":"PLAN-002","type":"conflict_warning","data":{"issue_ids":["ISS-20260308-120000","ISS-20260308-120001"],"overlapping_files":["src/auth/handler.ts"]}}
-{"ts":"2026-03-08T10:10:00Z","worker":"EXEC-001","type":"impl_result","data":{"issue_id":"ISS-20260308-120000","files_changed":3,"tests_pass":true,"commit":"abc123"}}
-```
-
-> All agents (planner and executor) read/write the same discoveries.ndjson file.
-
----
-
-## Cross-Wave Context Flow
-
-| Source | Target | Mechanism |
-|--------|--------|-----------|
-| PLAN-N findings | EXEC-N prev_context | Injected via prev_context column in wave-2.csv |
-| PLAN-N artifact_path | EXEC-N | Executor reads solution file from artifact_path |
-| Any agent discovery | Any agent | Shared via discoveries.ndjson |
-
----
-
-## Pipeline Structure
-
-### Standard Two-Wave Pipeline
-
-| Wave | Tasks | Role | Parallelism |
-|------|-------|------|-------------|
-| 1 | PLAN-001..N | planner | All concurrent (up to max_concurrency) |
-| 2 | EXEC-001..N | executor | All concurrent (up to max_concurrency) |
-
-Each EXEC-NNN depends on its corresponding PLAN-NNN. If PLAN-NNN fails, EXEC-NNN is automatically skipped.
-
----
-
-## Solution Artifact Schema
-
-Written by planner agents to `artifacts/solutions/{issueId}.json`:
-
-```json
-{
-  "session_id": "planex-xxx-20260308",
-  "issue_id": "ISS-20260308-120000",
-  "solution": {
-    "title": "Add rate limiting middleware",
-    "approach": "Create express middleware with sliding window",
-    "tasks": [
-      {
-        "order": 1,
-        "description": "Create rate limiter middleware in src/middleware/rate-limit.ts",
-        "files_touched": ["src/middleware/rate-limit.ts"]
-      },
-      {
-        "order": 2,
-        "description": "Add per-route configuration in src/config/routes.ts",
-        "files_touched": ["src/config/routes.ts"]
-      }
-    ],
-    "estimated_complexity": "Medium",
-    "estimated_files": 4
-  },
-  "planned_at": "2026-03-08T10:00:00Z"
-}
-```
-
----
-
-## 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 {planner, executor} | "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" |
-| EXEC deps on PLAN | Every EXEC-N must depend on PLAN-N | "EXEC task without PLAN dependency: {id}" |
-| Issue IDs non-empty | Every task has at least one issue_id | "No issue_ids for task: {id}" |

package/.codex/skills/team-quality-assurance/agents/executor.md

@@ -1,192 +0,0 @@
-# Test Executor Agent
-
-Interactive agent that executes test suites, collects coverage, and performs iterative auto-fix cycles. Acts as the Critic in the Generator-Critic loop within the QA pipeline.
-
-## Identity
-
-- **Type**: `interactive`
-- **Responsibility**: Validation (test execution with fix cycles)
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Run test suites using the correct framework command
-- Collect coverage data from test output or coverage reports
-- Attempt auto-fix for failing tests (max 5 iterations per invocation)
-- Only modify test files, NEVER modify source code
-- Save results to session results directory
-- Share defect discoveries to discoveries.ndjson
-- Report pass rate and coverage in structured output
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Modify source code (only test files may be changed)
-- Use `@ts-ignore`, `as any`, or skip/ignore test annotations
-- Exceed 5 fix iterations without reporting current state
-- Delete or disable existing passing tests
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | file-read | Load test files, source files, strategy, results |
-| `Write` | file-write | Save test results, update test files |
-| `Edit` | file-edit | Fix test assertions, imports, mocks |
-| `Bash` | shell | Run test commands, collect coverage |
-| `Glob` | search | Find test files in session directory |
-| `Grep` | search | Find patterns in test output |
-
----
-
-## Execution
-
-### Phase 1: Context Loading
-
-**Objective**: Detect test framework and locate test files.
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| Session folder | Yes | Path to session directory |
-| Layer | Yes | Target test layer (L1/L2/L3) |
-| Coverage target | Yes | Minimum coverage percentage |
-| Previous context | No | Findings from generator and scout |
-
-**Steps**:
-
-1. Read discoveries.ndjson for framework detection info
-2. Determine layer directory:
-   - L1 -> tests/L1-unit/
-   - L2 -> tests/L2-integration/
-   - L3 -> tests/L3-e2e/
-3. Find test files in the layer directory
-4. Determine test framework command:
-
-| Framework | Command Template |
-|-----------|-----------------|
-| vitest | `npx vitest run --coverage --reporter=json <test-dir>` |
-| jest | `npx jest --coverage --json --outputFile=<results-path> <test-dir>` |
-| pytest | `python -m pytest --cov --cov-report=json -v <test-dir>` |
-| mocha | `npx mocha --reporter json > test-results.json` |
-| default | `npm test -- --coverage` |
-
-**Output**: Framework, test command, test file list
-
----
-
-### Phase 2: Iterative Test-Fix Cycle
-
-**Objective**: Run tests and fix failures up to 5 iterations.
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| Test command | Yes | From Phase 1 |
-| Test files | Yes | From Phase 1 |
-| Coverage target | Yes | From spawn message |
-
-**Steps**:
-
-For each iteration (1..5):
-
-1. Run test command, capture stdout/stderr
-2. Parse results: extract passed/failed counts, parse coverage
-3. Evaluate exit condition:
-
-| Condition | Action |
-|-----------|--------|
-| All tests pass (0 failures) | Exit loop: SUCCESS |
-| pass_rate >= 0.95 AND iteration >= 2 | Exit loop: GOOD ENOUGH |
-| iteration >= 5 | Exit loop: MAX ITERATIONS |
-
-4. If not exiting, extract failure details:
-   - Error messages and stack traces
-   - Failing test file:line references
-   - Assertion mismatches
-
-5. Apply targeted fixes:
-   - Fix incorrect assertions (expected vs actual)
-   - Fix missing imports or broken module paths
-   - Fix mock setup issues
-   - Fix async/await handling
-   - Do NOT skip tests, do NOT add type suppressions
-
-6. Share defect discoveries:
-   ```bash
-   echo '{"ts":"<ISO>","worker":"<task-id>","type":"defect_found","data":{"file":"<src>","line":<N>,"pattern":"<type>","description":"<desc>"}}' >> <session>/discoveries.ndjson
-   ```
-
-**Output**: Final pass rate, coverage achieved, iteration count
-
----
-
-### Phase 3: Result Recording
-
-**Objective**: Save execution results and update state.
-
-**Steps**:
-
-1. Build result data:
-   ```json
-   {
-     "layer": "<L1|L2|L3>",
-     "framework": "<detected>",
-     "iterations": <N>,
-     "pass_rate": <decimal>,
-     "coverage": <percentage>,
-     "tests_passed": <N>,
-     "tests_failed": <N>,
-     "all_passed": <boolean>,
-     "defect_patterns": [...]
-   }
-   ```
-
-2. Save results to `<session>/results/run-<layer>.json`
-3. Save last test output to `<session>/results/output-<layer>.txt`
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Test execution for <layer>: <pass_rate> pass rate, <coverage>% coverage after <N> iterations
-
-## Findings
-- Finding 1: specific test result with file:line reference
-- Finding 2: defect pattern discovered
-
-## Defect Patterns
-- Pattern: type, frequency, severity
-- Pattern: type, frequency, severity
-
-## Coverage
-- Overall: <N>%
-- Target: <N>%
-- Gap files: file1 (<N>%), file2 (<N>%)
-
-## Open Questions
-1. Any unresolvable test failures (if any)
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Test command not found | Try alternative commands (npx, npm test), report if all fail |
-| No test files found | Report in findings, status = failed |
-| Coverage tool unavailable | Degrade to pass rate only, report in findings |
-| All tests timeout | Report with partial results, status = failed |
-| Import resolution fails after fix | Report remaining failures, continue with other tests |
-| Timeout approaching | Output current findings with "PARTIAL" status |