claude-code-workflow 7.2.15 → 7.2.16

package/.codex/skills/team-frontend-debug/agents/conditional-skip-gate.md

@@ -1,130 +0,0 @@
-# Conditional Skip Gate Agent
-
-Interactive agent for evaluating TEST-001 results and determining whether to skip downstream tasks (ANALYZE, FIX, VERIFY) when no issues are found.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `agents/conditional-skip-gate.md`
-- **Responsibility**: Read TEST results, evaluate issue severity, decide skip/proceed
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Read the TEST-001 issues JSON
-- Evaluate issue count and severity distribution
-- Apply conditional skip logic
-- Present decision to user when only warnings exist
-- Produce structured output following template
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Auto-skip when high/medium issues exist
-- Modify test artifacts directly
-- Produce unstructured output
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | built-in | Load test results and issues |
-| `request_user_input` | built-in | Get user decision on warnings |
-| `Write` | built-in | Store gate decision result |
-
----
-
-## Execution
-
-### Phase 1: Load Test Results
-
-**Objective**: Load TEST-001 issues and evaluate severity
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| TEST-001-issues.json | Yes | Discovered issues with severity |
-| TEST-001-report.md | No | Full test report |
-
-**Steps**:
-
-1. Extract session path from task assignment
-2. Read TEST-001-issues.json
-3. Parse issues array
-4. Count by severity: high, medium, low, warning
-
-**Output**: Issue severity distribution
-
----
-
-### Phase 2: Skip Decision
-
-**Objective**: Apply conditional skip logic
-
-**Steps**:
-
-1. Evaluate issues:
-
-| Condition | Action |
-|-----------|--------|
-| `issues.length === 0` | Skip all downstream. Report "all_pass". |
-| Only low/warning severity | Ask user: fix or complete |
-| Any high/medium severity | Proceed with ANALYZE -> FIX -> VERIFY |
-
-2. If only warnings, present choice:
-
-```javascript
-request_user_input({
-  questions: [{
-    question: "Testing found only low-severity warnings. How would you like to proceed?",
-    header: "Test Results",
-    id: "warning_decision",
-    options: [
-      { label: "Fix warnings (Recommended)", description: "Proceed with analysis and fixes for warnings" },
-      { label: "Complete", description: "Accept current state, skip remaining tasks" }
-    ]
-  }]
-})
-```
-
-3. Handle response and record decision
-
-**Output**: Skip/proceed directive
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Test report evaluated: TEST-001
-- Issues found: <total>
-- High: <count>, Medium: <count>, Low: <count>, Warning: <count>
-- Decision: <all_pass|skip_warnings|proceed>
-
-## Findings
-- All features tested: <count>
-- Pass rate: <percentage>
-
-## Decision Details
-- Action: <skip-downstream|proceed-with-fixes>
-- Downstream tasks affected: ANALYZE-001, FIX-001, VERIFY-001
-- User choice: <if applicable>
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| TEST-001-issues.json not found | Report error, cannot evaluate |
-| Issues JSON malformed | Report parse error, default to proceed |
-| User does not respond | Timeout, default to proceed with fixes |

package/.codex/skills/team-frontend-debug/agents/iteration-handler.md

@@ -1,120 +0,0 @@
-# Iteration Handler Agent
-
-Interactive agent for handling the analyzer's request for more evidence. Creates supplemental reproduction and re-analysis tasks when root cause analysis confidence is low.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `agents/iteration-handler.md`
-- **Responsibility**: Parse analyzer evidence request, create REPRODUCE-002 + ANALYZE-002 tasks, update dependency chain
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Read the analyzer's need_more_evidence request
-- Parse specific evidence dimensions and actions requested
-- Create supplemental reproduction task description
-- Create re-analysis task description
-- Update FIX dependency to point to new ANALYZE task
-- Produce structured output following template
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Ignore the analyzer's specific requests
-- Create tasks beyond iteration bounds (max 2 reproduction rounds)
-- Modify existing task artifacts
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | built-in | Load analyzer output and session state |
-| `Write` | built-in | Store iteration handler result |
-
----
-
-## Execution
-
-### Phase 1: Parse Evidence Request
-
-**Objective**: Understand what additional evidence the analyzer needs
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| Analyzer findings | Yes | Contains need_more_evidence with specifics |
-| Session state | No | Current iteration count |
-
-**Steps**:
-
-1. Extract session path from task assignment
-2. Read analyzer's findings or RCA report (partial)
-3. Parse evidence request:
-   - Additional dimensions needed (network_detail, state_inspection, etc.)
-   - Specific actions (capture request body, evaluate React state, etc.)
-4. Check current iteration count
-
-**Output**: Parsed evidence request
-
----
-
-### Phase 2: Create Iteration Tasks
-
-**Objective**: Build task descriptions for supplemental reproduction and re-analysis
-
-**Steps**:
-
-1. Check iteration bounds:
-
-| Condition | Action |
-|-----------|--------|
-| Reproduction rounds < 2 | Create REPRODUCE-002 + ANALYZE-002 |
-| Reproduction rounds >= 2 | Escalate to user for manual investigation |
-
-2. Build REPRODUCE-002 description with specific evidence requests from analyzer
-
-3. Build ANALYZE-002 description that loads both original and supplemental evidence
-
-4. Record new tasks and dependency updates
-
-**Output**: Task descriptions for dynamic wave extension
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Analyzer evidence request processed
-- Iteration round: <current>/<max>
-- Action: <create-reproduction|escalate>
-
-## Evidence Request
-- Dimensions needed: <list>
-- Specific actions: <list>
-
-## Tasks Created
-- REPRODUCE-002: <description summary>
-- ANALYZE-002: <description summary>
-
-## Dependency Updates
-- FIX-001 deps updated: ANALYZE-001 -> ANALYZE-002
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Evidence request unclear | Use all default dimensions |
-| Max iterations reached | Escalate to user |
-| Session state missing | Default to iteration round 1 |

package/.codex/skills/team-frontend-debug/instructions/agent-instruction.md

@@ -1,272 +0,0 @@
-# Agent Instruction Template -- Team Frontend Debug
-
-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}.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 Frontend Debug
-
-### 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}
-**Pipeline Mode**: {pipeline_mode}
-**Base URL**: {base_url}
-**Evidence Dimensions**: {evidence_dimensions}
-
-### 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**: Follow role-specific instructions below
-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
-- `feature_tested`: {feature, name, result, issues} -- Feature test result
-- `bug_reproduced`: {url, steps, console_errors, network_failures} -- Bug reproduction outcome
-- `evidence_collected`: {dimension, file, description} -- Evidence artifact saved
-- `root_cause_found`: {category, file, line, confidence} -- Root cause identified
-- `file_modified`: {file, change, lines_added} -- Code fix applied
-- `verification_result`: {verdict, original_error_resolved, new_errors} -- Verification outcome
-- `issue_found`: {file, line, severity, description} -- Issue discovered
-
----
-
-## 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",
-  "issues_count": "",
-  "verdict": "",
-  "error": ""
-}
-```
-
----
-
-## Role-Specific Customization
-
-The coordinator generates per-role instruction variants during Phase 1.
-
-### For Tester Role (test-pipeline)
-
-```
-3. **Execute**:
-   - Parse feature list from task description
-   - For each feature:
-     a. Navigate to feature URL: mcp__chrome-devtools__navigate_page({ type: "url", url: "<base_url><path>" })
-     b. Wait for page load: mcp__chrome-devtools__wait_for({ text: ["<expected>"], timeout: 10000 })
-     c. Explore page structure: mcp__chrome-devtools__take_snapshot()
-     d. Generate test scenarios from UI elements if not predefined
-     e. Capture baseline: take_screenshot (before), list_console_messages
-     f. Execute test steps: map step descriptions to MCP actions
-        - Click: take_snapshot -> find uid -> click({ uid })
-        - Fill: take_snapshot -> find uid -> fill({ uid, value })
-        - Hover: take_snapshot -> find uid -> hover({ uid })
-        - Wait: wait_for({ text: ["expected"] })
-        - Navigate: navigate_page({ type: "url", url: "path" })
-        - Press key: press_key({ key: "Enter" })
-     g. Capture result: take_screenshot (after), list_console_messages (errors), list_network_requests
-     h. Evaluate: console errors? network failures? expected text present? visual issues?
-     i. Classify: pass / fail / warning
-   - Compile test report: <session>/artifacts/TEST-001-report.md
-   - Compile issues list: <session>/artifacts/TEST-001-issues.json
-   - Set issues_count in output
-```
-
-### For Reproducer Role (debug-pipeline)
-
-```
-3. **Execute**:
-   - Verify browser accessible: mcp__chrome-devtools__list_pages()
-   - Navigate to target URL: mcp__chrome-devtools__navigate_page({ type: "url", url: "<target>" })
-   - Wait for load: mcp__chrome-devtools__wait_for({ text: ["<expected>"], timeout: 10000 })
-   - Capture baseline evidence:
-     - Screenshot (before): take_screenshot({ filePath: "<session>/evidence/before-screenshot.png" })
-     - DOM snapshot (before): take_snapshot({ filePath: "<session>/evidence/before-snapshot.txt" })
-     - Console baseline: list_console_messages()
-   - Execute reproduction steps:
-     - For each step, parse action and execute via MCP tools
-     - Track DOM changes via snapshots after key steps
-   - Capture post-action evidence:
-     - Screenshot (after): take_screenshot({ filePath: "<session>/evidence/after-screenshot.png" })
-     - DOM snapshot (after): take_snapshot({ filePath: "<session>/evidence/after-snapshot.txt" })
-     - Console errors: list_console_messages({ types: ["error", "warn"] })
-     - Network requests: list_network_requests({ resourceTypes: ["xhr", "fetch"] })
-     - Request details for failures: get_network_request({ reqid: <id> })
-     - Performance trace (if dimension): performance_start_trace() + reproduce + performance_stop_trace()
-   - Write evidence-summary.json to <session>/evidence/
-```
-
-### For Analyzer Role
-
-```
-3. **Execute**:
-   - Load evidence from upstream (reproducer evidence/ or tester artifacts/)
-   - Console error analysis (priority):
-     - Filter by type: error > warn > log
-     - Extract stack traces, identify source file:line
-     - Classify: TypeError, ReferenceError, NetworkError, etc.
-   - Network analysis (if dimension):
-     - Identify failed requests (4xx, 5xx, timeout, CORS)
-     - Check auth tokens, API endpoints, payload issues
-   - DOM structure analysis (if snapshots):
-     - Compare before/after snapshots
-     - Identify missing/extra elements, attribute anomalies
-   - Performance analysis (if trace):
-     - Identify long tasks (>50ms), layout thrashing, memory leaks
-   - Cross-correlation: build timeline, identify trigger point
-   - Source code mapping:
-     - Use mcp__ace-tool__search_context or Grep to locate root cause
-     - Read identified source files
-   - Confidence assessment:
-     - High (>80%): clear stack trace + specific line
-     - Medium (50-80%): likely cause, needs confirmation
-     - Low (<50%): request more evidence (set findings to include "need_more_evidence")
-   - Write RCA report to <session>/artifacts/ANALYZE-001-rca.md
-   - Set issues_count in output
-```
-
-### For Fixer Role
-
-```
-3. **Execute**:
-   - Load RCA report from analyzer output
-   - Extract root cause: category, file, line, recommended fix
-   - Read identified source files
-   - Search for similar patterns: mcp__ace-tool__search_context
-   - Plan fix: minimal change addressing root cause
-   - Apply fix strategy by category:
-     - TypeError/null: add null check, default value
-     - API error: fix URL, add error handling
-     - Missing import: add import statement
-     - CSS/rendering: fix styles, layout
-     - State bug: fix state update logic
-     - Race condition: add async handling
-   - Implement fix using Edit tool (fallback: mcp__ccw-tools__edit_file)
-   - Validate: run syntax/type checks
-   - Document changes in <session>/artifacts/FIX-001-changes.md
-```
-
-### For Verifier Role
-
-```
-3. **Execute**:
-   - Load original evidence (reproducer) and fix changes (fixer)
-   - Pre-verification: check modified files contain expected changes
-   - Navigate to same URL: mcp__chrome-devtools__navigate_page
-   - Execute EXACT same reproduction/test steps
-   - Capture post-fix evidence:
-     - Screenshot: take_screenshot({ filePath: "<session>/evidence/verify-screenshot.png" })
-     - DOM snapshot: take_snapshot({ filePath: "<session>/evidence/verify-snapshot.txt" })
-     - Console: list_console_messages({ types: ["error", "warn"] })
-     - Network: list_network_requests({ resourceTypes: ["xhr", "fetch"] })
-   - Compare evidence:
-     - Console: original error gone?
-     - Network: failed request now succeeds?
-     - Visual: expected rendering achieved?
-     - New errors: any regression?
-   - Determine verdict:
-     - pass: original resolved AND no new errors
-     - pass_with_warnings: original resolved BUT new issues
-     - fail: original still present
-   - Write verification report to <session>/artifacts/VERIFY-001-report.md
-   - Set verdict in output
-```
-
----
-
-## Chrome DevTools MCP Reference
-
-### Common Patterns
-
-**Navigate and Wait**:
-```
-mcp__chrome-devtools__navigate_page({ type: "url", url: "<url>" })
-mcp__chrome-devtools__wait_for({ text: ["<expected>"], timeout: 10000 })
-```
-
-**Find Element and Interact**:
-```
-mcp__chrome-devtools__take_snapshot()  // Get uids
-mcp__chrome-devtools__click({ uid: "<uid>" })
-mcp__chrome-devtools__fill({ uid: "<uid>", value: "<value>" })
-```
-
-**Capture Evidence**:
-```
-mcp__chrome-devtools__take_screenshot({ filePath: "<path>" })
-mcp__chrome-devtools__list_console_messages({ types: ["error", "warn"] })
-mcp__chrome-devtools__list_network_requests({ resourceTypes: ["xhr", "fetch"] })
-```
-
-**Debug API Error**:
-```
-mcp__chrome-devtools__list_network_requests()  // Find request
-mcp__chrome-devtools__get_network_request({ reqid: <id> })  // Inspect details
-```
-
----
-
-## Quality Requirements
-
-All agents must verify before reporting complete:
-
-| Requirement | Criteria |
-|-------------|----------|
-| Files produced | Verify all claimed artifacts exist via Read |
-| Evidence captured | All planned dimensions have evidence files |
-| Findings accuracy | Findings reflect actual observations |
-| Discovery sharing | At least 1 discovery shared to board |
-| Error reporting | Non-empty error field if status is failed |
-| Verdict set | verifier role sets verdict field |
-| Issues count set | tester/analyzer roles set issues_count field |
-
----
-
-## 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 |
-| `{pipeline_mode}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{base_url}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{evidence_dimensions}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{prev_context}` | spawn_agents_on_csv | Runtime from CSV row |