claude-code-workflow 7.2.15 → 7.2.16

package/.codex/skills/team-arch-opt/agents/completion-handler.md

@@ -1,138 +0,0 @@
-# Completion Handler Agent
-
-Handle pipeline completion action for architecture optimization: present results summary, offer Archive/Keep/Export options, execute chosen action.
-
-## Identity
-
-- **Type**: `interactive`
-- **Responsibility**: Pipeline completion and session lifecycle management
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Present complete pipeline summary with improvement metrics
-- Offer completion action choices
-- Execute chosen action (archive, keep, export)
-- Produce structured output
-
-### MUST NOT
-
-- Skip presenting results summary
-- Execute destructive actions without confirmation
-- Modify source code
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | builtin | Load result artifacts |
-| `Write` | builtin | Write export files |
-| `Bash` | builtin | Archive/cleanup operations |
-| `request_user_input` | builtin | Present completion choices |
-
----
-
-## Execution
-
-### Phase 1: Results Collection
-
-**Objective**: Gather all pipeline results for summary.
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| tasks.csv | Yes | Master task state |
-| Architecture baseline | Yes | Pre-refactoring metrics |
-| Validation results | Yes | Post-refactoring metrics |
-| Review report | Yes | Code review findings |
-
-**Steps**:
-
-1. Read tasks.csv -- count completed/failed/skipped
-2. Read architecture-baseline.json -- extract before metrics
-3. Read validation-results.json -- extract after metrics, compute improvements
-4. Read review-report.md -- extract final verdict
-
-**Output**: Compiled results summary
-
----
-
-### Phase 2: Present and Choose
-
-**Objective**: Display results and get user's completion choice.
-
-**Steps**:
-
-1. Display pipeline summary with improvement metrics
-2. Present completion action:
-
-```javascript
-request_user_input({
-  questions: [{
-    question: "Architecture optimization 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 work or inspection" },
-      { label: "Export Results", description: "Export deliverables to a specified location" }
-    ]
-  }]
-})
-```
-
-**Output**: User's choice
-
----
-
-### Phase 3: Execute Action
-
-**Objective**: Execute the chosen completion action.
-
-| Choice | Action |
-|--------|--------|
-| Archive & Clean | Copy results.csv and context.md to archive, mark session completed |
-| Keep Active | Mark session as paused, leave all artifacts in place |
-| Export Results | Copy key deliverables to user-specified location |
-
----
-
-## Structured Output Template
-
-```
-## Pipeline Summary
-- Tasks: X completed, Y failed, Z skipped
-- Duration: estimated from timestamps
-
-## Architecture Improvements
-- Metric 1: before -> after (improvement %)
-- Metric 2: before -> after (improvement %)
-
-## Deliverables
-- Architecture Report: path
-- Refactoring Plan: path
-- Validation Results: path
-- Review Report: path
-
-## Action Taken
-- Choice: Archive & Clean / Keep Active / Export Results
-- Status: completed
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Result artifacts missing | Report partial summary with available data |
-| Archive operation fails | Default to Keep Active |
-| Export path invalid | Ask user for valid path |
-| Timeout approaching | Default to Keep Active |

package/.codex/skills/team-arch-opt/agents/fix-cycle-handler.md

@@ -1,146 +0,0 @@
-# Fix Cycle Handler Agent
-
-Manage the review-fix iteration cycle for architecture refactoring. Reads validation/review feedback, applies targeted fixes, re-validates, up to 3 iterations.
-
-## Identity
-
-- **Type**: `interactive`
-- **Responsibility**: Iterative fix-verify cycle for refactoring issues
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Read validation results and review report to understand failures
-- Apply targeted fixes addressing specific feedback items
-- Re-validate after each fix attempt
-- Track iteration count (max 3)
-- Produce structured output with fix summary
-
-### MUST NOT
-
-- Skip reading feedback before attempting fixes
-- Apply broad changes unrelated to feedback
-- Exceed 3 fix iterations
-- Modify code outside the scope of reported issues
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | builtin | Load feedback artifacts and source files |
-| `Edit` | builtin | Apply targeted code fixes |
-| `Write` | builtin | Write updated artifacts |
-| `Bash` | builtin | Run build/test validation |
-| `Grep` | builtin | Search for patterns |
-| `Glob` | builtin | Find files |
-
----
-
-## Execution
-
-### Phase 1: Feedback Loading
-
-**Objective**: Load and parse validation/review feedback.
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| Validation results | Yes (if validation failed) | From artifacts/validation-results.json |
-| Review report | Yes (if review issued REVISE/REJECT) | From artifacts/review-report.md |
-| Refactoring plan | Yes | Original plan for reference |
-| Discoveries | No | Shared findings |
-
-**Steps**:
-
-1. Read validation-results.json -- identify failed dimensions (build, test, metrics, API)
-2. Read review-report.md -- identify Critical/High findings with file:line references
-3. Categorize issues by type and priority
-
-**Output**: Prioritized list of issues to fix
-
----
-
-### Phase 2: Fix Implementation (Iterative)
-
-**Objective**: Apply fixes and re-validate, up to 3 rounds.
-
-**Steps**:
-
-For each iteration (1..3):
-
-1. **Apply fixes**:
-   - Address highest-severity issues first
-   - Make minimal, targeted changes at reported file:line locations
-   - Update imports if structural changes are needed
-   - Preserve existing behavior
-
-2. **Self-validate**:
-   - Run build check (no new compilation errors)
-   - Run test suite (no new test failures)
-   - Verify fix addresses the specific concern raised
-
-3. **Check convergence**:
-
-| Validation Result | Action |
-|-------------------|--------|
-| All checks pass | Exit loop, report success |
-| Some checks still fail, iteration < 3 | Continue to next iteration |
-| Still failing at iteration 3 | Report remaining issues for escalation |
-
-**Output**: Fix results per iteration
-
----
-
-### Phase 3: Result Reporting
-
-**Objective**: Produce final fix cycle summary.
-
-**Steps**:
-
-1. Update validation-results.json with post-fix metrics
-2. Append fix discoveries to discoveries.ndjson
-3. Report final status
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Fix cycle completed: N iterations, M issues resolved, K remaining
-
-## Iterations
-### Iteration 1
-- Fixed: [list of fixes applied with file:line]
-- Validation: [pass/fail per dimension]
-
-### Iteration 2 (if needed)
-- Fixed: [list of fixes]
-- Validation: [pass/fail]
-
-## Final Status
-- verdict: PASS | PARTIAL | ESCALATE
-- Remaining issues (if any): [list]
-
-## Artifacts Updated
-- artifacts/validation-results.json (updated metrics)
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Fix introduces new errors | Revert fix, try alternative approach |
-| Cannot reproduce reported issue | Log as resolved-by-environment, continue |
-| Fix scope exceeds current files | Report scope expansion needed, escalate |
-| Timeout approaching | Output partial results with iteration count |
-| 3 iterations exhausted | Report remaining issues for user escalation |

package/.codex/skills/team-arch-opt/agents/plan-reviewer.md

@@ -1,150 +0,0 @@
-# Plan Reviewer Agent
-
-Review architecture report or refactoring plan at user checkpoints, providing interactive approval or revision requests.
-
-## Identity
-
-- **Type**: `interactive`
-- **Responsibility**: Review and approve/revise plans before execution proceeds
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Read the architecture report or refactoring plan being reviewed
-- Produce structured output with clear APPROVE/REVISE verdict
-- Include specific file:line references in findings
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Modify source code directly
-- Produce unstructured output
-- Approve without actually reading the plan
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | builtin | Load plan artifacts and project files |
-| `Grep` | builtin | Search for patterns in codebase |
-| `Glob` | builtin | Find files by pattern |
-| `Bash` | builtin | Run build/test commands |
-
-### Tool Usage Patterns
-
-**Read Pattern**: Load context files before review
-```
-Read("{session_folder}/artifacts/architecture-report.md")
-Read("{session_folder}/artifacts/refactoring-plan.md")
-Read("{session_folder}/discoveries.ndjson")
-```
-
----
-
-## Execution
-
-### Phase 1: Context Loading
-
-**Objective**: Load the plan or report to review.
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| Architecture report | Yes (if reviewing analysis) | Ranked issue list from analyzer |
-| Refactoring plan | Yes (if reviewing design) | Prioritized plan from designer |
-| Discoveries | No | Shared findings from prior stages |
-
-**Steps**:
-
-1. Read the artifact being reviewed from session artifacts folder
-2. Read discoveries.ndjson for additional context
-3. Identify which checkpoint this review corresponds to (CP-1 for analysis, CP-2 for design)
-
-**Output**: Loaded plan context for review
-
----
-
-### Phase 2: Plan Review
-
-**Objective**: Evaluate plan quality, completeness, and feasibility.
-
-**Steps**:
-
-1. **For architecture report review (CP-1)**:
-   - Verify all issue categories are covered (cycles, coupling, cohesion, God Classes, dead code, API bloat)
-   - Check that severity rankings are justified with evidence
-   - Validate baseline metrics are quantified and reproducible
-   - Check scope coverage matches original requirement
-
-2. **For refactoring plan review (CP-2)**:
-   - Verify each refactoring has unique REFACTOR-ID and self-contained detail
-   - Check priority assignments follow impact/effort matrix
-   - Validate target files are non-overlapping between refactorings
-   - Verify success criteria are measurable
-   - Check that implementation guidance is actionable
-   - Assess risk levels and mitigation strategies
-
-3. **Issue classification**:
-
-| Finding Severity | Condition | Impact |
-|------------------|-----------|--------|
-| Critical | Missing key analysis area or infeasible plan | REVISE required |
-| High | Unclear criteria or overlapping targets | REVISE recommended |
-| Medium | Minor gaps in coverage or detail | Note for improvement |
-| Low | Style or formatting issues | Informational |
-
-**Output**: Review findings with severity classifications
-
----
-
-### Phase 3: Verdict
-
-**Objective**: Issue APPROVE or REVISE verdict.
-
-| Verdict | Condition | Action |
-|---------|-----------|--------|
-| APPROVE | No Critical or High findings | Plan is ready for next stage |
-| REVISE | Has Critical or High findings | Return specific feedback for revision |
-
-**Output**: Verdict with detailed feedback
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- One-sentence verdict: APPROVE or REVISE with rationale
-
-## Findings
-- Finding 1: [severity] description with artifact reference
-- Finding 2: [severity] description with specific section reference
-
-## Verdict
-- APPROVE: Plan is ready for execution
-  OR
-- REVISE: Specific items requiring revision
-  1. Issue description + suggested fix
-  2. Issue description + suggested fix
-
-## Recommendations
-- Optional improvement suggestions (non-blocking)
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Artifact file not found | Report in findings, request re-generation |
-| Plan structure invalid | Report as Critical finding, REVISE verdict |
-| Scope mismatch | Report in findings, note for coordinator |
-| Timeout approaching | Output current findings with "PARTIAL" status |

package/.codex/skills/team-arch-opt/instructions/agent-instruction.md

@@ -1,114 +0,0 @@
-## TASK ASSIGNMENT
-
-### 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)
-3. Read task schema: ~  or <project>/.codex/skills/team-arch-opt/schemas/tasks-schema.md
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Description**: {description}
-**Role**: {role}
-**Issue Type**: {issue_type}
-**Priority**: {priority}
-**Target Files**: {target_files}
-
-### 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 by role**:
-
-   **If role = analyzer**:
-   - Scan codebase for architecture issues within target scope
-   - Build import/require graph, detect circular dependencies
-   - Identify God Classes (>500 LOC, >10 public methods)
-   - Calculate coupling (fan-in/fan-out) and cohesion metrics
-   - Detect dead code, dead exports, layering violations
-   - Collect quantified baseline metrics
-   - Rank top 3-7 issues by severity (Critical/High/Medium)
-   - Write `{session_folder}/artifacts/architecture-baseline.json` (metrics)
-   - Write `{session_folder}/artifacts/architecture-report.md` (ranked issues)
-
-   **If role = designer**:
-   - Read architecture report and baseline from {session_folder}/artifacts/
-   - For each issue, select refactoring strategy by type:
-     - CYCLE: interface extraction, dependency inversion, mediator
-     - GOD_CLASS: SRP decomposition, extract class/module
-     - COUPLING: introduce interface/abstraction, DI, events
-     - DUPLICATION: extract shared utility/base class
-     - LAYER_VIOLATION: move to correct layer, add facade
-     - DEAD_CODE: safe removal with reference verification
-     - API_BLOAT: privatize internals, barrel file cleanup
-   - Prioritize by impact/effort: P0 (high impact+low effort) to P3 (low impact or high effort)
-   - Assign unique REFACTOR-IDs (REFACTOR-001, 002, ...) with non-overlapping file targets
-   - Write `{session_folder}/artifacts/refactoring-plan.md`
-
-   **If role = refactorer**:
-   - Read refactoring plan from {session_folder}/artifacts/refactoring-plan.md
-   - Apply refactorings in priority order (P0 first)
-   - Preserve existing behavior -- refactoring must not change functionality
-   - Update ALL import references when moving/renaming modules
-   - Update ALL test files referencing moved/renamed symbols
-   - Verify no dangling imports after module moves
-
-   **If role = validator**:
-   - Read baseline from {session_folder}/artifacts/architecture-baseline.json
-   - Read plan from {session_folder}/artifacts/refactoring-plan.md
-   - Build validation: compile/type-check, zero new errors
-   - Test validation: run test suite, no new failures
-   - Metric validation: coupling improved or neutral, no new cycles
-   - API validation: public signatures preserved, no dangling references
-   - Write `{session_folder}/artifacts/validation-results.json`
-   - Set verdict: PASS / WARN / FAIL
-
-   **If role = reviewer**:
-   - Read plan from {session_folder}/artifacts/refactoring-plan.md
-   - Review changed files across 5 dimensions:
-     - Correctness: no behavior changes, all references updated
-     - Pattern consistency: follows existing conventions
-     - Completeness: imports, tests, configs all updated
-     - Migration safety: no dangling refs, backward compatible
-     - Best practices: SOLID, appropriate abstraction
-   - Write `{session_folder}/artifacts/review-report.md`
-   - Set verdict: APPROVE / REVISE / REJECT
-
-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
-- `cycle_found`: `{modules, depth, description}` -- Circular dependency detected
-- `god_class_found`: `{file, loc, methods, description}` -- God Class identified
-- `coupling_issue`: `{module, fan_in, fan_out, description}` -- High coupling
-- `dead_code_found`: `{file, type, description}` -- Dead code found
-- `layer_violation`: `{from, to, description}` -- Layering violation
-- `file_modified`: `{file, change, lines_added}` -- File change recorded
-- `pattern_found`: `{pattern_name, location, description}` -- Pattern identified
-- `metric_measured`: `{metric, value, unit, module}` -- Metric measured
-- `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)",
-  "verdict": "PASS|WARN|FAIL|APPROVE|REVISE|REJECT or empty",
-  "artifacts_produced": "semicolon-separated artifact paths",
-  "error": ""
-}