claude-code-workflow 7.2.15 → 7.2.16

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

@@ -1,163 +0,0 @@
-# Agent Instruction Template -- Team Skill Designer
-
-Base instruction template for CSV wave agents. Each agent receives this template with its row's column values substituted at runtime via `spawn_agents_on_csv`.
-
-## Purpose
-
-| Phase | Usage |
-|-------|-------|
-| Phase 1 | Baked into instruction parameter with session folder path |
-| Phase 2 | Injected as `instruction` parameter to `spawn_agents_on_csv` |
-
----
-
-## Base Instruction Template
-
-```markdown
-## TASK ASSIGNMENT -- Team Skill Designer
-
-### 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 teamConfig: <session-folder>/teamConfig.json (REQUIRED -- contains complete skill configuration)
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Role**: {role}
-**File Target**: {file_target}
-**Generation Type**: {gen_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. **Read teamConfig**: Load <session-folder>/teamConfig.json for complete skill configuration (roles, pipelines, specs, templates)
-3. **Use context**: Apply previous tasks' findings from prev_context above
-4. **Execute by gen_type**:
-
-### For gen_type = directory
-   - Parse teamConfig to determine required directories
-   - Create directory structure at teamConfig.targetDir
-   - Create subdirectories: roles/, specs/, templates/ (if needed)
-   - Create per-role subdirectories: roles/<role-name>/ (+ commands/ if hasCommands)
-   - Verify all directories exist
-
-### For gen_type = router
-   - Read existing Codex team skill SKILL.md as reference pattern
-   - Generate SKILL.md with these sections in order:
-     1. YAML frontmatter (name, description, argument-hint, allowed-tools)
-     2. Auto Mode section
-     3. Title + Usage examples
-     4. Overview with workflow diagram
-     5. Task Classification Rules
-     6. CSV Schema (header + column definitions)
-     7. Agent Registry (if interactive agents exist)
-     8. Output Artifacts table
-     9. Session Structure diagram
-     10. Implementation (session init, phases 0-4)
-     11. Discovery Board Protocol
-     12. Error Handling table
-     13. Core Rules list
-   - Use teamConfig.roles for role registry
-   - Use teamConfig.pipelines for pipeline definitions
-
-### For gen_type = role-bundle
-   - Generate role.md with:
-     1. YAML frontmatter (role, prefix, inner_loop, message_types)
-     2. Identity section
-     3. Boundaries (MUST/MUST NOT)
-     4. Entry Router (for coordinator)
-     5. Phase references (Phase 0-5 for coordinator)
-   - Generate commands/*.md for each command in teamConfig.roles[].commands
-   - Each command file: Purpose, Constants, Phase 2-4 execution logic
-   - Coordinator always gets: analyze.md, dispatch.md, monitor.md
-
-### For gen_type = role-inline
-   - Generate single role.md with:
-     1. YAML frontmatter (role, prefix, inner_loop, message_types)
-     2. Identity section
-     3. Boundaries (MUST/MUST NOT)
-     4. Phase 2: Context Loading
-     5. Phase 3: Domain Execution (role-specific logic)
-     6. Phase 4: Output & Report
-
-### For gen_type = spec
-   - For pipelines.md: Generate from teamConfig.pipelines
-     - Pipeline name, task table (ID, Role, Name, Depends On, Checkpoint)
-     - Task metadata registry
-     - Conditional routing rules
-     - Dynamic specialist injection
-   - For other specs: Generate domain-appropriate content
-
-### For gen_type = template
-   - Check for reference templates in existing skills
-   - Generate domain-appropriate template structure
-   - Include placeholder sections and formatting guidelines
-
-5. **Share discoveries**: Append exploration findings to shared board:
-   ```bash
-   echo '{"ts":"<ISO8601>","worker":"{id}","type":"<type>","data":{...}}' >> <session-folder>/discoveries.ndjson
-   ```
-6. **Report result**: Return JSON via report_agent_job_result
-
-### Discovery Types to Share
-- `dir_created`: {path, description} -- Directory structure created
-- `file_generated`: {file, gen_type, sections} -- File generated with specific sections
-- `pattern_found`: {pattern_name, description} -- Design pattern identified
-- `config_decision`: {decision, rationale, impact} -- Configuration decision made
-- `reference_found`: {source, target, type} -- Cross-reference between generated files
-
----
-
-## Output (report_agent_job_result)
-
-Return JSON:
-{
-  "id": "{id}",
-  "status": "completed" | "failed",
-  "findings": "Key discoveries and generation notes (max 500 chars)",
-  "files_produced": "semicolon-separated paths of produced files relative to skill root",
-  "error": ""
-}
-```
-
----
-
-## Quality Requirements
-
-All agents must verify before reporting complete:
-
-| Requirement | Criteria |
-|-------------|----------|
-| Files produced | Verify all claimed files exist via Read |
-| teamConfig adherence | Generated content matches teamConfig specifications |
-| Pattern fidelity | Generated files follow existing Codex skill patterns |
-| Discovery sharing | At least 1 discovery shared to board |
-| Error reporting | Non-empty error field if status is failed |
-| YAML frontmatter | Role files must have valid frontmatter for agent parsing |
-
----
-
-## 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 |
-| `{file_target}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{gen_type}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{prev_context}` | spawn_agents_on_csv | Runtime from CSV row |

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

@@ -1,180 +0,0 @@
-# Team Skill Designer -- CSV Schema
-
-## Master CSV: tasks.csv
-
-### Column Definitions
-
-#### Input Columns (Set by Decomposer)
-
-| Column | Type | Required | Description | Example |
-|--------|------|----------|-------------|---------|
-| `id` | string | Yes | Unique task identifier | `"SCAFFOLD-001"` |
-| `title` | string | Yes | Short task title | `"Create directory structure"` |
-| `description` | string | Yes | Detailed generation instructions (self-contained) | `"Create roles/, specs/, templates/ directories..."` |
-| `role` | string | Yes | Generator role name | `"scaffolder"` |
-| `file_target` | string | Yes | Target file/directory path relative to skill root | `"roles/coordinator/role.md"` |
-| `gen_type` | enum | Yes | `directory`, `router`, `role-bundle`, `role-inline`, `spec`, `template`, `validation` | `"role-inline"` |
-| `deps` | string | No | Semicolon-separated dependency task IDs | `"SCAFFOLD-001;SPEC-001"` |
-| `context_from` | string | No | Semicolon-separated task IDs for context | `"SPEC-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) | `"[SCAFFOLD-001] Created directory structure at .codex/skills/..."` |
-
-#### Output Columns (Set by Agent)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `status` | enum | `pending` -> `completed` / `failed` / `skipped` | `"completed"` |
-| `findings` | string | Key discoveries (max 500 chars) | `"Generated coordinator with 3 commands: analyze, dispatch, monitor"` |
-| `files_produced` | string | Semicolon-separated paths of produced files | `"roles/coordinator/role.md;roles/coordinator/commands/analyze.md"` |
-| `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.
-
----
-
-### Generator Roles
-
-| Role | gen_type Values | Description |
-|------|-----------------|-------------|
-| `scaffolder` | `directory` | Creates directory structures |
-| `router-writer` | `router` | Generates SKILL.md orchestrator files |
-| `role-writer` | `role-bundle`, `role-inline` | Generates role.md files (+ optional commands/) |
-| `spec-writer` | `spec` | Generates specs/*.md files |
-| `template-writer` | `template` | Generates templates/*.md files |
-| `validator` | `validation` | Validates generated skill package |
-
----
-
-### gen_type Values
-
-| gen_type | Target | Description |
-|----------|--------|-------------|
-| `directory` | Directory path | Create directory structure with subdirectories |
-| `router` | SKILL.md | Generate main orchestrator SKILL.md with frontmatter, role registry, router |
-| `role-bundle` | Directory path | Generate role.md + commands/ folder with multiple command files |
-| `role-inline` | Single .md file | Generate single role.md with inline Phase 2-4 logic |
-| `spec` | Single .md file | Generate spec file (pipelines, quality-gates, etc.) |
-| `template` | Single .md file | Generate document template file |
-| `validation` | Report | Validate complete skill package structure and references |
-
----
-
-### Example Data
-
-```csv
-id,title,description,role,file_target,gen_type,deps,context_from,exec_mode,wave,status,findings,files_produced,error
-"SCAFFOLD-001","Create directory structure","Create complete directory structure for team-code-review skill:\n- ~  or <project>/.codex/skills/team-code-review/\n- roles/coordinator/ + commands/\n- roles/analyst/\n- roles/reviewer/\n- specs/\n- templates/","scaffolder","skill-dir","directory","","","csv-wave","1","pending","","",""
-"ROUTER-001","Generate SKILL.md","Generate ~  or <project>/.codex/skills/team-code-review/SKILL.md with:\n- Frontmatter (name, description, allowed-tools)\n- Architecture diagram\n- Role registry table\n- CSV schema reference\n- Session structure\n- Wave execution engine\nUse teamConfig.json for role list and pipeline definitions","router-writer","SKILL.md","router","SCAFFOLD-001","SCAFFOLD-001","csv-wave","2","pending","","",""
-"SPEC-001","Generate pipelines spec","Generate specs/pipelines.md with:\n- Pipeline definitions from teamConfig\n- Task registry with PREFIX-NNN format\n- Conditional routing rules\n- Dynamic specialist injection\nRoles: analyst(ANALYSIS-*), reviewer(REVIEW-*)","spec-writer","specs/pipelines.md","spec","SCAFFOLD-001","SCAFFOLD-001","csv-wave","2","pending","","",""
-"ROLE-001","Generate coordinator","Generate roles/coordinator/role.md with entry router and commands/analyze.md, commands/dispatch.md, commands/monitor.md. Coordinator orchestrates the analysis pipeline","role-writer","roles/coordinator/","role-bundle","SCAFFOLD-001;SPEC-001","SPEC-001","csv-wave","3","pending","","",""
-"ROLE-002","Generate analyst role","Generate roles/analyst/role.md with Phase 2 (context loading), Phase 3 (analysis execution), Phase 4 (output). Prefix: ANALYSIS, inner_loop: false","role-writer","roles/analyst/role.md","role-inline","SCAFFOLD-001;SPEC-001","SPEC-001","csv-wave","3","pending","","",""
-"ROLE-003","Generate reviewer role","Generate roles/reviewer/role.md with Phase 2 (load artifacts), Phase 3 (review execution), Phase 4 (report). Prefix: REVIEW, inner_loop: false","role-writer","roles/reviewer/role.md","role-inline","SCAFFOLD-001;SPEC-001","SPEC-001","csv-wave","3","pending","","",""
-```
-
----
-
-### Column Lifecycle
-
-```
-Decomposer (Phase 1)     Wave Engine (Phase 2)    Agent (Execution)
----------------------    --------------------     -----------------
-id          ---------->  id          ---------->  id
-title       ---------->  title       ---------->  (reads)
-description ---------->  description ---------->  (reads)
-role        ---------->  role        ---------->  (reads)
-file_target ---------->  file_target ---------->  (reads)
-gen_type    ---------->  gen_type    ---------->  (reads)
-deps        ---------->  deps        ---------->  (reads)
-context_from---------->  context_from---------->  (reads)
-exec_mode   ---------->  exec_mode   ---------->  (reads)
-                         wave         ---------->  (reads)
-                         prev_context ---------->  (reads)
-                                                   status
-                                                   findings
-                                                   files_produced
-                                                   error
-```
-
----
-
-## Output Schema (JSON)
-
-Agent output via `report_agent_job_result` (csv-wave tasks):
-
-```json
-{
-  "id": "ROLE-001",
-  "status": "completed",
-  "findings": "Generated coordinator role with entry router, 3 commands (analyze, dispatch, monitor), beat model in monitor.md only",
-  "files_produced": "roles/coordinator/role.md;roles/coordinator/commands/analyze.md;roles/coordinator/commands/dispatch.md;roles/coordinator/commands/monitor.md",
-  "error": ""
-}
-```
-
-Interactive tasks output via structured text or JSON written to `interactive/{id}-result.json`.
-
----
-
-## Discovery Types
-
-| Type | Dedup Key | Data Schema | Description |
-|------|-----------|-------------|-------------|
-| `dir_created` | `data.path` | `{path, description}` | Directory structure created |
-| `file_generated` | `data.file` | `{file, gen_type, sections}` | File generated with sections |
-| `pattern_found` | `data.pattern_name` | `{pattern_name, description}` | Design pattern from golden sample |
-| `config_decision` | `data.decision` | `{decision, rationale, impact}` | Config decision made |
-| `validation_result` | `data.check` | `{check, passed, message}` | Validation check result |
-| `reference_found` | `data.source+data.target` | `{source, target, type}` | Cross-reference between files |
-
-### Discovery NDJSON Format
-
-```jsonl
-{"ts":"2026-03-08T10:00:00Z","worker":"SCAFFOLD-001","type":"dir_created","data":{"path":"~  or <project>/.codex/skills/team-code-review/roles/","description":"Created roles directory with coordinator, analyst, reviewer subdirs"}}
-{"ts":"2026-03-08T10:05:00Z","worker":"ROLE-001","type":"file_generated","data":{"file":"roles/coordinator/role.md","gen_type":"role-bundle","sections":["entry-router","phase-0","phase-1","phase-2","phase-3"]}}
-{"ts":"2026-03-08T10:10:00Z","worker":"SPEC-001","type":"config_decision","data":{"decision":"full-lifecycle pipeline","rationale":"Both analyst and reviewer roles present","impact":"4-tier dependency graph"}}
-```
-
-> 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}" |
-| gen_type valid | Value in {directory, router, role-bundle, role-inline, spec, template, validation} | "Invalid gen_type: {value}" |
-| file_target valid | Path is relative and uses forward slashes | "Invalid file_target: {path}" |
-| Cross-mechanism deps | Interactive to CSV deps resolve correctly | "Cross-mechanism dependency unresolvable: {id}" |

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

@@ -1,62 +0,0 @@
-## TASK ASSIGNMENT
-
-### MANDATORY FIRST STEPS
-1. Read role definition: {role_spec_path} (MUST read first)
-2. Read shared discoveries: {session_folder}/discoveries.ndjson (if exists, skip if not)
-3. Read project context: .workflow/project-tech.json (if exists)
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Description**: {description}
-**Role**: {role}
-
-### Previous Tasks' Findings (Context)
-{prev_context}
-
----
-
-## Execution Protocol
-
-1. **Read role definition**: Load {role_spec_path} for Phase 2-4 domain instructions (MANDATORY)
-2. **Read discoveries**: Load {session_folder}/discoveries.ndjson for shared exploration findings
-3. **Use context**: Apply previous tasks' findings from prev_context above
-4. **Execute**: Follow the role-specific instructions from your role definition file
-5. **Share discoveries**: Append exploration findings to shared board:
-   ```bash
-   echo '{"ts":"<ISO8601>","worker":"{id}","type":"<type>","data":{...}}' >> {session_folder}/discoveries.ndjson
-   ```
-6. **Report result**: Return JSON via report_agent_job_result
-
-### Role Definition Structure
-
-Your role definition file contains:
-- **Phase 2**: Context & scope resolution
-- **Phase 3**: Execution steps
-- **Phase 4**: Output generation
-
-Follow the phases in order as defined in your role file.
-
-### Discovery Types to Share
-
-- `implementation`: {file, function, approach, notes} — Implementation approach taken
-- `test_result`: {test_name, status, duration} — Test execution result
-- `review_comment`: {file, line, severity, comment} — Code review comment
-- `pattern`: {pattern, files[], occurrences} — Code pattern identified
-
----
-
-## Output (report_agent_job_result)
-
-Return JSON:
-{
-  "id": "{id}",
-  "status": "completed" | "failed",
-  "findings": "Key discoveries and implementation notes (max 500 chars)",
-  "error": ""
-}
-
-**Findings format**: Concise summary of what was accomplished, key decisions made, and any important notes for downstream tasks.

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

@@ -1,141 +0,0 @@
-# Team Executor — CSV Schema
-
-## Master CSV: tasks.csv
-
-### Column Definitions
-
-#### Input Columns (Set by Decomposer)
-
-| Column | Type | Required | Description | Example |
-|--------|------|----------|-------------|---------|
-| `id` | string | Yes | Unique task identifier | `"1"` |
-| `title` | string | Yes | Short task title | `"Implement auth module"` |
-| `description` | string | Yes | Detailed task description (self-contained) | `"Create authentication module with JWT support"` |
-| `deps` | string | No | Semicolon-separated dependency task IDs | `"1;2"` |
-| `context_from` | string | No | Semicolon-separated task IDs for context | `"1"` |
-| `exec_mode` | enum | Yes | Execution mechanism: `csv-wave` or `interactive` | `"csv-wave"` |
-| `role` | string | Yes | Role name from session role-specs | `"implementer"` |
-
-#### 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) | `"[Task 1] Created auth module..."` |
-
-#### 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 auth with bcrypt password hashing"` |
-| `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,role,wave,status,findings,error
-1,Implement auth module,Create authentication module with JWT,,,"csv-wave","implementer",1,pending,"",""
-2,Write tests,Write unit tests for auth module,1,1,"csv-wave","tester",2,pending,"",""
-3,Review code,Review implementation and tests,2,2,"interactive","reviewer",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)
-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": "1",
-  "status": "completed",
-  "findings": "Implemented JWT authentication with bcrypt password hashing. Created login, logout, and token refresh endpoints. Added middleware for protected routes.",
-  "error": ""
-}
-```
-
-Interactive tasks output via structured text or JSON written to `interactive/{id}-result.json`.
-
----
-
-## Discovery Types
-
-| Type | Dedup Key | Data Schema | Description |
-|------|-----------|-------------|-------------|
-| `implementation` | `file+function` | `{file, function, approach, notes}` | Implementation approach taken |
-| `test_result` | `test_name` | `{test_name, status, duration}` | Test execution result |
-| `review_comment` | `file+line` | `{file, line, severity, comment}` | Code review comment |
-| `pattern` | `pattern_name` | `{pattern, files[], occurrences}` | Code pattern identified |
-
-### Discovery NDJSON Format
-
-```jsonl
-{"ts":"2026-03-08T14:30:22Z","worker":"1","type":"implementation","data":{"file":"src/auth.ts","function":"login","approach":"JWT-based","notes":"Used bcrypt for password hashing"}}
-{"ts":"2026-03-08T14:35:10Z","worker":"2","type":"test_result","data":{"test_name":"auth.login.success","status":"pass","duration":125}}
-{"ts":"2026-03-08T14:40:05Z","worker":"3","type":"review_comment","data":{"file":"src/auth.ts","line":42,"severity":"medium","comment":"Consider adding rate limiting"}}
-```
-
-> 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 non-empty | Every task has role | "Empty role for task: {id}" |
-| Role exists | Role has corresponding role-spec file | "Role not found: {role}" |

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

@@ -1,131 +0,0 @@
-# Completion Handler Agent
-
-Interactive agent for handling pipeline completion action. Presents deliverables summary and offers Archive/Keep/Export choices.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `agents/completion-handler.md`
-- **Responsibility**: Present 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 complete deliverables listing
-- 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 deliverables inventory
-
-**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 deliverables inventory
-4. Calculate pipeline statistics
-
-**Output**: Deliverables summary ready for user
-
----
-
-### Phase 2: Completion Choice
-
-**Objective**: Present results and get user action
-
-**Steps**:
-
-1. Display pipeline summary with deliverables
-2. Present completion choice:
-
-```javascript
-request_user_input({
-  questions: [{
-    question: "Frontend 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 work" },
-      { label: "Export Results", description: "Export design tokens, component specs, and QA audits" }
-    ]
-  }]
-})
-```
-
-3. Handle response:
-
-| Response | Action |
-|----------|--------|
-| Archive & Clean | Mark session as completed, output final summary |
-| Keep Active | Mark session as paused, keep all artifacts |
-| Export Results | Copy key artifacts to project directory |
-
-**Output**: Completion action result
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Pipeline completed: <task-count> tasks
-- Status: <all-pass|with-warnings|with-failures>
-- QA final score: <score>/10
-
-## Deliverables
-- Design Intelligence: <path>
-- Design Tokens: <path>
-- Component Specs: <path>
-- QA Audits: <path>
-- Implementation: <file-count> files
-
-## 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 |