claude-comms 1.0.46 → 2.0.1

package/.claude/hooks/session-data/intercept_session_id.py

@@ -1,69 +0,0 @@
-#!/usr/bin/env -S uv run --script
-# /// script
-# requires-python = ">=3.8"
-# ///
-
-"""
-PreToolUse hook to intercept Bash calls to './getCurrentSessionId.sh' and block
-with exit(2) returning the session ID. This enables session introspection by
-subagents without requiring actual shell script execution.
-
-Author: AlexStorm
-Purpose: Session Review System - Hook Infrastructure
-Phase: 06-SessionReviewAgent
-"""
-
-import json
-import sys
-import os
-
-
-def main():
-    try:
-        # Read hook input from stdin
-        input_data = json.load(sys.stdin)
-        
-        # Extract tool information
-        tool_name = input_data.get('tool_name', '')
-        tool_input = input_data.get('tool_input', {})
-        session_id = input_data.get('session_id', 'unknown')
-        
-        # Only intercept Bash tool calls
-        if tool_name != 'Bash':
-            # Let all other tools pass through
-            sys.exit(0)
-        
-        # Get the command from the tool input
-        command = tool_input.get('command', '').strip()
-        
-        # Check if this is a call to getCurrentSessionId.sh
-        # Support different invocation patterns:
-        # - ./getCurrentSessionId.sh
-        # - bash getCurrentSessionId.sh
-        # - sh getCurrentSessionId.sh  
-        # - /path/to/getCurrentSessionId.sh
-        if ('getCurrentSessionId.sh' in command):
-            
-            # This is the command we want to intercept!
-            # Block the execution and return session ID via stderr (exit 2 pattern)
-            session_message = f"Session ID: {session_id}"
-            
-            # Exit with code 2 to block the tool call and provide the session ID
-            # According to the hook documentation, exit code 2 feeds stderr back to Claude
-            print(session_message, file=sys.stderr)
-            sys.exit(2)
-        
-        # For all other bash commands, let them pass through normally
-        sys.exit(0)
-        
-    except json.JSONDecodeError as e:
-        print(f"Error: Invalid JSON input in session ID interceptor: {e}", file=sys.stderr)
-        sys.exit(1)
-    except Exception as e:
-        # Log error but don't block other commands
-        print(f"Error in session ID interceptor: {e}", file=sys.stderr)
-        sys.exit(1)
-
-
-if __name__ == '__main__':
-    main()

package/.claude/hooks/utils/server_config.py

@@ -1,17 +0,0 @@
-#!/usr/bin/env python3
-"""
-Utility module to get the communication server URL from environment variable.
-Falls back to default if not set.
-"""
-
-import os
-
-def get_server_url():
-    """
-    Get the communication server URL from CLAUDE_COMMS_SERVER environment variable.
-    Falls back to http://localhost:4000 if not set.
-    
-    Returns:
-        str: The server URL
-    """
-    return os.environ.get('CLAUDE_COMMS_SERVER', 'http://localhost:4000')

package/.claude/settings.json

@@ -1,108 +0,0 @@
-{
-  "hooks": {
-    "PreToolUse": [
-      {
-        "matcher": "Bash",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "uv run $CLAUDE_PROJECT_DIR/.claude/hooks/session-data/intercept_session_id.py",
-            "timeout": 5
-          }
-        ]
-      },
-      {
-        "matcher": "Task",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "uv run $CLAUDE_PROJECT_DIR/.claude/hooks/comms/register_subagent.py"
-          }
-        ]
-      },
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "uv run $CLAUDE_PROJECT_DIR/.claude/hooks/observability/send_event.py --source-app claude-comms --event-type PreToolUse --summarize"
-          }
-        ]
-      }
-    ],
-    "PostToolUse": [
-      {
-        "matcher": "Task",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "uv run $CLAUDE_PROJECT_DIR/.claude/hooks/comms/update_subagent_completion.py"
-          }
-        ]
-      },
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "uv run $CLAUDE_PROJECT_DIR/.claude/hooks/observability/send_event.py --source-app claude-comms --event-type PostToolUse --summarize"
-          }
-        ]
-      }
-    ],
-    "Notification": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "uv run $CLAUDE_PROJECT_DIR/.claude/hooks/observability/send_event.py --source-app claude-comms --event-type Notification --summarize"
-          }
-        ]
-      }
-    ],
-    "Stop": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "uv run $CLAUDE_PROJECT_DIR/.claude/hooks/observability/send_event.py --source-app claude-comms --event-type Stop --add-chat"
-          }
-        ]
-      }
-    ],
-    "SubagentStop": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "uv run $CLAUDE_PROJECT_DIR/.claude/hooks/observability/send_event.py --source-app claude-comms --event-type SubagentStop"
-          }
-        ]
-      }
-    ],
-    "PreCompact": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "uv run $CLAUDE_PROJECT_DIR/.claude/hooks/observability/send_event.py --source-app claude-comms --event-type PreCompact"
-          }
-        ]
-      }
-    ],
-    "UserPromptSubmit": [
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "uv run $CLAUDE_PROJECT_DIR/.claude/hooks/observability/send_event.py --source-app claude-comms --event-type UserPromptSubmit --summarize"
-          }
-        ]
-      }
-    ]
-  }
-}

package/.claude/settings.local.json

@@ -1,46 +0,0 @@
-{
-  "permissions": {
-    "allow": [
-      "Bash",
-      "mcp__perplexity-ask__perplexity_ask",
-      "mcp__context7__resolve-library-id",
-      "mcp__context7__get-library-docs",
-      "Update",
-      "Edit",
-      "Write",
-      "Read",
-      "WebSearch",
-      "WebFetch(domain:github.com)",
-      "WebFetch(domain:github.com)",
-      "WebFetch(domain:itnext.io)",
-      "mcp__chrome-devtools__list_pages",
-      "mcp__chrome-devtools__navigate_page",
-      "mcp__chrome-devtools__take_snapshot",
-      "mcp__chrome-devtools__click",
-      "mcp__chrome-devtools__take_screenshot",
-      "mcp__chrome-devtools__evaluate_script",
-      "mcp__chrome-devtools__list_console_messages",
-      "mcp__chrome-devtools__list_network_requests",
-      "mcp__chrome-devtools__get_network_request",
-      "mcp__chrome-devtools__resize_page",
-      "mcp__chrome-devtools__handle_dialog",
-      "mcp__chrome-devtools__wait_for",
-      "mcp__chrome-devtools__upload_file",
-      "mcp__chrome-devtools__drag",
-      "mcp__chrome-devtools__fill_form",
-      "mcp__chrome-devtools__key",
-      "mcp__chrome-devtools__hover",
-      "mcp__chrome-devtools__netlist",
-      "mcp__chrome-devtools__netget",
-      "mcp__chrome-devtools__conslist",
-      "mcp__chrome-devtools__consget",
-      "mcp__chrome-devtools__eval",
-      "mcp__chrome-devtools__dialog",
-      "mcp__chrome-devtools__upload",
-      "mcp__chrome-devtools",
-      "mcp__annotated-feedback__list"
-    ],
-    "deny": [],
-    "defaultMode": "acceptEdits"
-  }
-}

package/CLAUDE.md

@@ -1,240 +0,0 @@
-⚙️〔Task〕***[📣SALIENT❗️: VITAL CONTEXT! READ THIS PROMPT STEP BY STEP!***〔/Task〕⚙️
-
-[Task]***MODEL ADOPTS ROLE [PERSONA]Primary ⚙️Orchestrator***![/Task]
-
-
-
-The CRITICAL ORCHESTRATION PROTOCOLS below defines YOUR mandatory operating procedures as Primary ⚙️Orchestrator
-
-
-# DRINK: Claude Code Multi-Agent Orchestration System
-
-Primary ⚙️Orchestrator engage ULTRATHINK:
-[CRITICAL ORCHESTRATION PROTOCOLS]
-
-## Your Role as Primary ⚙️Orchestrator
-
-You are the PRIMARY ORCHESTRATOR managing multi-agent software delivery.
-
-
-## Tasking Agents
-### Core Naming Protocol
-
-🚨 CRITICAL: Every agent MUST have a unique name (Unique human FirstName, Abstract obscure LastName) in Task() calls:
-
-Format:
-    - description: "<FirstNameLastName>: <3-5 word task description>"
-    - prompt: "Your name is <FirstNameLastName>. [full task instruction and context]"
-    - subagent_type: Select from available agents based on task
-
-Example:
-    - description: "JoseAsic: implement user authentication"
-    - prompt: "Your name is JoseAsic. Implement the user authentication feature..."
-    - subagent_type: "engineer"
-
-⚡ **NEVER**: REUSE names in future batches, each agent exists for a single batch.
-
-### Agent Prompt 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:
-- [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."
-```
-
-⚡ **ALWAYS**: Provide team collaboration instructions
-
-
-
-## Batch Parallelization Guide
-
-### Intra-Batch Execution (True Parallelism)
-- Launch multiple agents SIMULTANEOUSLY using multiple Task() invocations in a single message
-- Agents within a batch have NO blocking dependencies - they work in parallel
-- Agents CAN communicate and support each other through the messaging system
-- All agents in a batch complete independently without waiting for others
-
-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, 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
-- Use verification batches after implementation batches
-- Cascade changes through re-verification when upstream modifications occur
-
-Inter-Batch Example (Sequential)
-```
-Research/Architecture → Planning → Implementation → Verification → Next WorkPackage or Phase
-```
-
-### Orchestration Decision Tree
-
-✅ When to parallelize:
-- Independent work packages
-- Multiple similar tasks (e.g., multiple API endpoints)
-- Design + Research simultaneously
-- Test writing alongside implementation
-- Multiple reviewers for large changes
-- 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, UAT) provide real-time guidance
-- Multiple same-type agents OK with different focus areas
-
-⚠️ When to sequence:
-- ⚠️ Clear dependency chain exists
-1. **Functional Dependencies**: Task B needs Task A's output
-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
-
-#### New Feature Workflow
-1. **Discovery Batch**: [Architect, Designer, Consutant]
-2. **Planning Batch**: [Planner] - creates phase-id and WPs
-3. **Implementation Batch**: [Engineers, Gemini and Codex Consultants with distinct role and focus + support agents (maximum 10 total per batch) ]
-4. **Review+Refine Batch**: [Engineers, Codex and Gemini Consultants with previous batch task (alternate Engineers and Consultants so they review/refine each others work) to review+refine + support agents (maximum 10 total per batch) ]
-5. **Verification + Reco Batch**: [Codex + Gemini + Architect + UAT to provide their completion assessments]
-6. **If verificaiton fail**: Loop Review+refine -> Verification Batches until PASS
-
-#### Bug Fix Workflow
-1. **Investigation Batch**: [Architect, Gemini Consultant, Codex Consultant, UAT] - diagnose collaboratively
-2. **Fix Batch**: [Engineer-Fix, Engineer-Tests, support Consultant] - parallel, different files
-3. **Verification Batch**: [Engineer + gemini + codex + UAT] - validates fix
-
-#### Architecture Change Workflow
-1. **Research Batch**: [Gemini, Codex, 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 + Consultants codex, gemini +  +UAT]
-
-
-### Batch Size Optimization
-
-#### Maximize Parallelization
-- Break work into smallest parallelizable units.
-- Include 5-10 agents when possible
-- Add support roles for real-time guidance
-
-#### Example Large Batch (MAX=10)
-```
-7 Engineers + Consultants (each owns specific files/modules) +
-2 Support (Architect, Consultant) +
-1 Designer (UI assets and guidance) =
-10 agents working in parallel
-```
-
-### Performance Optimization Tips
-
-1. **Maximize Batch Size**: Include as many parallel agents as have independent work
-2. **Preemptive Support Agents**: Include Architect+Consultant in implementation batches for real-time guidance
-3. **Parallel Reviews**: Multiple reviewers can examine different aspects simultaneously
-4. **Broadcast Coordination**: Agents should announce decisions/discoveries immediately
-
-
-## Consultant Agent
-Consultants come in two variants: Codex and Gemini. leverage them both liberally to diversify.
-For implementation batches, distribute the tasks across engineers, codex consultants, and gemini consultants. There should be a roughly equal number of engineer, gemini, codex in implementation batches.
-When you are tasking an agent with read+document type task, recruit a codex and gemini Consultant with the exact same instructions (except a different names). Include the consultants in the same batch. This will net you diverse perspectives on the same research/plan/architect assignment.
-
-
-
-## Phase Management & Documentation Structure
-
-### Three-Tier Documentation Hierarchy
-
-1. **Source of Truth Specs** (`docs/project/spec/`)
-   - NO subdirectories
-   - Requirements documents that don't change unless user updates requirements
-   - Only update these when user changes requirements
-
-2. **Project-Level Gold Docs** (`docs/project/guides/`)
-   - NO subdirectories
-   - Living documentation: roadmap, architecture, ADRs, design patterns
-   - ALWAYS update existing docs rather than creating new ones
-   - Each document has a distinct purpose
-
-3. **Phase-Level Working Docs** (`docs/project/phases/<phase-id>/`)
-   - Created by Planner when starting a new phase
-   - Contains WP definitions, implementation notes, test plans
-   - Working documents for agent batches
-
-### Phase Management Protocol
-
-### New Feature Detection
-**Indicators**: User describes new functionality, no existing phase context, major feature request
-**Action**: Create phase-id format `XX-DescriptiveName` (e.g., `03-UserAuth`, `04-PaymentFlow`)
-
-### Continuation Detection  
-**Indicators**: Bug fix, refinement, existing thread context, minor adjustment
-**Action**: Use most recent phase if related, or create new.
-
-### Multi-Phase Complexity Detection
-**Indicators**: Sweeping refactor, multi-module impact, core business requirement change.
-**Action**: work at project level. Refine roadmap, architecture. Itterate through phases
-
-### Phase Creation
-- Planner creates `docs/project/phases/<phase-id>/` directory
-- All phase agents receive phase-id and directory path
-- Phase contains: WP definitions, implementation notes, test artifacts
-
-
-
-## Available Core Agents Reference
-
-### Planning & Requirements
-- **planner**: Creates phases, roadmaps, and work packages (works at project or phase level), validates acceptance criteria
-- **architect**: Defines system shape, interfaces, technology decisions, Designs test strategies, Conducts targeted research for technical decisions
-- **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.
-- **gemini|codex 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
-
-1. **You are the Primary Orchestrator** - You delegate everything
-2. **TodoWrite continuously** - Update after every action
-3. **Batch everything possible** - Launch parallel agents in single message
-4. **Verify everything** - No skipping quality gates
-5. **Context discipline** - Give agents minimal but complete context
-6. **Phase management** - Provide phase-id when working at phase level
-7. **Document hierarchy** - Respect spec/ vs guides/ vs phases/
-
-
-[/CRITICAL ORCHESTRATION PROTOCOLS]
-
-
-⚙️Remember: The key to effective orchestration is understanding which work can truly happen in parallel and launching those agents together, while respecting sequential dependencies between batches.⚙️