claude-code-workflow 7.2.15 → 7.2.16

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

@@ -1,165 +0,0 @@
-# Team Coordinate -- 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) | `"RESEARCH-001"` |
-| `title` | string | Yes | Short task title | `"Investigate auth patterns"` |
-| `description` | string | Yes | Detailed task description (self-contained) with goal, steps, success criteria, key files | `"PURPOSE: Research JWT auth patterns..."` |
-| `role` | string | Yes | Dynamic role name | `"researcher"` |
-| `responsibility_type` | enum | Yes | `orchestration`, `read-only`, `code-gen`, `code-gen-docs`, `validation` | `"orchestration"` |
-| `output_type` | enum | Yes | `artifact` (session files), `codebase` (project files), `mixed` | `"artifact"` |
-| `deps` | string | No | Semicolon-separated dependency task IDs | `"RESEARCH-001;DESIGN-001"` |
-| `context_from` | string | No | Semicolon-separated task IDs for context | `"RESEARCH-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) | `"[RESEARCH-001] Found 3 auth patterns..."` |
-
-#### 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 with refresh token support..."` |
-| `artifacts_produced` | string | Semicolon-separated paths of produced artifacts | `"artifacts/research-findings.md;src/auth/jwt.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.
-
----
-
-### Dynamic Role Prefixes
-
-| Capability | Prefix | Responsibility Type |
-|------------|--------|---------------------|
-| researcher | RESEARCH | orchestration |
-| writer | DRAFT | code-gen-docs |
-| developer | IMPL | code-gen |
-| designer | DESIGN | orchestration |
-| analyst | ANALYSIS | read-only |
-| tester | TEST | validation |
-| planner | PLAN | orchestration |
-| (default) | TASK | orchestration |
-
----
-
-### Example Data
-
-```csv
-id,title,description,role,responsibility_type,output_type,deps,context_from,exec_mode,wave,status,findings,artifacts_produced,error
-"RESEARCH-001","Research auth patterns","PURPOSE: Investigate JWT authentication patterns and industry best practices | Success: Comprehensive findings document with pattern comparison\nTASK:\n- Survey JWT vs session-based auth\n- Compare token refresh strategies\n- Document security considerations\nCONTEXT:\n- Key files: src/auth/*, src/middleware/*\nEXPECTED: artifacts/research-findings.md","researcher","orchestration","artifact","","","csv-wave","1","pending","","",""
-"DESIGN-001","Design auth architecture","PURPOSE: Design authentication module architecture based on research | Success: Architecture document with component diagram\nTASK:\n- Define auth module structure\n- Design token lifecycle\n- Plan middleware integration\nCONTEXT:\n- Upstream: RESEARCH-001 findings\nEXPECTED: artifacts/auth-design.md","designer","orchestration","artifact","RESEARCH-001","RESEARCH-001","csv-wave","2","pending","","",""
-"IMPL-001","Implement auth module","PURPOSE: Build JWT authentication middleware | Success: Working auth module with tests passing\nTASK:\n- Create JWT utility functions\n- Implement auth middleware\n- Add route guards\nCONTEXT:\n- Upstream: DESIGN-001 architecture\n- Key files: src/auth/*, src/middleware/*\nEXPECTED: Source files + artifacts/implementation-summary.md","developer","code-gen","mixed","DESIGN-001","DESIGN-001","csv-wave","3","pending","","",""
-"TEST-001","Test auth implementation","PURPOSE: Validate auth module correctness | Success: All tests pass, coverage >= 80%\nTASK:\n- Write unit tests for JWT utilities\n- Write integration tests for middleware\n- Run test suite\nCONTEXT:\n- Upstream: IMPL-001 implementation\nEXPECTED: artifacts/test-report.md","tester","validation","artifact","IMPL-001","IMPL-001","csv-wave","4","pending","","",""
-```
-
----
-
-### Column Lifecycle
-
-```
-Decomposer (Phase 1)     Wave Engine (Phase 2)    Agent (Execution)
----------------------    --------------------     -----------------
-id          ---------->  id          ---------->  id
-title       ---------->  title       ---------->  (reads)
-description ---------->  description ---------->  (reads)
-role        ---------->  role        ---------->  (reads)
-responsibility_type --->  responsibility_type --->  (reads)
-output_type ---------->  output_type ---------->  (reads)
-deps        ---------->  deps        ---------->  (reads)
-context_from---------->  context_from---------->  (reads)
-exec_mode   ---------->  exec_mode   ---------->  (reads)
-                         wave         ---------->  (reads)
-                         prev_context ---------->  (reads)
-                                                   status
-                                                   findings
-                                                   artifacts_produced
-                                                   error
-```
-
----
-
-## Output Schema (JSON)
-
-Agent output via `report_agent_job_result` (csv-wave tasks):
-
-```json
-{
-  "id": "IMPL-001",
-  "status": "completed",
-  "findings": "Implemented JWT auth middleware with access/refresh token support. Created 3 files: jwt.ts, auth-middleware.ts, route-guard.ts. All syntax checks pass.",
-  "artifacts_produced": "artifacts/implementation-summary.md;src/auth/jwt.ts;src/auth/auth-middleware.ts",
-  "error": ""
-}
-```
-
-Interactive tasks output via structured text or JSON written to `interactive/{id}-result.json`.
-
----
-
-## Discovery Types
-
-| Type | Dedup Key | Data Schema | Description |
-|------|-----------|-------------|-------------|
-| `pattern_found` | `data.pattern_name+data.location` | `{pattern_name, location, description}` | Design pattern identified |
-| `file_modified` | `data.file` | `{file, change, lines_added}` | File change recorded |
-| `dependency_found` | `data.from+data.to` | `{from, to, type}` | Dependency relationship |
-| `issue_found` | `data.file+data.line` | `{file, line, severity, description}` | Issue discovered |
-| `decision_made` | `data.decision` | `{decision, rationale, impact}` | Design decision |
-| `artifact_produced` | `data.path` | `{name, path, producer, type}` | Deliverable created |
-
-### Discovery NDJSON Format
-
-```jsonl
-{"ts":"2026-03-08T10:00:00Z","worker":"RESEARCH-001","type":"pattern_found","data":{"pattern_name":"Repository Pattern","location":"src/repos/","description":"Data access layer uses repository pattern"}}
-{"ts":"2026-03-08T10:05:00Z","worker":"IMPL-001","type":"file_modified","data":{"file":"src/auth/jwt.ts","change":"Added JWT middleware","lines_added":45}}
-{"ts":"2026-03-08T10:10:00Z","worker":"IMPL-001","type":"artifact_produced","data":{"name":"implementation-summary","path":"artifacts/implementation-summary.md","producer":"developer","type":"markdown"}}
-```
-
-> 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 matches a generated role-instruction | "No instruction for role: {role}" |
-| Cross-mechanism deps | Interactive to CSV deps resolve correctly | "Cross-mechanism dependency unresolvable: {id}" |

package/.codex/skills/team-designer/agents/requirement-clarifier.md

@@ -1,247 +0,0 @@
-# Requirement Clarifier Agent
-
-Interactive agent for gathering and refining team skill requirements from user input. Used in Phase 0 when the skill description needs clarification or missing details.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `agents/requirement-clarifier.md`
-- **Responsibility**: Gather skill name, roles, pipelines, specs, and build teamConfig
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Parse user input to detect input source (reference, structured, natural)
-- Gather all required teamConfig fields
-- Confirm configuration with user before reporting complete
-- Produce structured output following template
-- Write teamConfig.json to session folder
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Generate skill files (that is Phase 2 work)
-- Approve incomplete configurations
-- Produce unstructured output
-- Exceed defined scope boundaries
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | built-in | Load reference skills, existing patterns |
-| `request_user_input` | built-in | Gather missing details from user |
-| `Write` | built-in | Store teamConfig.json |
-| `Glob` | built-in | Find reference skill files |
-
-### Tool Usage Patterns
-
-**Read Pattern**: Load reference skill for pattern extraction
-```
-Read(".codex/skills/<reference-skill>/SKILL.md")
-Read(".codex/skills/<reference-skill>/schemas/tasks-schema.md")
-```
-
-**Write Pattern**: Store configuration
-```
-Write("<session>/teamConfig.json", <config>)
-```
-
----
-
-## Execution
-
-### Phase 1: Input Detection
-
-**Objective**: Detect input source type and extract initial information
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| User requirement | Yes | Skill description from $ARGUMENTS |
-| Reference skill | No | Existing skill if "based on" detected |
-
-**Steps**:
-
-1. Parse user input to detect source type:
-
-| Source Type | Detection | Action |
-|-------------|-----------|--------|
-| Reference | Contains "based on", "like", skill path | Read referenced skill, extract roles/pipelines |
-| Structured | Contains ROLES:, PIPELINES:, DOMAIN: | Parse structured fields directly |
-| Natural language | Default | Analyze keywords for role discovery |
-
-2. Extract initial information from detected source
-3. Identify missing required fields
-
-**Output**: Initial teamConfig draft with gaps identified
-
----
-
-### Phase 2: Requirement Gathering
-
-**Objective**: Fill in all required teamConfig fields
-
-**Steps**:
-
-1. **Core Identity** -- gather if not clear from input:
-
-```javascript
-request_user_input({
-  questions: [
-    {
-      question: "Team skill name? (kebab-case, e.g., team-code-review)",
-      header: "Skill Name",
-      id: "skill_name",
-      options: [
-        { label: "<auto-suggested-name> (Recommended)", description: "Auto-suggested from description" },
-        { label: "Custom", description: "Enter custom name" }
-      ]
-    },
-    {
-      question: "Session prefix? (3-4 chars for task IDs, e.g., TCR)",
-      header: "Prefix",
-      id: "session_prefix",
-      options: [
-        { label: "<auto-suggested-prefix> (Recommended)", description: "Auto-suggested" },
-        { label: "Custom", description: "Enter custom prefix" }
-      ]
-    }
-  ]
-})
-```
-
-2. **Role Discovery** -- identify roles from domain keywords:
-
-| Signal | Keywords | Default Role |
-|--------|----------|-------------|
-| Analysis | analyze, research, investigate | analyst |
-| Planning | plan, design, architect | planner |
-| Writing | write, document, draft | writer |
-| Implementation | implement, build, code | executor |
-| Testing | test, verify, validate | tester |
-| Review | review, audit, check | reviewer |
-
-3. **Commands Distribution** -- determine per role:
-
-| Rule | Condition | Result |
-|------|-----------|--------|
-| Coordinator | Always | commands/: analyze, dispatch, monitor |
-| Multi-action role | 2+ distinct actions | commands/ folder |
-| Single-action role | 1 action | Inline in role.md |
-
-4. **Pipeline Construction** -- determine from role combination:
-
-| Roles Present | Pipeline Type |
-|---------------|---------------|
-| analyst + writer + executor | full-lifecycle |
-| analyst + writer (no executor) | spec-only |
-| planner + executor (no analyst) | impl-only |
-| Other combinations | custom |
-
-5. **Specs and Templates** -- determine required specs:
-   - Always: pipelines.md
-   - If quality gates needed: quality-gates.md
-   - If writer role: domain-appropriate templates
-
-**Output**: Complete teamConfig ready for confirmation
-
----
-
-### Phase 3: Confirmation
-
-**Objective**: Present configuration summary and get user approval
-
-**Steps**:
-
-1. Display configuration summary:
-
-```
-Team Skill Configuration Summary
-
-Skill Name:     <skillName>
-Session Prefix: <sessionPrefix>
-Domain:         <domain>
-Target:         .codex/skills/<skillName>/
-
-Roles:
-  +- coordinator (commands: analyze, dispatch, monitor)
-  +- <role-a> [PREFIX-*] (inline)
-  +- <role-b> [PREFIX-*] (commands: cmd1, cmd2)
-
-Pipelines:
-  +- <pipeline-name>: TASK-001 -> TASK-002 -> TASK-003
-
-Specs: pipelines, <additional>
-Templates: <list or none>
-```
-
-2. Present confirmation:
-
-```javascript
-request_user_input({
-  questions: [{
-    question: "Confirm this team skill configuration?",
-    header: "Config Review",
-    id: "config_review",
-    options: [
-      { label: "Confirm (Recommended)", description: "Proceed with generation" },
-      { label: "Modify Roles", description: "Add, remove, or change roles" },
-      { label: "Modify Pipelines", description: "Change pipeline structure" }
-    ]
-  }]
-})
-```
-
-3. Handle response:
-
-| Response | Action |
-|----------|--------|
-| Confirm | Write teamConfig.json, report complete |
-| Modify Roles | Loop back to role gathering |
-| Modify Pipelines | Loop back to pipeline construction |
-| Cancel | Report cancelled status |
-
-**Output**: Confirmed teamConfig.json written to session folder
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Configuration: <confirmed|modified|cancelled>
-- Skill: <skill-name>
-
-## Configuration
-- Roles: <count> roles defined
-- Pipelines: <count> pipelines
-- Target: <target-dir>
-
-## Details
-- Role list with prefix and commands structure
-- Pipeline definitions with task flow
-- Specs and templates list
-
-## Open Questions
-1. Any unresolved items from clarification
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Reference skill not found | Report error, ask for correct path |
-| Invalid role name | Suggest valid kebab-case alternative |
-| Conflicting pipeline structure | Ask user to resolve |
-| User does not respond | Timeout, report partial with current config |
-| Processing failure | Output partial results with clear status indicator |

package/.codex/skills/team-designer/agents/validation-reporter.md

@@ -1,186 +0,0 @@
-# Validation Reporter Agent
-
-Validate generated skill package structure and content, reporting results with PASS/WARN/FAIL verdict.
-
-## Identity
-
-- **Type**: `interactive`
-- **Role File**: `agents/validation-reporter.md`
-- **Responsibility**: Validate generated skill package structure and content, report results
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Load the generated skill package from session artifacts
-- Validate all structural integrity checks
-- Produce structured output with clear PASS/WARN/FAIL verdict
-- Include specific file references in findings
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Modify generated skill files
-- Produce unstructured output
-- Report PASS without actually validating all checks
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | builtin | Load generated skill files and verify content |
-| `Glob` | builtin | Find files by pattern in skill package |
-| `Grep` | builtin | Search for cross-references and patterns |
-| `Bash` | builtin | Run validation commands, check JSON syntax |
-
-### Tool Usage Patterns
-
-**Read Pattern**: Load skill package files for validation
-```
-Read("{session_folder}/artifacts/<skill-name>/SKILL.md")
-Read("{session_folder}/artifacts/<skill-name>/team-config.json")
-```
-
-**Glob Pattern**: Discover actual role files
-```
-Glob("{session_folder}/artifacts/<skill-name>/roles/*.md")
-Glob("{session_folder}/artifacts/<skill-name>/commands/*.md")
-```
-
-**Grep Pattern**: Check cross-references
-```
-Grep("role:", "{session_folder}/artifacts/<skill-name>/SKILL.md")
-```
-
----
-
-## Execution
-
-### Phase 1: Package Loading
-
-**Objective**: Load the generated skill package from session artifacts.
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| Skill package path | Yes | Path to generated skill directory in artifacts/ |
-| teamConfig.json | Yes | Original configuration used for generation |
-
-**Steps**:
-
-1. Read SKILL.md from the generated package
-2. Read team-config.json from the generated package
-3. Enumerate all files in the package using Glob
-4. Read teamConfig.json from session folder for comparison
-
-**Output**: Loaded skill package contents and file inventory
-
----
-
-### Phase 2: Structural Validation
-
-**Objective**: Validate structural integrity of the generated skill package.
-
-**Steps**:
-
-1. **SKILL.md validation**:
-   - Verify file exists
-   - Verify valid frontmatter (name, description, allowed-tools)
-   - Verify Role Registry table is present
-
-2. **Role Registry consistency**:
-   - Extract roles listed in SKILL.md Role Registry table
-   - Glob actual files in roles/ directory
-   - Compare: every registry entry has a matching file, every file has a registry entry
-
-3. **Role file validation**:
-   - Read each role.md in roles/ directory
-   - Verify valid frontmatter (prefix, inner_loop, message_types)
-   - Check frontmatter values are non-empty
-
-4. **Pipeline validation**:
-   - Extract pipeline stages from SKILL.md or specs/pipelines.md
-   - Verify each stage references an existing role
-
-5. **team-config.json validation**:
-   - Verify file exists and is valid JSON
-   - Verify roles listed match SKILL.md Role Registry
-
-6. **Cross-reference validation**:
-   - Check coordinator commands/ files exist if referenced in SKILL.md
-   - Verify no broken file paths in cross-references
-
-7. **Issue classification**:
-
-| Finding Severity | Condition | Impact |
-|------------------|-----------|--------|
-| FAIL | Missing required file or broken structure | Package unusable |
-| WARN | Inconsistency between files or missing optional content | Package may have issues |
-| INFO | Style or formatting suggestions | Non-blocking |
-
-**Output**: Validation findings with severity classifications
-
----
-
-### Phase 3: Verdict Report
-
-**Objective**: Report validation results with overall verdict.
-
-| Verdict | Condition | Action |
-|---------|-----------|--------|
-| PASS | No FAIL findings, zero or few WARN | Package is ready for use |
-| WARN | No FAIL findings, but multiple WARN issues | Package usable with noted issues |
-| FAIL | One or more FAIL findings | Package requires regeneration or manual fix |
-
-**Output**: Verdict with detailed findings
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Verdict: PASS | WARN | FAIL
-- Skill: <skill-name>
-- Files checked: <count>
-
-## Findings
-- [FAIL] description with file reference (if any)
-- [WARN] description with file reference (if any)
-- [INFO] description with file reference (if any)
-
-## Validation Details
-- SKILL.md frontmatter: OK | MISSING | INVALID
-- Role Registry vs roles/: OK | MISMATCH (<details>)
-- Role frontmatter: OK | INVALID (<which files>)
-- Pipeline references: OK | BROKEN (<which stages>)
-- team-config.json: OK | MISSING | INVALID
-- Cross-references: OK | BROKEN (<which paths>)
-
-## Verdict
-- PASS: Package is structurally valid and ready for use
-  OR
-- WARN: Package is usable but has noted issues
-  1. Issue description
-  OR
-- FAIL: Package requires fixes before use
-  1. Issue description + suggested resolution
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Skill package directory not found | Report as FAIL, request correct path |
-| SKILL.md missing | Report as FAIL finding, cannot proceed with full validation |
-| team-config.json invalid JSON | Report as FAIL, include parse error |
-| Role file unreadable | Report as WARN, note which file |
-| Timeout approaching | Output current findings with "PARTIAL" status |