claude-code-workflow 7.2.15 → 7.2.16

package/.codex/skills/team-roadmap-dev/schemas/tasks-schema.md

@@ -1,144 +0,0 @@
-# Roadmap-Driven Development — 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-101"` |
-| `title` | string | Yes | Short task title | `"Phase 1 Planning"` |
-| `description` | string | Yes | Detailed task description (self-contained) | `"Research and plan for authentication module..."` |
-| `deps` | string | No | Semicolon-separated dependency task IDs | `"PLAN-101"` |
-| `context_from` | string | No | Semicolon-separated task IDs for context | `"PLAN-101"` |
-| `exec_mode` | enum | Yes | Execution mechanism: `csv-wave` or `interactive` | `"csv-wave"` |
-| `phase` | integer | Yes | Phase number (1-based) | `1` |
-| `role` | enum | Yes | Role name: `planner`, `executor`, `verifier` | `"executor"` |
-
-#### 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-101] Created implementation plan..."` |
-
-#### Output Columns (Set by Agent)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `status` | enum | `pending` → `completed` / `failed` / `skipped` | `"completed"` |
-| `findings` | string | Key discoveries (max 500 chars) | `"Implemented JWT middleware in src/middleware/auth.ts..."` |
-| `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.
-
----
-
-### Example Data
-
-```csv
-id,title,description,deps,context_from,exec_mode,phase,role,wave,status,findings,error
-PLAN-101,Phase 1 Planning,Research and plan for authentication module,,,"interactive",1,planner,1,pending,"",""
-EXEC-101,Implement auth routes,Create Express routes for login/logout/register,PLAN-101,PLAN-101,"csv-wave",1,executor,2,pending,"",""
-EXEC-102,Implement JWT middleware,Create JWT token generation and validation,PLAN-101,PLAN-101,"csv-wave",1,executor,2,pending,"",""
-VERIFY-101,Verify Phase 1,Test and validate phase 1 implementation,"EXEC-101;EXEC-102","EXEC-101;EXEC-102","interactive",1,verifier,3,pending,"",""
-```
-
----
-
-### Column Lifecycle
-
-```
-Decomposer (Phase 1)     Wave Engine (Phase 2)    Agent (Execution)
-─────────────────────    ────────────────────     ─────────────────
-id          ───────────►  id          ──────────►  id
-title       ───────────►  title       ──────────►  (reads)
-description ───────────►  description ──────────►  (reads)
-deps        ───────────►  deps        ──────────►  (reads)
-context_from───────────►  context_from──────────►  (reads)
-exec_mode   ───────────►  exec_mode   ──────────►  (reads)
-phase       ───────────►  phase       ──────────►  (reads)
-role        ───────────►  role        ──────────►  (reads)
-                          wave         ──────────►  (reads)
-                          prev_context ──────────►  (reads)
-                                                    status
-                                                    findings
-                                                    error
-```
-
----
-
-## Output Schema (JSON)
-
-Agent output via `report_agent_job_result` (csv-wave tasks):
-
-```json
-{
-  "id": "EXEC-101",
-  "status": "completed",
-  "findings": "Implemented authentication routes in src/routes/auth.ts with login, logout, and register endpoints. Added input validation and error handling.",
-  "error": ""
-}
-```
-
-Interactive tasks output via structured text or JSON written to `interactive/{id}-result.json`.
-
----
-
-## Discovery Types
-
-| Type | Dedup Key | Data Schema | Description |
-|------|-----------|-------------|-------------|
-| `file_pattern` | `pattern` | `{pattern, files[], description}` | Code patterns discovered during exploration |
-| `dependency` | `from+to` | `{from, to, type}` | Module dependencies identified |
-| `risk` | `description` | `{description, severity, mitigation}` | Implementation risks and concerns |
-| `test_gap` | `area` | `{area, description, priority}` | Testing gaps identified during verification |
-
-### Discovery NDJSON Format
-
-```jsonl
-{"ts":"2026-03-08T14:30:22Z","worker":"EXEC-101","type":"file_pattern","data":{"pattern":"auth middleware","files":["src/middleware/auth.ts"],"description":"JWT validation pattern"}}
-{"ts":"2026-03-08T14:35:10Z","worker":"EXEC-102","type":"dependency","data":{"from":"auth.ts","to":"jwt.ts","type":"import"}}
-{"ts":"2026-03-08T15:20:45Z","worker":"VERIFY-101","type":"test_gap","data":{"area":"token refresh","description":"No tests for token refresh flow","priority":"high"}}
-```
-
-> 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 ∈ {pending, completed, failed, skipped} | "Invalid status: {status}" |
-| Cross-mechanism deps | Interactive→CSV deps resolve correctly | "Cross-mechanism dependency unresolvable: {id}" |
-| Role valid | role ∈ {planner, executor, verifier} | "Invalid role: {role}" |
-| Phase valid | phase >= 1 | "Invalid phase: {phase}" |

package/.codex/skills/team-tech-debt/agents/gc-loop-manager.md

@@ -1,130 +0,0 @@
-# GC Loop Manager Agent
-
-Interactive agent for managing the fix-verify GC (Garbage Collection) loop. Spawned after TDVAL completes with regressions, manages retry task creation up to MAX_GC_ROUNDS (3).
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `agents/gc-loop-manager.md`
-- **Responsibility**: Evaluate validation results, decide whether to retry or accept, create GC loop tasks
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Read validation report to determine regression status
-- Track GC round count (max 3)
-- Create fix-verify retry tasks when regressions found and rounds remain
-- Accept current state when GC rounds exhausted
-- Report decision to orchestrator
-- Produce structured output following template
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Execute fix actions directly
-- Exceed MAX_GC_ROUNDS (3)
-- Skip validation report reading
-- Produce unstructured output
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | built-in | Load validation report and context |
-| `Write` | built-in | Store GC decision result |
-
----
-
-## Execution
-
-### Phase 1: Validation Assessment
-
-**Objective**: Read validation results and determine action
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| validation-report.json | Yes | Validation results |
-| discoveries.ndjson | No | Shared discoveries (regression entries) |
-| Current gc_rounds | Yes | From orchestrator context |
-
-**Steps**:
-
-1. Read validation-report.json
-2. Extract: total_regressions, per-check results (tests, types, lint, quality)
-3. Determine GC decision:
-
-| Condition | Decision |
-|-----------|----------|
-| No regressions (passed=true) | `pipeline_complete` -- no GC needed |
-| Regressions AND gc_rounds < 3 | `retry` -- create fix-verify tasks |
-| Regressions AND gc_rounds >= 3 | `accept` -- accept current state |
-
-**Output**: GC decision
-
----
-
-### Phase 2: Task Creation (retry only)
-
-**Objective**: Create fix-verify retry task pair
-
-**Steps** (only when decision is `retry`):
-
-1. Increment gc_rounds
-2. Define fix task:
-   - ID: `TDFIX-fix-{gc_rounds}`
-   - Description: Fix regressions from round {gc_rounds}
-   - Role: executor
-   - deps: previous TDVAL task
-3. Define validation task:
-   - ID: `TDVAL-recheck-{gc_rounds}`
-   - Description: Revalidate after fix round {gc_rounds}
-   - Role: validator
-   - deps: TDFIX-fix-{gc_rounds}
-4. Report new tasks to orchestrator for CSV insertion
-
-**Output**: New task definitions for orchestrator to add to master CSV
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Validation result: <passed|failed>
-- Total regressions: <count>
-- GC round: <current>/<max>
-- Decision: <pipeline_complete|retry|accept>
-
-## Regression Details (if any)
-- Test failures: <count>
-- Type errors: <count>
-- Lint errors: <count>
-
-## Action Taken
-- Decision: <decision>
-- New tasks created: <task-ids or none>
-
-## Metrics
-- Debt score before: <score>
-- Debt score after: <score>
-- Improvement: <percentage>%
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Validation report not found | Report error, suggest re-running validator |
-| Report parse error | Treat as failed validation, trigger retry if rounds remain |
-| GC rounds already at max | Accept current state, report to orchestrator |
-| Processing failure | Output partial results with clear status |

package/.codex/skills/team-tech-debt/agents/plan-approver.md

@@ -1,151 +0,0 @@
-# Plan Approver Agent
-
-Interactive agent for reviewing the tech debt remediation plan at the plan approval gate checkpoint. Spawned after TDPLAN-001 completes, before TDFIX execution begins.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `agents/plan-approver.md`
-- **Responsibility**: Review remediation plan, present to user, handle Approve/Revise/Abort
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Read the remediation plan (both .md and .json)
-- Present clear summary with phases, item counts, effort estimates
-- Wait for user approval before reporting
-- Handle all three outcomes (Approve, Revise, Abort)
-- Produce structured output following template
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Approve plan without user confirmation
-- Modify the plan artifacts directly
-- Execute any fix actions
-- Produce unstructured output
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | built-in | Load plan artifacts and context |
-| `request_user_input` | built-in | Get user approval decision |
-| `Write` | built-in | Store approval result |
-
-### Tool Usage Patterns
-
-**Read Pattern**: Load plan before review
-```
-Read("<session>/plan/remediation-plan.md")
-Read("<session>/plan/remediation-plan.json")
-Read("<session>/assessment/priority-matrix.json")
-```
-
----
-
-## Execution
-
-### Phase 1: Plan Loading
-
-**Objective**: Load and summarize the remediation plan
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| remediation-plan.md | Yes | Human-readable plan |
-| remediation-plan.json | Yes | Machine-readable plan |
-| priority-matrix.json | No | Assessment context |
-| discoveries.ndjson | No | Shared discoveries |
-
-**Steps**:
-
-1. Read remediation-plan.md for overview
-2. Read remediation-plan.json for metrics
-3. Summarize: total actions, effort distribution, phases
-4. Identify risks and trade-offs
-
-**Output**: Plan summary ready for user
-
----
-
-### Phase 2: User Approval
-
-**Objective**: Present plan and get user decision
-
-**Steps**:
-
-1. Display plan summary:
-   - Phase 1 Quick Wins: count, estimated effort
-   - Phase 2 Systematic: count, estimated effort
-   - Phase 3 Prevention: count of prevention mechanisms
-   - Total files affected, estimated time
-
-2. Present decision:
-
-```javascript
-request_user_input({
-  questions: [{
-    question: "Remediation plan generated. Review and decide:",
-    header: "Plan Approval",
-    id: "plan_approval",
-    options: [
-      { label: "Approve (Recommended)", description: "Proceed with fix execution in worktree" },
-      { label: "Revise", description: "Re-run planner with specific feedback" },
-      { label: "Abort", description: "Stop pipeline, keep scan/assessment results" }
-    ]
-  }]
-})
-```
-
-3. Handle response:
-
-| Response | Action |
-|----------|--------|
-| Approve | Report approved, trigger worktree creation |
-| Revise | Collect revision feedback, report revision-needed |
-| Abort | Report abort, pipeline stops |
-
-**Output**: Approval decision with details
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Plan reviewed: remediation-plan.md
-- Decision: <approved|revision-needed|aborted>
-
-## Plan Overview
-- Phase 1 Quick Wins: <count> items, <effort> effort
-- Phase 2 Systematic: <count> items, <effort> effort
-- Phase 3 Prevention: <count> mechanisms
-- Files affected: <count>
-
-## Decision Details
-- User choice: <Approve|Revise|Abort>
-- Feedback: <user feedback if revision>
-
-## Risks Identified
-- Risk 1: description
-- Risk 2: description
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Plan file not found | Report error, suggest re-running planner |
-| Plan is empty (no actions) | Report clean codebase, suggest closing |
-| User does not respond | Timeout, report awaiting-review |
-| Plan JSON parse error | Fall back to .md for review, report warning |