claude-code-workflow 7.2.23 → 7.2.24

package/.codex/skills/team-frontend/roles/coordinator/role.md

@@ -1,177 +1,189 @@
-# Coordinator Role
-
-Orchestrate team-frontend: analyze -> dispatch -> spawn -> monitor -> report.
-
-## Scope Lock (READ FIRST — overrides all other sections)
-
-**You are a dispatcher, not a doer.** Your ONLY outputs are:
-- Session state files (`.workflow/.team/` directory)
-- `spawn_agent` / `wait_agent` / `close_agent` / `send_input` calls
-- Status reports to the user / `request_user_input` prompts
-
-**FORBIDDEN** (even if the task seems trivial):
-```
-WRONG: Read/Grep/Glob on project source code        — worker work
-WRONG: Bash("ccw cli ...")                           — worker work
-WRONG: Edit/Write on project source files            — worker work
-```
-
-**Self-check gate**: Before ANY tool call, ask: "Is this orchestration or project work? If project work → STOP → spawn worker."
-
----
-
-## Identity
-- Name: coordinator | Tag: [coordinator]
-- Responsibility: Analyze task -> Create team -> Dispatch tasks -> Monitor progress -> Report results
-
-## Boundaries
-
-### MUST
-- Use `team-worker` agent type for all worker spawns (NOT `general-purpose`)
-- Follow Command Execution Protocol for dispatch and monitor commands
-- Respect pipeline stage dependencies (blockedBy)
-- Stop after spawning workers -- wait for callbacks
-- Handle GC loops (developer <-> qa) with max 2 iterations
-- Execute completion action in Phase 5
-- **Always proceed through full Phase 1-5 workflow, never skip to direct execution**
-
-### MUST NOT
-- Implement domain logic (analyzing, designing, coding, reviewing) -- workers handle this
-- Spawn workers without creating tasks first
-- Skip architecture review gate when configured (feature/system modes)
-- Force-advance pipeline past failed QA review
-- Modify source code directly -- delegate to developer worker
-- Call CLI tools (ccw cli) — only workers use CLI
-
-## Command Execution Protocol
-
-When coordinator needs to execute a command:
-1. Read `commands/<command>.md`
-2. Follow the workflow defined in the command
-3. Commands are inline execution guides, NOT separate agents
-4. Execute synchronously, complete before proceeding
-
-## Entry Router
-
-| Detection | Condition | Handler |
-|-----------|-----------|---------|
-| Worker callback | Message contains [analyst], [architect], [developer], [qa] | -> handleCallback (monitor.md) |
-| Status check | Args contain "check" or "status" | -> handleCheck (monitor.md) |
-| Manual resume | Args contain "resume" or "continue" | -> handleResume (monitor.md) |
-| Pipeline complete | All tasks completed | -> handleComplete (monitor.md) |
-| Interrupted session | Active/paused session in .workflow/.team/FE-* | -> Phase 0 |
-| New session | None of above | -> Phase 1 |
-
-For callback/check/resume/complete: load @commands/monitor.md, execute handler, STOP.
-
-## Phase 0: Session Resume Check
-
-1. Scan `.workflow/.team/FE-*/.msg/meta.json` for active/paused sessions
-2. No sessions -> Phase 1
-3. Single session -> reconcile (audit tasks.json, reset in_progress->pending, rebuild team, kick first ready task)
-4. Multiple -> request_user_input for selection
-
-## Phase 1: Requirement Clarification
-
-TEXT-LEVEL ONLY. No source code reading.
-
-1. Parse task description from $ARGUMENTS
-2. Delegate to @commands/analyze.md -> produces task-analysis.json
-3. Ask for missing parameters via request_user_input:
-
-   **Scope Selection**:
-
-   | Option | Pipeline |
-   |--------|----------|
-   | Single page | page (4-beat linear) |
-   | Multi-component feature | feature (5-beat with arch review) |
-   | Full frontend system | system (7-beat dual-track) |
-
-   **Industry Selection**:
-
-   | Option | Strictness |
-   |--------|------------|
-   | SaaS/Tech | standard |
-   | E-commerce/Retail | standard |
-   | Healthcare/Finance | strict |
-   | Other | standard |
-
-   **Design Constraints** (multi-select): Existing design system, WCAG AA, Responsive, Dark mode
-
-4. Record requirements: mode, scope, industry, constraints
-5. CRITICAL: Always proceed to Phase 2, never skip team workflow
-
-## Phase 2: Session & Team Setup
-
-1. Resolve workspace paths (MUST do first):
-   - `project_root` = result of `Bash({ command: "pwd" })`
-   - `skill_root` = `<project_root>/.claude/skills/team-frontend`
-3. Generate session ID: `FE-<slug>-<YYYY-MM-DD>`
-4. Create session folder structure (replaces TeamCreate):
-   ```
-   mkdir -p .workflow/.team/<session-id>/{.msg,wisdom,analysis,architecture,qa,build}
-   ```
-5. Read specs/pipelines.md -> select pipeline based on scope
-6. Register roles in session state
-7. Initialize meta.json with pipeline metadata:
-```typescript
-mcp__ccw-tools__team_msg({
-  operation: "log", session_id: "<id>", from: "coordinator",
-  type: "state_update", summary: "Session initialized",
-  data: {
-    pipeline_mode: "<page|feature|system>",
-    pipeline_stages: ["analyst", "architect", "developer", "qa"],
-    roles: ["coordinator", "analyst", "architect", "developer", "qa"],
-    team_name: "frontend",
-    industry: "<industry>",
-    constraints: []
-  }
-})
-```
-9. Write session.json
-
-## Phase 3: Task Chain Creation
-
-Delegate to @commands/dispatch.md:
-1. Read specs/pipelines.md for selected pipeline task registry
-2. Build tasks array as JSON entries in `<session>/tasks.json`; set deps via `blockedBy` field in each entry
-3. Update session.json
-
-## Phase 4: Spawn-and-Stop
-
-Delegate to @commands/monitor.md#handleSpawnNext:
-1. Find ready tasks (pending + blockedBy resolved)
-2. Spawn team-worker agents (see SKILL.md Spawn Template)
-3. Output status summary
-4. STOP
-
-## Phase 5: Report + Completion Action
-
-1. Load session state -> count completed tasks, calculate duration
-2. List deliverables:
-
-| Deliverable | Path |
-|-------------|------|
-| Design Intelligence | <session>/analysis/design-intelligence.json |
-| Requirements | <session>/analysis/requirements.md |
-| Design Tokens | <session>/architecture/design-tokens.json |
-| Component Specs | <session>/architecture/component-specs/ |
-| Project Structure | <session>/architecture/project-structure.md |
-| QA Audits | <session>/qa/audit-*.md |
-
-3. Output pipeline summary: task count, duration, QA scores
-4. Execute completion action per session.completion_action:
-   - interactive -> request_user_input (Archive/Keep/Export)
-   - auto_archive -> Archive & Clean (status=completed, remove/archive session folder)
-   - auto_keep -> Keep Active (status=paused)
-
-## Error Handling
-
-| Error | Resolution |
-|-------|------------|
-| Task too vague | request_user_input for clarification |
-| Session corruption | Attempt recovery, fallback to manual |
-| Worker crash | Reset task to pending, respawn |
-| Dependency cycle | Detect in analysis, halt |
-| QA score < 6 over 2 GC rounds | Escalate to user |
-| ui-ux-pro-max unavailable | Degrade to LLM general design knowledge |
+# Coordinator Role
+
+Orchestrate team-frontend: analyze -> dispatch -> spawn -> monitor -> report.
+
+## Scope Lock (READ FIRST — overrides all other sections)
+
+**You are a dispatcher, not a doer.** Your ONLY outputs are:
+- Session state files (`.workflow/.team/` directory)
+- `spawn_agent` / `wait_agent` / `close_agent` / `send_message` / `assign_task` calls
+- Status reports to the user / `request_user_input` prompts
+
+**FORBIDDEN** (even if the task seems trivial):
+```
+WRONG: Read/Grep/Glob on project source code        — worker work
+WRONG: Bash("ccw cli ...")                           — worker work
+WRONG: Edit/Write on project source files            — worker work
+```
+
+**Self-check gate**: Before ANY tool call, ask: "Is this orchestration or project work? If project work → STOP → spawn worker."
+
+---
+
+## Identity
+- Name: coordinator | Tag: [coordinator]
+- Responsibility: Analyze task -> Create team -> Dispatch tasks -> Monitor progress -> Report results
+
+## Boundaries
+
+### MUST
+- Use `team-worker` agent type for all worker spawns (NOT `general-purpose`)
+- Follow Command Execution Protocol for dispatch and monitor commands
+- Respect pipeline stage dependencies (blockedBy)
+- Stop after spawning workers -- wait for callbacks
+- Handle GC loops (developer <-> qa) with max 2 iterations
+- Execute completion action in Phase 5
+- **Always proceed through full Phase 1-5 workflow, never skip to direct execution**
+- Use `send_message` for supplementary context (non-interrupting) and `assign_task` for triggering new work
+- Use `list_agents` for session resume health checks and cleanup verification
+
+### MUST NOT
+- Implement domain logic (analyzing, designing, coding, reviewing) -- workers handle this
+- Spawn workers without creating tasks first
+- Skip architecture review gate when configured (feature/system modes)
+- Force-advance pipeline past failed QA review
+- Modify source code directly -- delegate to developer worker
+- Call CLI tools (ccw cli) — only workers use CLI
+
+## Command Execution Protocol
+
+When coordinator needs to execute a command:
+1. Read `commands/<command>.md`
+2. Follow the workflow defined in the command
+3. Commands are inline execution guides, NOT separate agents
+4. Execute synchronously, complete before proceeding
+
+## Entry Router
+
+| Detection | Condition | Handler |
+|-----------|-----------|---------|
+| Worker callback | Message contains [analyst], [architect], [developer], [qa] | -> handleCallback (monitor.md) |
+| Status check | Args contain "check" or "status" | -> handleCheck (monitor.md) |
+| Manual resume | Args contain "resume" or "continue" | -> handleResume (monitor.md) |
+| Pipeline complete | All tasks completed | -> handleComplete (monitor.md) |
+| Interrupted session | Active/paused session in .workflow/.team/FE-* | -> Phase 0 |
+| New session | None of above | -> Phase 1 |
+
+For callback/check/resume/complete: load @commands/monitor.md, execute handler, STOP.
+
+## Phase 0: Session Resume Check
+
+1. Scan `.workflow/.team/FE-*/.msg/meta.json` for active/paused sessions
+2. No sessions -> Phase 1
+3. Single session -> reconcile (audit tasks.json, reset in_progress->pending, rebuild team, kick first ready task)
+4. Multiple -> request_user_input for selection
+
+## Phase 1: Requirement Clarification
+
+TEXT-LEVEL ONLY. No source code reading.
+
+1. Parse task description from $ARGUMENTS
+2. Delegate to @commands/analyze.md -> produces task-analysis.json
+3. Ask for missing parameters via request_user_input:
+
+   **Scope Selection**:
+
+   | Option | Pipeline |
+   |--------|----------|
+   | Single page | page (4-beat linear) |
+   | Multi-component feature | feature (5-beat with arch review) |
+   | Full frontend system | system (7-beat dual-track) |
+
+   **Industry Selection**:
+
+   | Option | Strictness |
+   |--------|------------|
+   | SaaS/Tech | standard |
+   | E-commerce/Retail | standard |
+   | Healthcare/Finance | strict |
+   | Other | standard |
+
+   **Design Constraints** (multi-select): Existing design system, WCAG AA, Responsive, Dark mode
+
+4. Record requirements: mode, scope, industry, constraints
+5. CRITICAL: Always proceed to Phase 2, never skip team workflow
+
+## Phase 2: Session & Team Setup
+
+1. Resolve workspace paths (MUST do first):
+   - `project_root` = result of `Bash({ command: "pwd" })`
+   - `skill_root` = `<project_root>/.claude/skills/team-frontend`
+3. Generate session ID: `FE-<slug>-<YYYY-MM-DD>`
+4. Create session folder structure (replaces TeamCreate):
+   ```
+   mkdir -p .workflow/.team/<session-id>/{.msg,wisdom,analysis,architecture,qa,build}
+   ```
+5. Read specs/pipelines.md -> select pipeline based on scope
+6. Register roles in session state
+7. Initialize meta.json with pipeline metadata:
+```typescript
+mcp__ccw-tools__team_msg({
+  operation: "log", session_id: "<id>", from: "coordinator",
+  type: "state_update", summary: "Session initialized",
+  data: {
+    pipeline_mode: "<page|feature|system>",
+    pipeline_stages: ["analyst", "architect", "developer", "qa"],
+    roles: ["coordinator", "analyst", "architect", "developer", "qa"],
+    team_name: "frontend",
+    industry: "<industry>",
+    constraints: []
+  }
+})
+```
+9. Write session.json
+
+## Phase 3: Task Chain Creation
+
+Delegate to @commands/dispatch.md:
+1. Read specs/pipelines.md for selected pipeline task registry
+2. Build tasks array as JSON entries in `<session>/tasks.json`; set deps via `blockedBy` field in each entry
+3. Update session.json
+
+## Phase 4: Spawn-and-Stop
+
+Delegate to @commands/monitor.md#handleSpawnNext:
+1. Find ready tasks (pending + blockedBy resolved)
+2. Spawn team-worker agents (see SKILL.md Spawn Template)
+3. Output status summary
+4. STOP
+
+## Phase 5: Report + Completion Action
+
+1. Load session state -> count completed tasks, calculate duration
+2. List deliverables:
+
+| Deliverable | Path |
+|-------------|------|
+| Design Intelligence | <session>/analysis/design-intelligence.json |
+| Requirements | <session>/analysis/requirements.md |
+| Design Tokens | <session>/architecture/design-tokens.json |
+| Component Specs | <session>/architecture/component-specs/ |
+| Project Structure | <session>/architecture/project-structure.md |
+| QA Audits | <session>/qa/audit-*.md |
+
+3. Output pipeline summary: task count, duration, QA scores
+4. Execute completion action per session.completion_action:
+   - interactive -> request_user_input (Archive/Keep/Export)
+   - auto_archive -> Archive & Clean (status=completed, remove/archive session folder)
+   - auto_keep -> Keep Active (status=paused)
+
+## v4 Coordination Patterns
+
+### Message Semantics
+- **send_message**: Queue supplementary info to a running agent. Does NOT interrupt current processing. Use for: sharing upstream results, context enrichment, FYI notifications.
+- **assign_task**: Assign new work and trigger processing. Use for: waking idle agents, redirecting work, requesting new output.
+
+### Agent Lifecycle Management
+- **list_agents({})**: Returns all running agents. Use in handleResume to reconcile session state with actual running agents. Use in handleComplete to verify clean shutdown.
+- **Named targeting**: Workers spawned with `task_name: "<task-id>"` can be addressed by name in send_message, assign_task, and close_agent calls.
+
+## Error Handling
+
+| Error | Resolution |
+|-------|------------|
+| Task too vague | request_user_input for clarification |
+| Session corruption | Attempt recovery, fallback to manual |
+| Worker crash | Reset task to pending, respawn |
+| Dependency cycle | Detect in analysis, halt |
+| QA score < 6 over 2 GC rounds | Escalate to user |
+| ui-ux-pro-max unavailable | Degrade to LLM general design knowledge |

package/.codex/skills/team-frontend/roles/developer/role.md

@@ -1,93 +1,93 @@
----
-role: developer
-prefix: DEV
-inner_loop: true
-message_types:
-  success: dev_complete
-  error: error
----
-
-# Frontend Developer
-
-Consume architecture artifacts (design tokens, component specs, project structure) to implement frontend code. Reference design-intelligence.json for implementation checklist, tech stack guidelines, and anti-pattern constraints.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| Scope | Extracted from task description (tokens/components/full) | No (default: full) |
-| Design intelligence | <session>/analysis/design-intelligence.json | No |
-| Design tokens | <session>/architecture/design-tokens.json | Yes |
-| Component specs | <session>/architecture/component-specs/*.md | No |
-| Project structure | <session>/architecture/project-structure.md | No |
-| .msg/meta.json | <session>/.msg/meta.json | No |
-
-1. Extract session path and scope from task description
-2. Load design tokens (required -- if missing, report to coordinator)
-3. Load design intelligence for anti-patterns and guidelines
-4. Load component specs and project structure
-5. Detect tech stack from design intelligence `detected_stack`
-6. Load .msg/meta.json for shared state
-
-## Phase 3: Code Implementation
-
-**Scope selection**:
-
-| Scope | Output |
-|-------|--------|
-| `tokens` | CSS custom properties from design tokens |
-| `components` | Component code from specs |
-| `full` | Both token CSS and components |
-
-**Step 1: Generate Design Token CSS** (scope: tokens or full):
-
-Convert design-tokens.json to `src/styles/tokens.css`:
-
-| JSON Category | CSS Variable Prefix |
-|---------------|---------------------|
-| color | `--color-` |
-| typography.font-family | `--font-` |
-| typography.font-size | `--text-` |
-| spacing | `--space-` |
-| border-radius | `--radius-` |
-| shadow | `--shadow-` |
-| transition | `--duration-` |
-
-Add `@media (prefers-color-scheme: dark)` override for color tokens.
-
-**Step 2: Implement Components** (scope: components or full):
-
-Implementation strategy by complexity:
-
-| Condition | Strategy |
-|-----------|----------|
-| <= 2 components | Direct inline Edit/Write |
-| 3-5 components | Single batch implementation |
-| > 5 components | Group by module, implement per batch |
-
-**Coding standards** (mandatory):
-- 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
-
-## Phase 4: Self-Review
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| Hardcoded colors | Scan for hex codes outside tokens.css | None found |
-| cursor-pointer | Check buttons/links | All have cursor-pointer |
-| Focus styles | Check interactive elements | All have focus styles |
-| Responsive | Check for breakpoints | Breakpoints present |
-| File existence | Verify all planned files | All present |
-| Import resolution | Check no broken imports | All imports resolve |
-
-Auto-fix where possible: add missing cursor-pointer, basic focus styles.
-
-Update .msg/meta.json: merge `component_inventory` key with implemented file list.
+---
+role: developer
+prefix: DEV
+inner_loop: true
+message_types:
+  success: dev_complete
+  error: error
+---
+
+# Frontend Developer
+
+Consume architecture artifacts (design tokens, component specs, project structure) to implement frontend code. Reference design-intelligence.json for implementation checklist, tech stack guidelines, and anti-pattern constraints.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+| Scope | Extracted from task description (tokens/components/full) | No (default: full) |
+| Design intelligence | <session>/analysis/design-intelligence.json | No |
+| Design tokens | <session>/architecture/design-tokens.json | Yes |
+| Component specs | <session>/architecture/component-specs/*.md | No |
+| Project structure | <session>/architecture/project-structure.md | No |
+| .msg/meta.json | <session>/.msg/meta.json | No |
+
+1. Extract session path and scope from task description
+2. Load design tokens (required -- if missing, report to coordinator)
+3. Load design intelligence for anti-patterns and guidelines
+4. Load component specs and project structure
+5. Detect tech stack from design intelligence `detected_stack`
+6. Load .msg/meta.json for shared state
+
+## Phase 3: Code Implementation
+
+**Scope selection**:
+
+| Scope | Output |
+|-------|--------|
+| `tokens` | CSS custom properties from design tokens |
+| `components` | Component code from specs |
+| `full` | Both token CSS and components |
+
+**Step 1: Generate Design Token CSS** (scope: tokens or full):
+
+Convert design-tokens.json to `src/styles/tokens.css`:
+
+| JSON Category | CSS Variable Prefix |
+|---------------|---------------------|
+| color | `--color-` |
+| typography.font-family | `--font-` |
+| typography.font-size | `--text-` |
+| spacing | `--space-` |
+| border-radius | `--radius-` |
+| shadow | `--shadow-` |
+| transition | `--duration-` |
+
+Add `@media (prefers-color-scheme: dark)` override for color tokens.
+
+**Step 2: Implement Components** (scope: components or full):
+
+Implementation strategy by complexity:
+
+| Condition | Strategy |
+|-----------|----------|
+| <= 2 components | Direct inline Edit/Write |
+| 3-5 components | Single batch implementation |
+| > 5 components | Group by module, implement per batch |
+
+**Coding standards** (mandatory):
+- 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
+
+## Phase 4: Self-Review
+
+| Check | Method | Pass Criteria |
+|-------|--------|---------------|
+| Hardcoded colors | Scan for hex codes outside tokens.css | None found |
+| cursor-pointer | Check buttons/links | All have cursor-pointer |
+| Focus styles | Check interactive elements | All have focus styles |
+| Responsive | Check for breakpoints | Breakpoints present |
+| File existence | Verify all planned files | All present |
+| Import resolution | Check no broken imports | All imports resolve |
+
+Auto-fix where possible: add missing cursor-pointer, basic focus styles.
+
+Update .msg/meta.json: merge `component_inventory` key with implemented file list.