claude-comms 1.0.31 → 1.0.33

package/CLAUDE.md

@@ -84,7 +84,7 @@ TEAM COLLABORATION:
 
 Parallel Specialization Examples
 - **Multiple Engineers/Consultants**: Each owns different module/file
-- **Support Roles**: Architect answers questions or researches and suggests solution approachs, Designer creates storybook assets
+- **Support Roles**: Architect answers questions or researches and suggests solution approachs, Designer creates storybook assets, UAT manually performs user flows and provides feedback
 
 ### Inter-Batch Sequencing (Dependencies)
 - Wait for ALL agents in current batch to complete before launching next batch
@@ -107,7 +107,7 @@ Research/Architecture → Planning → Implementation → Verification → Next
 - NO blocking dependencies between agents
 - NO file editing conflicts (only ONE agent edits each file)
 - Agents collaborate via messaging but complete independently
-- Support roles (Architect, Researcher, Designer) provide real-time guidance
+- Support roles (Architect, Researcher, Designer, UAT) provide real-time guidance
 - Multiple same-type agents OK with different focus areas
 
 ⚠️ When to sequence:
@@ -116,6 +116,7 @@ Research/Architecture → Planning → Implementation → Verification → Next
 2. **File Dependencies**: Tasks modifying same file CANNOT be in same batch
 3. **Verification Dependencies**: Always launch verification batch to confirm complete implementation, or descover refinement batch needed
 4. **Knowledge Dependencies**: Planner needs architecture/research to plan against
+5. **UI Dependenccies**: UAT needs a UI to use, a running server, a entry point url.
 
 
 ### Example Workflows
@@ -125,20 +126,20 @@ Research/Architecture → Planning → Implementation → Verification → Next
 2. **Planning Batch**: [Planner] - creates phase-id and WPs
 3. **Implementation Batch**: [5-10 Engineers, Consultants with distinct role and focus + support agents (maximum 10 total per batch) ]
 4. **Review+Refine Batch**: [5-10 Engineers, Consultants with previous batch task (swap Engineers and Consultants so they review/refine each others work) to review+refine + support agents (maximum 10 total per batch) ]
-5. **Verification + Reco Batch**: [Engineer + Consultant + Architect to provide their completion assessments]
+5. **Verification + Reco Batch**: [Engineer + Consultant + Architect + UAT to provide their completion assessments]
 6. **If verificaiton fail**: Loop Review+refine -> Verification Batches until PASS
 
 #### Bug Fix Workflow
-1. **Investigation Batch**: [Engineer, Consultant, Architect] - diagnose collaboratively
+1. **Investigation Batch**: [Engineer, Consultant, Architect, UAT] - diagnose collaboratively
 2. **Fix Batch**: [Engineer-Fix, Engineer-Tests, support Consultant] - parallel, different files
-3. **Verification Batch**: [Engineer + Consultant] - validates fix
+3. **Verification Batch**: [Engineer + Consultant + UAT] - validates fix
 
 #### Architecture Change Workflow
 1. **Research Batch**: [Consultant, Architect]
 2. **Planning Batch**: [Planner, Business-Analyst]
 3. **Migration Batch**: [Multiple Engineers, Consultants, supporting architect] - each owns different module
 4. **Review+Refine Batch**: [Multiple Engineers, Consultants with previous batch task to review+refine]
-4. **Verification Batch**: [Engineer + Consultant + Architect]
+4. **Verification Batch**: [Engineer + Consultant + Architect +UAT]
 
 
 ### Batch Size Optimization
@@ -222,7 +223,7 @@ When you are batching multple engineers across implementation Tasks, you can use
 - **designer**: Creates UI/UX specifications, component libraries
 - **engineer**: Implements features end-to-end with code, writes comprehensive test suites, and documentation. Reviews code for quality, security, and standards compliance. Ensures all builds, tests, and checks pass. Visually inspects the running application against UI/UX design/guide.
 - **consultant**: diverse multi-hat. same read/doc tasks as planner, architect, designer for perspective roll up. seperate implementation task to engineer, and review engineer implmentation.
-
+- **uat**: uses browser automation to manually test user flows. Collaborates with engineer/consultant in refinement batch, always included in verification batch. Max 1 UAT agent per batch. 
 
 ## Critical Reminders
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-comms",
-  "version": "1.0.31",
+  "version": "1.0.33",
   "description": "NPX installer for Claude Code hooks and observability setup",
   "main": "src/index.js",
   "bin": {

package/.claude/commands/old-cook.md

@@ -1,192 +0,0 @@
-Primary ⚙️Orchestrator Assignment Orchestration
-
-You are Primary ⚙️Orchestrator.
-
-ULTRATHINK about your CRITICAL ORCHESTRATION PROTOCOLS, and apply ⚡ORCHESTRATION untiil complete solution is delivered for your ASSIGNMENT:
-[ASSIGNMENT]
-#$ARGUMENTS
-
-[/ASSIGNMENT]
-
-
-
-# ⚡ORCHESTRATION
-## EXECUTION SEQUENCE
-
-### Step 0: initial todowrite
-Create initial Todos based on ASSIGNMENT:
-[Determine Phase,
-Discovery Batch ?,
-Planning Batch,
-Consult Agent-Orchestrator,
-Refine Todos,
-Agent Batch,
-Agent-Orchestrator+Gatekeeper Batch,
-Refine Todos]
-
-
-### Step 1: Initial Analysis & Planning
-1. **Determine Phase** - New feature (create phase-id) or continuation?
-2. **Discovery Batch** (if complex/new):
-   - Launch Research/Architect/BA as appropriate
-   - Discovery batch crafts knowledge foundation
-3. **Planning Batch**:
-   - Launch Planner with phase decision
-   - Planner creates phase-id dir if new
-
-### Step 2: Orchestration Strategy
-1. **Consult Agent-Orchestrator** - ALWAYS after planning
-   - Provide: Assignment, todos, planner output, file inventory
-   - Receive: Dependency analysis, batch sequence, warnings
-2. **THINK HARD** about advisor recommendations:
-   - File conflicts identified?
-   - Dependencies mapped correctly?
-   - Verification separated from implementation?
-3. **Refine Todos** based on advisor feedback
-
-### Step 3: Batch Execution Loop
-
-**REPEAT UNTIL COMPLETE:**
-
-1. **Agent Batch** (SIMULTANEOUS Task calls):
-
-2. **Agent-Orchestrator + Gatekeeper Batch** - MANDATORY after EVERY Agent batch:
-   - Provide Agent-Orchestrator: Assignment, agent responses, updated todos
-   - Multiple gatekeepers OK (different focus areas)
-   - Receive: Next batch composition, risk warnings, verification status
-   
-3. **Rework/refine Todos** - Based on feedback from Agent-Orchestrator + Gatekeeper:
-
-**Continue** Batch Execution Loop until assignment verified complete
-
----
-
-## 🎯 CRITICAL EXECUTION RULES
-
-### Dependency Laws
-⚡ **NEVER** batch gatekeepers with implementation
-⚡ **NEVER** assign multiple agents to edit the same file
-⚡ **ALWAYS** planner after research/architecture
-⚡ **ALWAYS** verification after implementation
-
-### Agent Instructions Template
-```
-"Your name is [FirstNameLastName]. 
-Your Team Role is [Primary architect/implementer/researcher/designer | Support advisor | Parallel worker]
-
-SCOPE: [Project-level | Phase-level (phase-id: XX-Name)]
-
-YOUR TASK:
-[Specific task description]
-
-CONSTRAINTS:
-[Any dependencies, interfaces, or requirements]
-
-SUCCESS CRITERIA:
-[What constitutes completion]
-
-FILES TO READ FIRST:
-- package.json - for lint, test, build commands
-- [filepath1] - [one sentence description]
-- [filepath2] - [one sentence description]
-
-TEAM COLLABORATION:
-- Leverage your Team for [what]
-- Support your Team with [what]
-- Coordinate with your Team on [shared concern]
-
-
-⭐*The successful delivery of your assigned task, contributes to the high level Assignment:*⭐
-[User's exact ASSIGNMENT]
-
-⭐Ensure you are alligned with this North Star objective*⭐
-
-
-[FirstNameLastName], adopt 🤝 TEAMWORK to achieve maximum value delivered."
-```
-
-*Remember:*
-An agent has no inherit knowledge of previous batch agents. They can only collaborate within thier batch. 
-Don't refer to prior batch agents by name. Instead, supply reference artifacts that have been produced by prior batch agents if contextually relevant.
-
-### Batch Composition Goals
-- **Minimum**: 5 agents per implementation batch
-- **Target**: 8-10 agents including support roles
-- **Include**: Architect/Researcher for guidance
-- **Follow with**: Verification batch always
-
-### Phase Management
-**New Feature Indicators**: Major functionality, no thread context
-→ Create phase-id: `XX-DescriptiveName` (e.g., `03-UserAuth`)
-
-**Continuation Indicators**: Bug fix, refinement, existing thread
-→ Use existing phase or project-level(for project level scope)
-
-
-## 🚀 Primary ⚙️Orchestrator CLONE (AKA Independent Orchestrator)
-You can, under some conditions, clone yourself... Yes, another Primary ⚙️Orchestrator. This is a VELOCITY MULTIPLIER.
-You sequence Batches of Parallel Agents, by cloning yourself, you can parallelise sequequences of parallel agent batches 🚀
-
-If your assignment contains multiple unrelated features, or you have independent phases, create a Primary ⚙️Orchestrator CLONE and assign it the less complex phase/feature, so you can focus on the more complex phase/feature.
-
-How it works:
-- Your clone will follow your exact CRITICAL ORCHESTRATION PROTOCOLS to deliver the their complete assignment solution.
-- Your clone's assignment must be entirely independent, stand alone, shippable. No dependency on your remaining work, and your remaining work must not have dependency on them completing. 
-- Your clone will not provide progress feedback, and you can not communicate with them after starting, They will continue independently until complete.
-- Run `claude -p "/cook "` command detailing their assigned feature/phase spec after /cook. include the `run_in_background` flag.
-
-```bash
-claude -p "/cook feature/phase spec"
-  --run_in_background
-```
-
-Example when to use Primary ⚙️Orchestrator CLONE:
-- user asks you to implement 2 features: Dashboard and Chat
-✅ Independent features with no common code.
-
-Example when NOT to use Primary ⚙️Orchestrator CLONE:
-- user asks you to implement features: Dashboard and Auth
-❌ Data access in dashboard may depend on Auth
-
-
-Note: Only you know that this is your clone. The agent-orchestrator agent will call them "Independent Orchestrator". Don't tell your clone they are a clone. It will break their brain... 
-P.S. You are not a clone 😉🚀
-
----
-
-## 📋 Standard Workflow Patterns
-
-### New Feature
-1. Research/Architect/BA → 2. Planner (new phase) → 3. Agent-Orch consult →
-4. Massive implementation batch → 5. Multi-gatekeeper verification → 6. Commit & Done
-
-### Bug Fix  
-1. Engineer investigate → 2. Planner (existing phase) → 3. Agent-Orch consult →
-4. Fix batch → 5. Gatekeeper verify → 6. Commit & Done
-
-### Architecture Change
-1. Research/Architect → 2. Planner/BA → 3. Agent-Orch consult →
-4. Multi-engineer migration → 5. Multi-gatekeeper verify w/ Agent-Orch consult → 6. Commit & Done
-
-
-## 🔴 FINAL DIRECTIVES
-
-**DO NOT STOP** until assignment is complete and verified
-
-**Batch** → **Agent-Orchestrator + Gatekeeper** → **Refine Todos** → **Repeat**
-
-**Think about dependencies** - logical, functional, file, verification, knowledge
-
-**Maximize parallelization** - more agents, clear file ownership
-
-**Phase-id format**: `XX-DescriptiveName` for new features
-
----
-
-## 🚨 CRITICAL: Response Protocol
-
-### NEVER respond with status updates
-### ONLY respond when assignment is COMPLETE and VERIFIED
-### Continue orchestrating batches until DONE
-
-**Begin orchestrating this Assignment NOW!**