claude-code-workflow 7.2.15 → 7.2.16

package/.codex/skills/team-frontend/agents/qa-gate-reviewer.md

@@ -1,153 +0,0 @@
-# QA Gate Reviewer Agent
-
-Interactive agent for reviewing QA audit verdicts and handling the Generator-Critic (GC) loop decision. Spawned when a QA task returns FIX_REQUIRED and the coordinator needs to determine whether to create a fix cycle or escalate.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `agents/qa-gate-reviewer.md`
-- **Responsibility**: Review QA audit verdicts, handle architecture review gates, manage GC loop decisions
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Read the QA audit report being reviewed
-- Present a clear summary of QA findings to the user
-- Wait for user decision before proceeding (if not AUTO_YES)
-- Produce structured output following template
-- Include file:line references in findings
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Auto-approve FIX_REQUIRED verdicts without checking GC round count
-- Modify QA audit artifacts directly
-- Produce unstructured output
-- Exceed defined scope boundaries
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | built-in | Load QA audit reports and context |
-| `request_user_input` | built-in | Get user decision on QA gate |
-| `Write` | built-in | Store review result |
-
-### Tool Usage Patterns
-
-**Read Pattern**: Load context files before review
-```
-Read("<session>/artifacts/qa/audit-*.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 QA audit report and GC loop state
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| QA audit report | Yes | The audit document to review |
-| discoveries.ndjson | No | Shared discoveries for context |
-| Master CSV (tasks.csv) | No | For GC round tracking |
-
-**Steps**:
-
-1. Extract session path from task assignment
-2. Read the QA audit report referenced in the task description
-3. Read discoveries.ndjson for additional context
-4. Check current GC round count from session state
-
-**Output**: QA verdict summary ready for review
-
----
-
-### Phase 2: Gate Decision
-
-**Objective**: Determine next action based on QA verdict
-
-**Steps**:
-
-1. Parse QA verdict from audit report:
-
-| Verdict | GC Round | Action |
-|---------|----------|--------|
-| PASSED | any | Report approved, no fix cycle needed |
-| PASSED_WITH_WARNINGS | any | Report approved with warnings noted |
-| FIX_REQUIRED | < 2 | Create DEV-fix + QA-recheck tasks |
-| FIX_REQUIRED | >= 2 | Escalate to user for manual intervention |
-
-2. If escalation needed, present choice:
-
-```javascript
-request_user_input({
-  questions: [{
-    question: "QA has flagged issues after 2 fix rounds. How would you like to proceed?",
-    header: "QA Gate",
-    id: "qa_gate_decision",
-    options: [
-      { label: "Accept current state (Recommended)", description: "Proceed despite remaining issues" },
-      { label: "Manual fix", description: "You will fix the issues manually" },
-      { label: "Abort pipeline", description: "Stop the pipeline" }
-    ]
-  }]
-})
-```
-
-3. Handle response accordingly
-
-**Output**: Gate decision with action directive
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- QA audit reviewed: <audit-id>
-- Verdict: <PASSED|PASSED_WITH_WARNINGS|FIX_REQUIRED>
-- Score: <score>/10
-- Decision: <approved|fix-cycle|escalated|aborted>
-
-## Findings
-- Critical issues: <count>
-- High issues: <count>
-- Medium issues: <count>
-- Low issues: <count>
-
-## Decision Details
-- GC round: <current>/<max>
-- Action: <proceed|create-fix-cycle|escalate|abort>
-- User feedback: <if applicable>
-
-## Open Questions
-1. Any unresolved items from review
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| QA audit report not found | Report in Open Questions, ask for path |
-| GC round state missing | Default to round 0 |
-| User does not respond | Timeout, report partial with "awaiting-review" status |
-| Processing failure | Output partial results with clear status indicator |

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

@@ -1,197 +0,0 @@
-# Agent Instruction Template -- Team Frontend
-
-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
-
-### 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}
-**Scope**: {scope}
-**Review Type**: {review_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**: 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
-- `tech_stack_detected`: {stack, framework, ui_lib} -- Tech stack identification
-- `design_pattern_found`: {pattern_name, location, description} -- Existing design pattern
-- `token_generated`: {category, count, supports_dark_mode} -- Design token category created
-- `file_modified`: {file, change, lines_added} -- File change performed
-- `issue_found`: {file, line, severity, description} -- Issue discovered
-- `anti_pattern_violation`: {pattern, file, line, description} -- Anti-pattern detected
-- `artifact_produced`: {name, path, producer, type} -- Deliverable 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",
-  "qa_score": "",
-  "qa_verdict": "",
-  "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 Analyst Role
-
-```
-3. **Execute**:
-   - Detect tech stack from package.json (react, nextjs, vue, svelte, html-tailwind)
-   - Detect existing design system via Glob: **/*token*.*, **/*.css
-   - Retrieve design intelligence via ui-ux-pro-max skill:
-     - Full design system: Skill(skill="ui-ux-pro-max", args="<industry> <keywords> --design-system")
-     - UX guidelines: Skill(skill="ui-ux-pro-max", args="accessibility animation responsive --domain ux")
-     - Tech stack guide: Skill(skill="ui-ux-pro-max", args="<keywords> --stack <detected-stack>")
-   - Fallback if skill unavailable: generate from LLM general design knowledge
-   - Analyze existing codebase patterns (color palette, typography, spacing, components)
-   - Optional: WebSearch for "<industry> web design trends best practices"
-   - Compile design-intelligence.json with: _source, industry, detected_stack, design_system, ux_guidelines, stack_guidelines, recommendations
-   - Write requirements.md summarizing all requirements
-   - Output to <session-folder>/artifacts/analysis/
-```
-
-### For Architect Role
-
-```
-3. **Execute**:
-   - Load design-intelligence.json from analyst output
-   - Generate design token system (design-tokens.json) with categories:
-     - color: primary, secondary, background, surface, text, CTA (light + dark mode)
-     - typography: font families, font sizes (scale)
-     - spacing: xs through 2xl
-     - border-radius: sm, md, lg, full
-     - shadow: sm, md, lg
-     - transition: fast, normal, slow
-   - Use $type + $value format (Design Tokens Community Group)
-   - Generate component specs in component-specs/ directory:
-     - Design reference (style, stack)
-     - Props table (name, type, default, description)
-     - Variants table
-     - Accessibility requirements (role, keyboard, ARIA, contrast)
-     - Anti-patterns to avoid
-   - Generate project structure (project-structure.md) using stack-specific layout
-   - Output to <session-folder>/artifacts/architecture/
-```
-
-### For Developer Role
-
-```
-3. **Execute**:
-   - Load design tokens, component specs, and project structure from architect output
-   - Generate CSS custom properties from design-tokens.json:
-     - color -> --color-*, typography -> --font-*, --text-*, spacing -> --space-*
-     - Add @media (prefers-color-scheme: dark) override for color tokens
-   - Implement components following specs and coding standards:
-     - Use design token CSS variables -- never hardcode colors/spacing
-     - All interactive elements: cursor: pointer
-     - Transitions: 150-300ms via var(--duration-normal)
-     - Text contrast: minimum 4.5:1 ratio
-     - Include focus-visible styles for keyboard navigation
-     - Support prefers-reduced-motion
-     - Responsive: mobile-first with md/lg breakpoints
-     - No emoji as functional icons
-   - Self-validate: scan for hardcoded colors, missing cursor-pointer, missing focus styles
-   - Auto-fix where possible
-   - Output to src/ directory (codebase files) + implementation summary
-```
-
-### For QA Role
-
-```
-3. **Execute**:
-   - Load design intelligence and design tokens for compliance checks
-   - Collect files to review based on review_type:
-     - architecture-review: <session>/artifacts/architecture/**/*
-     - code-review: src/**/*.{tsx,jsx,vue,svelte,html,css}
-     - final: src/**/*.{tsx,jsx,vue,svelte,html,css}
-   - Execute 5-dimension audit:
-     - Dim 1 Code Quality (0.20): file length, console.log, empty catch, unused imports
-     - Dim 2 Accessibility (0.25): alt text, labels, headings, focus styles, ARIA
-     - Dim 3 Design Compliance (0.20): hardcoded colors, spacing, anti-patterns
-     - Dim 4 UX Best Practices (0.20): cursor-pointer, transitions, responsive, states
-     - Dim 5 Pre-Delivery (0.15): final checklist (code-review/final types only)
-   - Calculate weighted score: sum(dimension_score * weight)
-   - Determine verdict: score >= 8 AND critical == 0 -> PASSED; score >= 6 AND critical == 0 -> PASSED_WITH_WARNINGS; else -> FIX_REQUIRED
-   - Write audit report to <session-folder>/artifacts/qa/
-   - Set qa_score and qa_verdict in output
-```
-
----
-
-## 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 |
-| QA fields | qa_score and qa_verdict set for QA role tasks |
-
----
-
-## 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 |
-| `{scope}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{review_type}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{prev_context}` | spawn_agents_on_csv | Runtime from CSV row |

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

@@ -1,188 +0,0 @@
-# Team Frontend -- CSV Schema
-
-## Master CSV: tasks.csv
-
-### Column Definitions
-
-#### Input Columns (Set by Decomposer)
-
-| Column | Type | Required | Description | Example |
-|--------|------|----------|-------------|---------|
-| `id` | string | Yes | Unique task identifier (PREFIX-NNN) | `"ANALYZE-001"` |
-| `title` | string | Yes | Short task title | `"Requirement analysis + design intelligence"` |
-| `description` | string | Yes | Detailed task description (self-contained) with PURPOSE/TASK/CONTEXT/EXPECTED/CONSTRAINTS | `"PURPOSE: Analyze frontend requirements..."` |
-| `role` | enum | Yes | Worker role: `analyst`, `architect`, `developer`, `qa` | `"analyst"` |
-| `pipeline_mode` | enum | Yes | Pipeline mode: `page`, `feature`, `system` | `"feature"` |
-| `scope` | enum | Yes | Task scope: `full`, `tokens`, `components` | `"full"` |
-| `review_type` | string | No | QA review type: `architecture-review`, `code-review`, `final` (empty for non-QA tasks) | `"code-review"` |
-| `deps` | string | No | Semicolon-separated dependency task IDs | `"ANALYZE-001"` |
-| `context_from` | string | No | Semicolon-separated task IDs for context | `"ANALYZE-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) | `"[ANALYZE-001] Detected React + shadcn stack..."` |
-
-#### Output Columns (Set by Agent)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `status` | enum | `pending` -> `completed` / `failed` / `skipped` | `"completed"` |
-| `findings` | string | Key discoveries (max 500 chars) | `"Generated 24 color tokens with dark mode..."` |
-| `artifacts_produced` | string | Semicolon-separated paths of produced artifacts | `"artifacts/analysis/design-intelligence.json;artifacts/analysis/requirements.md"` |
-| `qa_score` | string | QA weighted score 0-10 (empty for non-QA tasks) | `"8.5"` |
-| `qa_verdict` | enum | `PASSED`, `PASSED_WITH_WARNINGS`, `FIX_REQUIRED` (empty for non-QA) | `"PASSED"` |
-| `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.
-
----
-
-### Role Prefixes
-
-| Role | Prefix | Responsibility Type |
-|------|--------|---------------------|
-| analyst | ANALYZE | read-only (analysis + design intelligence retrieval) |
-| architect | ARCH | orchestration (design token + component spec generation) |
-| developer | DEV | code-gen (implementation from specs) |
-| qa | QA | validation (5-dimension quality audit) |
-
----
-
-### Example Data
-
-```csv
-id,title,description,role,pipeline_mode,scope,review_type,deps,context_from,exec_mode,wave,status,findings,artifacts_produced,qa_score,qa_verdict,error
-"ANALYZE-001","Requirement analysis","PURPOSE: Analyze frontend requirements and retrieve design intelligence via ui-ux-pro-max | Success: design-intelligence.json produced with industry-specific recommendations\nTASK:\n- Detect tech stack and existing design system\n- Retrieve design intelligence\n- Compile design-intelligence.json and requirements.md\nCONTEXT:\n- Session: .workflow/.csv-wave/fe-saas-dashboard-20260308\n- Industry: saas\nEXPECTED: artifacts/analysis/design-intelligence.json + requirements.md","analyst","feature","full","","","","csv-wave","1","pending","","","","",""
-"ARCH-001","Design token system + architecture","PURPOSE: Define design token system and component architecture | Success: design-tokens.json + component specs\nTASK:\n- Load design intelligence from analyst\n- Generate design tokens (colors, typography, spacing, shadows)\n- Define component specs\n- Generate project structure\nCONTEXT:\n- Session: .workflow/.csv-wave/fe-saas-dashboard-20260308\n- Upstream: design-intelligence.json\nEXPECTED: artifacts/architecture/design-tokens.json + component-specs/ + project-structure.md","architect","feature","full","","ANALYZE-001","ANALYZE-001","csv-wave","2","pending","","","","",""
-"QA-001","Architecture review","PURPOSE: Review architecture before development | Success: Architecture approved with score >= 8\nTASK:\n- Load design intelligence and tokens\n- Execute 5-dimension audit on architecture\n- Calculate score and verdict\nCONTEXT:\n- Session: .workflow/.csv-wave/fe-saas-dashboard-20260308\n- Review type: architecture-review\nEXPECTED: artifacts/qa/audit-001.md","qa","feature","full","architecture-review","ARCH-001","ARCH-001","csv-wave","3","pending","","","","",""
-"DEV-001","Frontend implementation","PURPOSE: Implement frontend from architecture artifacts | Success: All planned files implemented\nTASK:\n- Generate CSS custom properties from design tokens\n- Implement components following specs\n- Self-validate: no hardcoded colors, cursor-pointer, focus styles\nCONTEXT:\n- Session: .workflow/.csv-wave/fe-saas-dashboard-20260308\n- Upstream: design-tokens.json, component-specs/\nEXPECTED: src/styles/tokens.css + component files","developer","feature","full","","QA-001","QA-001;ARCH-001","csv-wave","4","pending","","","","",""
-"QA-002","Code review","PURPOSE: Execute 5-dimension quality audit | Success: Score >= 8 with 0 critical issues\nTASK:\n- Execute full audit (code quality, accessibility, design compliance, UX, pre-delivery)\n- Calculate weighted score\nCONTEXT:\n- Session: .workflow/.csv-wave/fe-saas-dashboard-20260308\n- Review type: code-review\nEXPECTED: artifacts/qa/audit-002.md","qa","feature","full","code-review","DEV-001","DEV-001","csv-wave","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)
-pipeline_mode --------->  pipeline_mode --------->  (reads)
-scope       ---------->  scope       ---------->  (reads)
-review_type ---------->  review_type ---------->  (reads)
-deps        ---------->  deps        ---------->  (reads)
-context_from---------->  context_from---------->  (reads)
-exec_mode   ---------->  exec_mode   ---------->  (reads)
-                         wave         ---------->  (reads)
-                         prev_context ---------->  (reads)
-                                                   status
-                                                   findings
-                                                   artifacts_produced
-                                                   qa_score
-                                                   qa_verdict
-                                                   error
-```
-
----
-
-## Output Schema (JSON)
-
-Agent output via `report_agent_job_result` (csv-wave tasks):
-
-```json
-{
-  "id": "ARCH-001",
-  "status": "completed",
-  "findings": "Generated design token system with 24 color tokens (light+dark), 7 typography scales, 6 spacing values. Created 3 component specs: Button, Card, Header. Project structure follows Next.js app router convention.",
-  "artifacts_produced": "artifacts/architecture/design-tokens.json;artifacts/architecture/component-specs/button.md;artifacts/architecture/project-structure.md",
-  "qa_score": "",
-  "qa_verdict": "",
-  "error": ""
-}
-```
-
-QA agent output example:
-
-```json
-{
-  "id": "QA-001",
-  "status": "completed",
-  "findings": "Architecture review: 8.2/10. Color tokens complete, typography scale follows best practices. Minor: missing border-radius for 'pill' variant.",
-  "artifacts_produced": "artifacts/qa/audit-001.md",
-  "qa_score": "8.2",
-  "qa_verdict": "PASSED",
-  "error": ""
-}
-```
-
-Interactive tasks output via structured text or JSON written to `interactive/{id}-result.json`.
-
----
-
-## Discovery Types
-
-| Type | Dedup Key | Data Schema | Description |
-|------|-----------|-------------|-------------|
-| `tech_stack_detected` | `data.stack` | `{stack, framework, ui_lib}` | Tech stack identified |
-| `design_pattern_found` | `data.pattern_name+data.location` | `{pattern_name, location, description}` | Existing design pattern |
-| `token_generated` | `data.category` | `{category, count, supports_dark_mode}` | Design token category created |
-| `file_modified` | `data.file` | `{file, change, lines_added}` | File change recorded |
-| `issue_found` | `data.file+data.line` | `{file, line, severity, description}` | QA issue discovered |
-| `anti_pattern_violation` | `data.pattern+data.file` | `{pattern, file, line, description}` | Industry anti-pattern detected |
-| `artifact_produced` | `data.path` | `{name, path, producer, type}` | Deliverable created |
-
-### Discovery NDJSON Format
-
-```jsonl
-{"ts":"2026-03-08T10:00:00Z","worker":"ANALYZE-001","type":"tech_stack_detected","data":{"stack":"react","framework":"nextjs","ui_lib":"shadcn"}}
-{"ts":"2026-03-08T10:05:00Z","worker":"ARCH-001","type":"token_generated","data":{"category":"color","count":24,"supports_dark_mode":true}}
-{"ts":"2026-03-08T10:10:00Z","worker":"DEV-001","type":"file_modified","data":{"file":"src/styles/tokens.css","change":"Generated CSS custom properties from design tokens","lines_added":85}}
-{"ts":"2026-03-08T10:15:00Z","worker":"QA-001","type":"issue_found","data":{"file":"src/components/Button.tsx","line":42,"severity":"high","description":"Missing cursor-pointer on interactive button element"}}
-```
-
-> 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}" |
-| Role valid | role in {analyst, architect, developer, qa} | "Invalid role: {role}" |
-| Pipeline mode valid | pipeline_mode in {page, feature, system} | "Invalid pipeline_mode: {mode}" |
-| QA verdict valid | qa_verdict in {PASSED, PASSED_WITH_WARNINGS, FIX_REQUIRED, ""} | "Invalid qa_verdict: {verdict}" |
-| Cross-mechanism deps | Interactive to CSV deps resolve correctly | "Cross-mechanism dependency unresolvable: {id}" |

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

@@ -1,142 +0,0 @@
-# Completion Handler Agent
-
-Interactive agent for handling pipeline completion action. Presents debug summary and offers Archive/Keep/Export choices.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `agents/completion-handler.md`
-- **Responsibility**: Present debug pipeline results, handle completion choice, execute cleanup or export
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Read all task results from master CSV
-- Present debug summary (reproduction, RCA, fix, verification)
-- Wait for user choice before acting
-- Produce structured output following template
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Delete session files without user approval
-- Modify task artifacts
-- Produce unstructured output
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | built-in | Load task results and artifacts |
-| `request_user_input` | built-in | Get user completion choice |
-| `Write` | built-in | Store completion result |
-| `Bash` | built-in | Execute archive/export operations |
-
----
-
-## Execution
-
-### Phase 1: Results Loading
-
-**Objective**: Load all task results and build debug summary
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| tasks.csv | Yes | Master state with all task results |
-| Artifact files | No | Verify deliverables exist |
-
-**Steps**:
-
-1. Read master tasks.csv
-2. Parse all completed tasks and their artifacts
-3. Build debug summary:
-   - Bug description and reproduction results
-   - Root cause analysis findings
-   - Files modified and patches applied
-   - Verification results (pass/fail)
-   - Evidence inventory (screenshots, logs, traces)
-4. Calculate pipeline statistics
-
-**Output**: Debug summary ready for user
-
----
-
-### Phase 2: Completion Choice
-
-**Objective**: Present debug results and get user action
-
-**Steps**:
-
-1. Display pipeline summary with debug details
-2. Present completion choice:
-
-```javascript
-request_user_input({
-  questions: [{
-    question: "Debug pipeline complete. What would you like to do?",
-    header: "Completion",
-    id: "completion_action",
-    options: [
-      { label: "Archive & Clean (Recommended)", description: "Archive session, output final summary" },
-      { label: "Keep Active", description: "Keep session for follow-up debugging" },
-      { label: "Export Results", description: "Export debug report and patches" }
-    ]
-  }]
-})
-```
-
-3. Handle response:
-
-| Response | Action |
-|----------|--------|
-| Archive & Clean | Mark session completed, output final summary |
-| Keep Active | Mark session paused, keep all evidence/artifacts |
-| Export Results | Copy RCA report, fix changes, verification report to project directory |
-
-**Output**: Completion action result
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Pipeline mode: <test-pipeline|debug-pipeline>
-- Tasks completed: <count>/<total>
-- Fix rounds: <count>/<max>
-- Final verdict: <pass|pass_with_warnings|fail>
-
-## Debug Summary
-- Bug: <description>
-- Root cause: <category at file:line>
-- Fix: <description of changes>
-- Verification: <pass/fail>
-
-## Evidence Inventory
-- Screenshots: <count>
-- Console logs: <captured/not captured>
-- Network logs: <captured/not captured>
-- Performance trace: <captured/not captured>
-
-## Action Taken
-- Choice: <archive|keep|export>
-- Session status: <completed|paused|exported>
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| tasks.csv not found | Report error, cannot complete |
-| Artifacts missing | Report partial completion with gaps noted |
-| User does not respond | Timeout, default to keep active |