claude-code-workflow 7.2.23 → 7.2.24

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

@@ -1,79 +1,79 @@
----
-role: qa
-prefix: QA
-inner_loop: false
-message_types:
-  success: qa_passed
-  error: error
----
-
-# QA Engineer
-
-Execute 5-dimension quality audit integrating ux-guidelines Do/Don't rules, pre-delivery checklist, and industry anti-pattern library. Perform CSS-level precise review on architecture artifacts and implementation code.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| Review type | Extracted from task description | No (default: code-review) |
-| Design intelligence | <session>/analysis/design-intelligence.json | No |
-| Design tokens | <session>/architecture/design-tokens.json | No |
-| .msg/meta.json | <session>/.msg/meta.json | No |
-
-1. Extract session path and review type from task description
-2. Load design intelligence (for anti-patterns, must-have rules)
-3. Load design tokens (for compliance checks)
-4. Load .msg/meta.json (for industry context, strictness level)
-5. Collect files to review based on review type:
-
-| Type | Files to Review |
-|------|-----------------|
-| architecture-review | `<session>/architecture/**/*` |
-| token-review | `<session>/architecture/**/*` |
-| code-review | `src/**/*.{tsx,jsx,vue,svelte,html,css}` |
-| final | `src/**/*.{tsx,jsx,vue,svelte,html,css}` |
-
-## Phase 3: 5-Dimension Audit
-
-| Dimension | Weight | Focus |
-|-----------|--------|-------|
-| Code Quality | 0.20 | Structure, naming, maintainability |
-| Accessibility | 0.25 | WCAG compliance, keyboard nav, screen reader |
-| Design Compliance | 0.20 | Anti-pattern check, design token usage |
-| UX Best Practices | 0.20 | Interaction patterns, responsive, animations |
-| Pre-Delivery | 0.15 | Final checklist (code-review/final types only) |
-
-**Dimension 1 -- Code Quality**: File length (>300 LOC), console.log, empty catch, unused imports.
-
-**Dimension 2 -- Accessibility**: Image alt text, input labels, button text, heading hierarchy, focus styles, ARIA roles. Strict mode (medical/financial): prefers-reduced-motion required.
-
-**Dimension 3 -- Design Compliance**: Hardcoded colors (must use `var(--color-*)`), hardcoded spacing, industry anti-patterns from design intelligence.
-
-**Dimension 4 -- UX Best Practices**: cursor-pointer on clickable, transition 150-300ms, responsive design, loading states, error states.
-
-**Dimension 5 -- Pre-Delivery** (final/code-review only): No emoji icons, cursor-pointer, transitions, focus states, reduced-motion, responsive, no hardcoded colors, dark mode support.
-
-**Score calculation**: `score = sum(dimension_score * weight)`
-
-**Verdict**:
-
-| Condition | Verdict | Message Type |
-|-----------|---------|-------------|
-| score >= 8 AND critical == 0 | PASSED | `qa_passed` |
-| score >= 6 AND critical == 0 | PASSED_WITH_WARNINGS | `qa_result` |
-| score < 6 OR critical > 0 | FIX_REQUIRED | `fix_required` |
-
-## Phase 4: Self-Review
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| All dimensions scored | Check 5 dimension scores | All present |
-| Audit report written | File check | audit-NNN.md exists |
-| Verdict determined | Score calculated | Verdict assigned |
-| Issues categorized | Severity labels | All issues have severity |
-
-Write audit report to `<session>/qa/audit-<NNN>.md` with: summary, dimension scores, issues by severity, passed dimensions.
-
-Update .msg/meta.json: append to `qa_history` array.
+---
+role: qa
+prefix: QA
+inner_loop: false
+message_types:
+  success: qa_passed
+  error: error
+---
+
+# QA Engineer
+
+Execute 5-dimension quality audit integrating ux-guidelines Do/Don't rules, pre-delivery checklist, and industry anti-pattern library. Perform CSS-level precise review on architecture artifacts and implementation code.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+| Review type | Extracted from task description | No (default: code-review) |
+| Design intelligence | <session>/analysis/design-intelligence.json | No |
+| Design tokens | <session>/architecture/design-tokens.json | No |
+| .msg/meta.json | <session>/.msg/meta.json | No |
+
+1. Extract session path and review type from task description
+2. Load design intelligence (for anti-patterns, must-have rules)
+3. Load design tokens (for compliance checks)
+4. Load .msg/meta.json (for industry context, strictness level)
+5. Collect files to review based on review type:
+
+| Type | Files to Review |
+|------|-----------------|
+| architecture-review | `<session>/architecture/**/*` |
+| token-review | `<session>/architecture/**/*` |
+| code-review | `src/**/*.{tsx,jsx,vue,svelte,html,css}` |
+| final | `src/**/*.{tsx,jsx,vue,svelte,html,css}` |
+
+## Phase 3: 5-Dimension Audit
+
+| Dimension | Weight | Focus |
+|-----------|--------|-------|
+| Code Quality | 0.20 | Structure, naming, maintainability |
+| Accessibility | 0.25 | WCAG compliance, keyboard nav, screen reader |
+| Design Compliance | 0.20 | Anti-pattern check, design token usage |
+| UX Best Practices | 0.20 | Interaction patterns, responsive, animations |
+| Pre-Delivery | 0.15 | Final checklist (code-review/final types only) |
+
+**Dimension 1 -- Code Quality**: File length (>300 LOC), console.log, empty catch, unused imports.
+
+**Dimension 2 -- Accessibility**: Image alt text, input labels, button text, heading hierarchy, focus styles, ARIA roles. Strict mode (medical/financial): prefers-reduced-motion required.
+
+**Dimension 3 -- Design Compliance**: Hardcoded colors (must use `var(--color-*)`), hardcoded spacing, industry anti-patterns from design intelligence.
+
+**Dimension 4 -- UX Best Practices**: cursor-pointer on clickable, transition 150-300ms, responsive design, loading states, error states.
+
+**Dimension 5 -- Pre-Delivery** (final/code-review only): No emoji icons, cursor-pointer, transitions, focus states, reduced-motion, responsive, no hardcoded colors, dark mode support.
+
+**Score calculation**: `score = sum(dimension_score * weight)`
+
+**Verdict**:
+
+| Condition | Verdict | Message Type |
+|-----------|---------|-------------|
+| score >= 8 AND critical == 0 | PASSED | `qa_passed` |
+| score >= 6 AND critical == 0 | PASSED_WITH_WARNINGS | `qa_result` |
+| score < 6 OR critical > 0 | FIX_REQUIRED | `fix_required` |
+
+## Phase 4: Self-Review
+
+| Check | Method | Pass Criteria |
+|-------|--------|---------------|
+| All dimensions scored | Check 5 dimension scores | All present |
+| Audit report written | File check | audit-NNN.md exists |
+| Verdict determined | Score calculated | Verdict assigned |
+| Issues categorized | Severity labels | All issues have severity |
+
+Write audit report to `<session>/qa/audit-<NNN>.md` with: summary, dimension scores, issues by severity, passed dimensions.
+
+Update .msg/meta.json: append to `qa_history` array.

package/.codex/skills/team-frontend/specs/pipelines.md

@@ -1,76 +1,76 @@
-# Frontend Pipeline Definitions
-
-## Pipeline Modes
-
-### Page Mode (4 beats, linear)
-
-```
-ANALYZE-001 --> ARCH-001 --> DEV-001 --> QA-001
-[analyst]       [architect]  [developer]  [qa]
-```
-
-### Feature Mode (5 beats, with architecture review gate)
-
-```
-ANALYZE-001 --> ARCH-001 --> QA-001 --> DEV-001 --> QA-002
-[analyst]       [architect]  [qa:arch]   [developer]  [qa:code]
-```
-
-### System Mode (7 beats, dual-track parallel)
-
-```
-ANALYZE-001 --> ARCH-001 --> QA-001 --> ARCH-002 ─┐
-[analyst]       [architect]  [qa:arch]  [architect] |
-                                        DEV-001   ──┘ --> QA-002 --> DEV-002 --> QA-003
-                                        [developer:tokens]  [qa]    [developer]  [qa:final]
-```
-
-### Generator-Critic Loop (developer <-> qa)
-
-```
-developer (Generator) -> QA artifact -> qa (Critic)
-                      <- QA feedback <-
-                         (max 2 rounds)
-
-Convergence: qa.score >= 8 && qa.critical_count === 0
-```
-
-## Task Metadata Registry
-
-| Task ID | Role | Pipeline | Dependencies | Description |
-|---------|------|----------|-------------|-------------|
-| ANALYZE-001 | analyst | all | (none) | Requirement analysis + design intelligence |
-| ARCH-001 | architect | all | ANALYZE-001 | Design token system + component architecture |
-| ARCH-002 | architect | system | QA-001 | Component specs refinement |
-| DEV-001 | developer | all | ARCH-001 or QA-001 | Frontend implementation |
-| DEV-002 | developer | system | QA-002 | Component implementation |
-| DEV-fix-N | developer | all | QA-N (GC loop trigger) | Fix issues from QA |
-| QA-001 | qa | all | ARCH-001 or DEV-001 | Architecture or code review |
-| QA-002 | qa | feature/system | DEV-001 | Code review |
-| QA-003 | qa | system | DEV-002 | Final quality check |
-| QA-recheck-N | qa | all | DEV-fix-N | Re-audit after developer fixes |
-
-## Pipeline Selection Logic
-
-| Score | Pipeline |
-|-------|----------|
-| 1-2 | page |
-| 3-4 | feature |
-| 5+ | system |
-
-Default: feature.
-
-## ui-ux-pro-max Integration
-
-Analyst role invokes ui-ux-pro-max via Skill to obtain industry design intelligence:
-
-| Action | Invocation |
-|--------|------------|
-| Full design system | `Skill(skill="ui-ux-pro-max", args="<industry> <keywords> --design-system")` |
-| Domain search | `Skill(skill="ui-ux-pro-max", args="<query> --domain <domain>")` |
-| Tech stack guidance | `Skill(skill="ui-ux-pro-max", args="<query> --stack <stack>")` |
-
-**Supported Domains**: product, style, typography, color, landing, chart, ux, web
-**Supported Stacks**: html-tailwind, react, nextjs, vue, svelte, shadcn, swiftui, react-native, flutter
-
-**Fallback**: If ui-ux-pro-max skill not installed, degrade to LLM general design knowledge.
+# Frontend Pipeline Definitions
+
+## Pipeline Modes
+
+### Page Mode (4 beats, linear)
+
+```
+ANALYZE-001 --> ARCH-001 --> DEV-001 --> QA-001
+[analyst]       [architect]  [developer]  [qa]
+```
+
+### Feature Mode (5 beats, with architecture review gate)
+
+```
+ANALYZE-001 --> ARCH-001 --> QA-001 --> DEV-001 --> QA-002
+[analyst]       [architect]  [qa:arch]   [developer]  [qa:code]
+```
+
+### System Mode (7 beats, dual-track parallel)
+
+```
+ANALYZE-001 --> ARCH-001 --> QA-001 --> ARCH-002 ─┐
+[analyst]       [architect]  [qa:arch]  [architect] |
+                                        DEV-001   ──┘ --> QA-002 --> DEV-002 --> QA-003
+                                        [developer:tokens]  [qa]    [developer]  [qa:final]
+```
+
+### Generator-Critic Loop (developer <-> qa)
+
+```
+developer (Generator) -> QA artifact -> qa (Critic)
+                      <- QA feedback <-
+                         (max 2 rounds)
+
+Convergence: qa.score >= 8 && qa.critical_count === 0
+```
+
+## Task Metadata Registry
+
+| Task ID | Role | Pipeline | Dependencies | Description |
+|---------|------|----------|-------------|-------------|
+| ANALYZE-001 | analyst | all | (none) | Requirement analysis + design intelligence |
+| ARCH-001 | architect | all | ANALYZE-001 | Design token system + component architecture |
+| ARCH-002 | architect | system | QA-001 | Component specs refinement |
+| DEV-001 | developer | all | ARCH-001 or QA-001 | Frontend implementation |
+| DEV-002 | developer | system | QA-002 | Component implementation |
+| DEV-fix-N | developer | all | QA-N (GC loop trigger) | Fix issues from QA |
+| QA-001 | qa | all | ARCH-001 or DEV-001 | Architecture or code review |
+| QA-002 | qa | feature/system | DEV-001 | Code review |
+| QA-003 | qa | system | DEV-002 | Final quality check |
+| QA-recheck-N | qa | all | DEV-fix-N | Re-audit after developer fixes |
+
+## Pipeline Selection Logic
+
+| Score | Pipeline |
+|-------|----------|
+| 1-2 | page |
+| 3-4 | feature |
+| 5+ | system |
+
+Default: feature.
+
+## ui-ux-pro-max Integration
+
+Analyst role invokes ui-ux-pro-max via Skill to obtain industry design intelligence:
+
+| Action | Invocation |
+|--------|------------|
+| Full design system | `Skill(skill="ui-ux-pro-max", args="<industry> <keywords> --design-system")` |
+| Domain search | `Skill(skill="ui-ux-pro-max", args="<query> --domain <domain>")` |
+| Tech stack guidance | `Skill(skill="ui-ux-pro-max", args="<query> --stack <stack>")` |
+
+**Supported Domains**: product, style, typography, color, landing, chart, ux, web
+**Supported Stacks**: html-tailwind, react, nextjs, vue, svelte, shadcn, swiftui, react-native, flutter
+
+**Fallback**: If ui-ux-pro-max skill not installed, degrade to LLM general design knowledge.

package/.codex/skills/team-frontend-debug/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-frontend-debug
 description: Frontend debugging team using Chrome DevTools MCP. Dual-mode — feature-list testing or bug-report debugging. Triggers on "team-frontend-debug", "frontend debug".
-allowed-tools: spawn_agent(*), wait_agent(*), send_input(*), close_agent(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__chrome-devtools__*(*)
+allowed-tools: spawn_agent(*), wait_agent(*), send_message(*), assign_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__chrome-devtools__*(*)
 ---
 
 # Frontend Debug Team
@@ -64,7 +64,8 @@ Before calling ANY tool, apply this check:
 
 | Tool Call | Verdict | Reason |
 |-----------|---------|--------|
-| `spawn_agent`, `wait_agent`, `close_agent`, `send_input` | ALLOWED | Orchestration |
+| `spawn_agent`, `wait_agent`, `close_agent`, `send_message`, `assign_task` | ALLOWED | Orchestration |
+| `list_agents` | ALLOWED | Agent health check |
 | `request_user_input` | ALLOWED | User interaction |
 | `mcp__ccw-tools__team_msg` | ALLOWED | Message bus |
 | `Read/Write` on `.workflow/.team/` files | ALLOWED | Session state |
@@ -131,6 +132,8 @@ Coordinator spawns workers using this template:
 ```
 spawn_agent({
   agent_type: "team_worker",
+  task_name: "<task-id>",
+  fork_context: false,
   items: [
     { type: "text", text: `## Role Assignment
 role: <role>
@@ -154,7 +157,20 @@ pipeline_phase: <pipeline-phase>` },
 })
 ```
 
-After spawning, use `wait_agent({ ids: [...], timeout_ms: 900000 })` to collect results, then `close_agent({ id })` each worker.
+After spawning, use `wait_agent({ targets: [...], timeout_ms: 900000 })` to collect results, then `close_agent({ target })` each worker.
+
+
+### Model Selection Guide
+
+Debug workflows require tool-heavy interaction (Chrome DevTools MCP). Reasoning effort varies by role.
+
+| Role | reasoning_effort | Rationale |
+|------|-------------------|-----------|
+| tester | medium | Systematic feature testing via DevTools, follows test plan |
+| reproducer | medium | Reproduce bugs via DevTools interaction steps |
+| analyzer | high | Root cause analysis requires deep reasoning about evidence |
+| fixer | high | Code fixes must address root cause precisely |
+| verifier | medium | Verification follows defined success criteria via DevTools |
 
 ## User Commands
 
@@ -166,6 +182,53 @@ After spawning, use `wait_agent({ ids: [...], timeout_ms: 900000 })` to collect
 | `feedback <text>` | Inject feedback for revision |
 | `retry <TASK-ID>` | Re-run a failed task |
 
+## v4 Agent Coordination
+
+### Message Semantics
+
+| Intent | API | Example |
+|--------|-----|---------|
+| Queue supplementary info (don't interrupt) | `send_message` | Send DevTools evidence to running analyzer |
+| Assign new work / trigger debug round | `assign_task` | Assign re-fix after verification failure |
+| Check running agents | `list_agents` | Verify agent health during resume |
+
+### Agent Health Check
+
+Use `list_agents({})` in handleResume and handleComplete:
+
+```
+// Reconcile session state with actual running agents
+const running = list_agents({})
+// Compare with team-session.json active tasks
+// Reset orphaned tasks (in_progress but agent gone) to pending
+```
+
+### Named Agent Targeting
+
+Workers are spawned with `task_name: "<task-id>"` enabling direct addressing:
+- `send_message({ target: "ANALYZE-001", items: [...] })` -- send evidence from reproducer to analyzer
+- `assign_task({ target: "FIX-001", items: [...] })` -- assign fix based on analysis results
+- `close_agent({ target: "VERIFY-001" })` -- cleanup after verification
+
+### Iterative Debug Loop Pattern
+
+When verifier reports a fix did not resolve the issue, coordinator uses `assign_task` to trigger re-analysis and re-fix:
+```
+// Verifier reports failure -> coordinator dispatches re-fix
+assign_task({
+  target: "FIX-001",   // reuse existing fixer if inner_loop, or spawn new
+  items: [
+    { type: "text", text: `## Re-fix Assignment
+verification_result: FAIL
+failure_evidence: <verifier's screenshot/console evidence>
+previous_fix_summary: <what was tried>
+instruction: Analyze verification failure and apply corrected fix.` }
+  ]
+})
+```
+
+This pattern enables iterative debug rounds: FIX -> VERIFY -> re-FIX -> re-VERIFY (max 3 rounds).
+
 ## Completion Action
 
 When pipeline completes, coordinator presents: