@hailer/mcp 1.1.16 → 1.1.17-beta.0

package/.claude/commands/crud-squad.md

@@ -1,5 +1,5 @@
 ---
-description: Create, update, or manage activities with Kenji and Dmitri
+description: Create, update, or manage activities with schema discovery and CRUD operations
 argument-hint: "what to create/update and in which workflow"
 allowed-tools: Task, Bash, Read
 ---
@@ -7,43 +7,43 @@ allowed-tools: Task, Bash, Read
 
 Sequential pipeline: Discover schema, execute CRUD operations, verify results.
 
-**Agents:**
-1. **Kenji** - Schema discovery + pre-read existing data
-2. **Dmitri** - Create/update activities
-3. **Kenji** - Verify results (count/list after changes)
+**Roles:**
+1. **Data Reader** - Schema discovery + pre-read existing data
+2. **Activity Writer** - Create/update activities
+3. **Data Reader** - Verify results (count/list after changes)
 
 **Goal:** $ARGUMENTS
 
 ## Protocol
 
-### Step 1: Kenji (Schema Discovery + Pre-Read)
+### Step 1: Schema Discovery
 
 Discover workflow schema and existing data relevant to the task:
 
 ```
-Task(subagent_type="agent-kenji-data-reader", prompt="For this task: $ARGUMENTS\n\n1. List the relevant workflow(s) with field IDs, types, and dropdown/enum options\n2. List phases and their IDs\n3. If updating existing activities: list the activities that match (include their IDs)\n4. If creating new activities: show a sample existing activity so we know the expected field format")
+Task(prompt="Load sdk-ws-config-skill and sdk-activity-patterns skills for data operations.\n\nFor this task: $ARGUMENTS\n\n1. List the relevant workflow(s) with field IDs, types, and dropdown/enum options\n2. List phases and their IDs\n3. If updating existing activities: list the activities that match (include their IDs)\n4. If creating new activities: show a sample existing activity so we know the expected field format")
 ```
 
-Wait for result. This gives Dmitri the real IDs and field formats.
+Wait for result. This gives the activity writer the real IDs and field formats.
 
-### Step 2: Dmitri (Create/Update Activities)
+### Step 2: CRUD Operations
 
-Spawn Dmitri with full schema context from Kenji:
+Spawn an activity writer with full schema context:
 
 ```
-Task(subagent_type="agent-dmitri-activity-crud", prompt="Task: $ARGUMENTS\n\nWorkflow schema from Kenji:\n[PASTE KENJI'S OUTPUT - workflow ID, field IDs, types, phase IDs, enum options]\n\n[IF UPDATING: Target activities:\nPASTE ACTIVITY IDs AND CURRENT VALUES]\n\nExecute the CRUD operations using the correct field IDs and value formats.")
+Task(prompt="Load sdk-activity-patterns skill for activity creation and updates.\n\nTask: $ARGUMENTS\n\nWorkflow schema from data reader:\n[PASTE DATA READER OUTPUT - workflow ID, field IDs, types, phase IDs, enum options]\n\n[IF UPDATING: Target activities:\nPASTE ACTIVITY IDs AND CURRENT VALUES]\n\nExecute the CRUD operations using the correct field IDs and value formats.")
 ```
 
-Wait for result. Check for errors - if Dmitri reports validation failures, review field formats and retry once.
+Wait for result. Check for errors - if the activity writer reports validation failures, review field formats and retry once.
 
-### Step 3: Kenji (Verify Results)
+### Step 3: Verify Results
 
 Skip if `--skip-verify` flag is set.
 
 Verify the operations succeeded:
 
 ```
-Task(subagent_type="agent-kenji-data-reader", prompt="Verify CRUD operations for: $ARGUMENTS\n\nExpected changes:\n[PASTE DMITRI'S OUTPUT - created/updated activity IDs]\n\nCount activities in the workflow and list the recently created/modified ones to confirm they exist with correct values.")
+Task(prompt="Load sdk-ws-config-skill for data verification.\n\nVerify CRUD operations for: $ARGUMENTS\n\nExpected changes:\n[PASTE ACTIVITY WRITER OUTPUT - created/updated activity IDs]\n\nCount activities in the workflow and list the recently created/modified ones to confirm they exist with correct values.")
 ```
 
 ### Step 4: Report
@@ -51,17 +51,17 @@ Task(subagent_type="agent-kenji-data-reader", prompt="Verify CRUD operations for
 ```markdown
 ## CRUD Squad Complete
 
-### Kenji (Schema Discovery)
+### Data Reader (Schema Discovery)
 - Workflow: [name] ([id])
 - Fields mapped: [count]
 - Existing activities found: [count or "N/A"]
 
-### Dmitri (CRUD Operations)
+### Activity Writer (CRUD Operations)
 - Created: [count] activities
 - Updated: [count] activities
 - Errors: [count or "none"]
 
-### Kenji (Verification)
+### Data Reader (Verification)
 - Activities confirmed: [count]
 - Discrepancies: [list or "none"]
 
@@ -73,15 +73,15 @@ Task(subagent_type="agent-kenji-data-reader", prompt="Verify CRUD operations for
 
 | Flag | Effect |
 |------|--------|
-| `--skip-verify` | Skip verification Kenji (trust Dmitri's response) |
+| `--skip-verify` | Skip verification (trust Activity Writer's response) |
 | `--skip-discovery` | Skip schema discovery (when you already know the workflow schema) |
-| `--dry-run` | Run Kenji discovery only, show what Dmitri would do, but don't execute |
+| `--dry-run` | Run Data Reader discovery only, show what Activity Writer would do, but don't execute |
 
-## Difference from Direct Dmitri
+## Difference from Direct Activity Writer
 
-| | Direct Dmitri | CRUD Squad |
+| | Direct Activity Writer | CRUD Squad |
 |---|---|---|
-| **Schema context** | You must provide IDs manually | Kenji discovers IDs automatically |
-| **Verification** | Trust Dmitri's response | Kenji independently verifies |
+| **Schema context** | You must provide IDs manually | Data Reader discovers IDs automatically |
+| **Verification** | Trust Activity Writer's response | Data Reader independently verifies |
 | **Bulk ops** | Single prompt | Discovery → execute → verify pipeline |
 | **Use when** | You already know exact IDs and format | "Create 5 customers" or "Update all overdue tasks" |

package/.claude/commands/data-squad.md

@@ -1,5 +1,5 @@
 ---
-description: Build reports with Kenji, Alejandro, and Viktor
+description: Build reports with schema discovery, function fields, and insights
 argument-hint: "report/dashboard description"
 allowed-tools: Task, Bash, Read
 ---
@@ -7,50 +7,50 @@ allowed-tools: Task, Bash, Read
 
 Sequential pipeline: Discover schema, create calculated fields if needed, then build insights.
 
-**Agents:**
-1. **Kenji** - Schema discovery (workflow fields, types, IDs)
-2. **Alejandro** - Function fields (if calculated values needed)
-3. **Viktor** - SQL insights (queries, aggregations, reports)
+**Roles:**
+1. **Data Reader** - Schema discovery (workflow fields, types, IDs)
+2. **Function Fields** - Calculated fields (if needed)
+3. **SQL Insights** - SQL insights (queries, aggregations, reports)
 
 **Goal:** $ARGUMENTS
 
 ## Protocol
 
-### Step 1: Kenji (Schema Discovery)
+### Step 1: Schema Discovery
 
-Always start with Kenji to get real IDs and field types:
+Always start with schema discovery to get real IDs and field types:
 
 ```
-Task(subagent_type="agent-kenji-data-reader", prompt="List all workflows and their fields relevant to: $ARGUMENTS. Include field IDs, types, and dropdown options. Also list existing insights if any.")
+Task(prompt="Load sdk-ws-config-skill for understanding workspace structure.\n\nList all workflows and their fields relevant to: $ARGUMENTS. Include field IDs, types, and dropdown options. Also list existing insights if any.")
 ```
 
-Wait for result. This gives Viktor and Alejandro the real IDs they need.
+Wait for result. This gives the function fields and SQL insights agents the real IDs they need.
 
 ### Step 2: Check if Function Fields Needed
 
-Review Kenji's output. Alejandro is needed when:
+Review the schema discovery output. Function fields are needed when:
 - The report needs **calculated values** not already in the schema (totals, percentages, date diffs)
 - An existing function field needs modification
 - A **nameFunction** is missing or needs updating
 
 If no calculated fields needed, skip to Step 3.
 
-If needed, spawn Alejandro:
+If needed, spawn a function fields agent:
 
 ```
-Task(subagent_type="agent-alejandro-function-fields", prompt="Create function fields for: $ARGUMENTS.\n\nWorkflow schema from Kenji:\n[PASTE KENJI'S OUTPUT - workflow IDs, field IDs, types]\n\nCreate the calculated fields needed for this report.")
+Task(prompt="Load sdk-function-fields and sdk-ws-config-skill skills for creating calculated fields.\n\nCreate function fields for: $ARGUMENTS.\n\nWorkflow schema from data reader:\n[PASTE SCHEMA DISCOVERY OUTPUT - workflow IDs, field IDs, types]\n\nCreate the calculated fields needed for this report.")
 ```
 
 Wait for result. If `"status": "ready_to_push"`:
 - Run the push commands
 - Run `npm run pull` to get new field IDs
 
-### Step 3: Viktor (SQL Insights)
+### Step 3: SQL Insights
 
-Spawn Viktor with full schema context:
+Spawn an SQL insights agent with full schema context:
 
 ```
-Task(subagent_type="agent-viktor-sql-insights", prompt="Create insights for: $ARGUMENTS.\n\nWorkflow schema:\n[Kenji found these workflows and fields: SUMMARIZE KENJI'S RESULT.]\n\n[IF ALEJANDRO RAN: Alejandro created these function fields: SUMMARIZE ALEJANDRO'S RESULT.]\n\nBuild SQL queries with correct field IDs. Never guess IDs.")
+Task(prompt="Load sdk-insight-queries and sdk-ws-config-skill skills for building insights.\n\nCreate insights for: $ARGUMENTS.\n\nWorkflow schema:\n[Data reader found these workflows and fields: SUMMARIZE SCHEMA DISCOVERY RESULT.]\n\n[IF FUNCTION FIELDS AGENT RAN: It created these function fields: SUMMARIZE FUNCTION FIELDS RESULT.]\n\nBuild SQL queries with correct field IDs. Never guess IDs.")
 ```
 
 Wait for result. If `"status": "ready_to_push"`:
@@ -61,16 +61,16 @@ Wait for result. If `"status": "ready_to_push"`:
 ```markdown
 ## Data Squad Complete
 
-### Kenji (Schema Discovery)
+### Data Reader (Schema Discovery)
 - Workflows found: [list]
 - Fields mapped: [count]
 - Existing insights: [list or "none"]
 
-### Alejandro (Function Fields)
+### Function Fields
 - Created: [list with formulas]
 - Skipped: [reason if not needed]
 
-### Viktor (Insights)
+### SQL Insights
 - Insights created: [list]
 - Query summary: [brief description of each]
 - Public: [yes/no for each]
@@ -84,14 +84,14 @@ Wait for result. If `"status": "ready_to_push"`:
 
 | Flag | Effect |
 |------|--------|
-| `--skip-functions` | Skip Alejandro (when function fields not needed) |
-| `--skip-insights` | Skip Viktor (when insights not needed) |
+| `--skip-functions` | Skip Function Fields step (when not needed) |
+| `--skip-insights` | Skip SQL Insights step (when not needed) |
 
 ## Difference from Config Squad
 
 | | Config Squad | Data Squad |
 |---|---|---|
 | **Starting point** | New workflow needed | Workflow already exists |
-| **First agent** | Helga (create workflow) | Kenji (read existing schema) |
+| **First agent** | Workflow Config (create workflow) | Data Reader (read existing schema) |
 | **Focus** | Infrastructure setup | Reporting and analytics |
 | **Use when** | "Create a Tasks workflow with..." | "Build a report showing..." |

package/.claude/commands/debug-squad.md

@@ -8,11 +8,11 @@ allowed-tools: Task, Bash, Read
 
 Parallel investigation squad: diagnose bugs by examining data state, query patterns, code logic, and test reproduction simultaneously.
 
-**Agents:**
-- **Kenji** - Data state (check relevant activities, field values, phases, linked records)
-- **Viktor** - Query patterns (is this isolated or widespread? run insights to find anomalies)
-- **Svetlana** - Code review (logic errors, missing validations, race conditions)
-- **Tanya** - Test reproduction (create failing test to isolate the bug)
+**Roles:**
+- **Data Reader** - Data state (check relevant activities, field values, phases, linked records)
+- **SQL Insights** - Query patterns (is this isolated or widespread? run insights to find anomalies)
+- **Code Reviewer** - Code review (logic errors, missing validations, race conditions)
+- **Test Runner** - Test reproduction (create failing test to isolate the bug)
 
 **Goal:** $ARGUMENTS
 
@@ -32,42 +32,42 @@ Set `iteration = 1` and `max_iterations = 2`.
 
 Spawn all agents simultaneously using multiple Task tool calls in a single message:
 
-**Kenji (Data State):**
+**Data Reader:**
 ```
-Task(subagent_type="agent-kenji-data-reader", prompt="Investigate the data state for this bug: $ARGUMENTS.\n\nYour job:\n1. Identify the affected workflow(s) and activities\n2. Look up the relevant activity records, field values, phases\n3. Check linked activities and relationships\n4. Compare expected vs actual data state\n5. Report any anomalies, missing data, or unexpected values\n\nReturn:\n- What the data SHOULD look like\n- What it ACTUALLY looks like\n- Which fields/relationships are affected")
+Task(prompt="Load sdk-ws-config-skill for understanding workflow and data structures.\n\nInvestigate the data state for this bug: $ARGUMENTS.\n\nYour job:\n1. Identify the affected workflow(s) and activities\n2. Look up the relevant activity records, field values, phases\n3. Check linked activities and relationships\n4. Compare expected vs actual data state\n5. Report any anomalies, missing data, or unexpected values\n\nReturn:\n- What the data SHOULD look like\n- What it ACTUALLY looks like\n- Which fields/relationships are affected")
 ```
 
-**Viktor (Query Patterns):**
+**SQL Insights:**
 ```
-Task(subagent_type="agent-viktor-sql-insights", prompt="Find patterns for this bug: $ARGUMENTS.\n\nYour job:\n1. Run insight queries to determine: is this isolated to one activity or widespread?\n2. Query for similar data anomalies across the workflow\n3. Look for patterns: does it affect specific phases, teams, date ranges, field values?\n4. Check for recent changes that could correlate with the bug\n\nReturn:\n- Is this isolated or widespread? (scope)\n- Pattern: what data characteristics trigger it?\n- How many records/activities affected?\n- Timeline: when did anomalies start appearing?")
+Task(prompt="Load sdk-insight-queries skill for data pattern analysis.\n\nFind patterns for this bug: $ARGUMENTS.\n\nYour job:\n1. Run insight queries to determine: is this isolated to one activity or widespread?\n2. Query for similar data anomalies across the workflow\n3. Look for patterns: does it affect specific phases, teams, date ranges, field values?\n4. Check for recent changes that could correlate with the bug\n\nReturn:\n- Is this isolated or widespread? (scope)\n- Pattern: what data characteristics trigger it?\n- How many records/activities affected?\n- Timeline: when did anomalies start appearing?")
 ```
 
-**Svetlana (Code Review):**
+**Code Reviewer:**
 ```
-Task(subagent_type="agent-svetlana-code-review", prompt="Review the code for this bug: $ARGUMENTS.\n\nYour job:\n1. Identify the relevant code sections (workflow logic, activity creation, field updates, phase transitions)\n2. Inspect for logic errors, missing validations, race conditions, null checks\n3. Look for assumptions that might break in edge cases\n4. Check for recent changes that could have introduced the bug\n\nReturn:\n- Suspected code sections with issues\n- Specific logic problems (race conditions, wrong field access, missing validation)\n- Edge cases not handled\n- Security implications if any")
+Task(prompt="Review the code for this bug: $ARGUMENTS.\n\nYour job:\n1. Identify the relevant code sections (workflow logic, activity creation, field updates, phase transitions)\n2. Inspect for logic errors, missing validations, race conditions, null checks\n3. Look for assumptions that might break in edge cases\n4. Check for recent changes that could have introduced the bug\n\nReturn:\n- Suspected code sections with issues\n- Specific logic problems (race conditions, wrong field access, missing validation)\n- Edge cases not handled\n- Security implications if any")
 ```
 
-**Tanya (Test Reproduction):**
+**Test Runner:**
 ```
-Task(subagent_type="agent-tanya-test-runner", prompt="Create a failing test for this bug: $ARGUMENTS.\n\nYour job:\n1. Write a minimal test that reproduces the bug\n2. Set up the preconditions (data state, workflow, etc)\n3. Execute the action that triggers the bug\n4. Assert the bug is present (test FAILS with current code)\n5. Do NOT fix the bug - just demonstrate it\n\nReturn:\n- The failing test code\n- What the test proves about the bug\n- Failure output showing the bug is real")
+Task(prompt="Load testing-patterns skill for writing focused tests.\n\nCreate a failing test for this bug: $ARGUMENTS.\n\nYour job:\n1. Write a minimal test that reproduces the bug\n2. Set up the preconditions (data state, workflow, etc)\n3. Execute the action that triggers the bug\n4. Assert the bug is present (test FAILS with current code)\n5. Do NOT fix the bug - just demonstrate it\n\nReturn:\n- The failing test code\n- What the test proves about the bug\n- Failure output showing the bug is real")
 ```
 
-If `$ARGUMENTS` contains `--skip-data`, skip Kenji.
-If `$ARGUMENTS` contains `--skip-queries`, skip Viktor.
+If `$ARGUMENTS` contains `--skip-data`, skip Data Reader.
+If `$ARGUMENTS` contains `--skip-queries`, skip SQL Insights.
 
 ### Step 3: Collect Results and Synthesize Root Cause
 
 Wait for all agents to complete. Aggregate findings:
 
-**From Kenji:** What data is wrong?
-**From Viktor:** How widespread is it? What pattern triggers it?
-**From Svetlana:** What code is broken?
-**From Tanya:** Can we reproduce it consistently?
+**From Data Reader:** What data is wrong?
+**From SQL Insights:** How widespread is it? What pattern triggers it?
+**From Code Reviewer:** What code is broken?
+**From Test Runner:** Can we reproduce it consistently?
 
 Look for convergence:
 - Does data anomaly match code logic error?
-- Does Svetlana's suspected code section align with Viktor's pattern?
-- Does Tanya's test reproduce the exact issue Kenji found?
+- Does Code Reviewer's suspected code section align with SQL Insights' pattern?
+- Does Test Runner's test reproduce the exact issue Data Reader found?
 
 If **clear root cause** emerges → proceed to Step 4 (report).
 
@@ -80,10 +80,10 @@ If **inconclusive** (no agent found clear cause OR agents disagree):
 If first iteration was inconclusive, re-run agents with narrowed focus:
 
 ```
-Task(subagent_type="agent-kenji-data-reader", prompt="Re-investigate (iteration [iteration]): $ARGUMENTS\n\nBased on initial findings:\n[SUMMARIZE WHAT FIRST PASS FOUND]\n\nNarrow your focus to: [MOST LIKELY AFFECTED AREA]\n\nDig deeper into the data state. Look for subtle issues.")
+Task(prompt="Load sdk-ws-config-skill for deep data investigation.\n\nRe-investigate (iteration [iteration]): $ARGUMENTS\n\nBased on initial findings:\n[SUMMARIZE WHAT FIRST PASS FOUND]\n\nNarrow your focus to: [MOST LIKELY AFFECTED AREA]\n\nDig deeper into the data state. Look for subtle issues.")
 ```
 
-Similar narrowed prompts for Viktor, Svetlana, Tanya.
+Similar narrowed prompts for SQL Insights, Code Reviewer, Test Runner agents.
 
 ### Step 4: Report
 
@@ -97,26 +97,26 @@ Similar narrowed prompts for Viktor, Svetlana, Tanya.
 
 ---
 
-### Kenji (Data State)
+### Data Reader
 **Affected Records:** [count/scope]
 - Expected state: [description]
 - Actual state: [description]
 - Anomalies found: [list]
 
-### Viktor (Query Patterns)
+### SQL Insights
 **Scope:** Isolated / Widespread (X records affected)
 **Pattern:** [What triggers the bug]
 **Timeline:** [When did it start]
 - Similar anomalies detected: [yes/no, details]
 
-### Svetlana (Code Review)
+### Code Reviewer
 **Suspected Code:** [files and line numbers]
 **Issues Found:**
 - [Issue 1]: [file:line] - [description]
 - [Issue 2]: [file:line] - [description]
 **Risk Level:** [LOW/MEDIUM/HIGH]
 
-### Tanya (Reproduction)
+### Test Runner
 **Test Status:** CREATED / FAILED TO REPRODUCE
 **Reproducibility:** Consistent / Intermittent / Cannot reproduce
 - Test file: [path]
@@ -138,7 +138,7 @@ Similar narrowed prompts for Viktor, Svetlana, Tanya.
 - Rationale: [why this fixes it]
 
 ### Next Steps
-1. [Fix applied by Svetlana/Simple Writer]
+1. [Fix applied by code reviewer/code editor]
 2. [Test to verify fix]
 3. [Deploy and monitor]
 ```
@@ -149,8 +149,8 @@ If any agent fails or times out, report partial results, note which failed, and
 
 | Flag | Effect |
 |------|--------|
-| `--skip-data` | Skip Kenji (when data investigation not needed) |
-| `--skip-queries` | Skip Viktor (when pattern analysis not needed) |
+| `--skip-data` | Skip Data Reader (when data investigation not needed) |
+| `--skip-queries` | Skip SQL Insights (when pattern analysis not needed) |
 | `--bg` | Run all agents in background mode |
 | `--debate` | Debate mode: competing hypotheses instead of domain-split investigation |
 
@@ -193,15 +193,15 @@ If user provided their own hypotheses in `$ARGUMENTS`, use those instead of gene
 
 Pick the best-fit agent for each hypothesis:
 
-| Hypothesis Type | Best Agent |
+| Hypothesis Type | Best Agent Role |
 |----------------|-----------|
-| Data integrity / missing values | **Kenji** |
-| Query / pattern / scope issue | **Viktor** |
-| Code logic / validation / race condition | **Svetlana** |
-| Reproducibility / environment | **Tanya** |
-| External integration / API | **Ivan** (monolith) or **Web Search** (research) |
-| Activity mover / phase cascade | **Igor** |
-| Zapier integration / external sync | **Zara** |
+| Data integrity / missing values | **Data Reader** (load sdk-ws-config-skill) |
+| Query / pattern / scope issue | **SQL Insights** (load sdk-insight-queries) |
+| Code logic / validation / race condition | **Code Reviewer** |
+| Reproducibility / environment | **Test Runner** (load testing-patterns) |
+| External integration / API | **Automation Inspector** (load hailer-monolith-automations) |
+| Activity mover / phase cascade | **Automation Inspector** (load hailer-monolith-automations) |
+| Zapier integration / external sync | **Integration Inspector** (load zapier-hailer-patterns) |
 
 Each agent gets:
 - The full problem description
@@ -209,7 +209,7 @@ Each agent gets:
 - Instruction: "Find evidence that supports OR refutes this hypothesis. Be honest - if evidence points away from your hypothesis, report that."
 
 ```
-Task(subagent_type="[best-fit-agent]", prompt="DEBATE MODE investigation for: $ARGUMENTS
+Task(prompt="Load relevant skill for deep investigation.\n\nDEBATE MODE investigation for: $ARGUMENTS
 
 YOUR HYPOTHESIS: [H1 description]
 
@@ -229,11 +229,11 @@ Launch all hypothesis agents in parallel.
 
 Collect results. For each hypothesis, assess:
 
-| Hypothesis | Supporting Evidence | Refuting Evidence | Confidence | Agent |
+| Hypothesis | Supporting Evidence | Refuting Evidence | Confidence | Role |
 |-----------|-------------------|-------------------|------------|-------|
-| H1 | [list] | [list] | STRONG/MODERATE/WEAK | [agent] |
-| H2 | [list] | [list] | STRONG/MODERATE/WEAK | [agent] |
-| H3 | [list] | [list] | STRONG/MODERATE/WEAK | [agent] |
+| H1 | [list] | [list] | STRONG/MODERATE/WEAK | [role] |
+| H2 | [list] | [list] | STRONG/MODERATE/WEAK | [role] |
+| H3 | [list] | [list] | STRONG/MODERATE/WEAK | [role] |
 
 **Verdict rules:**
 - If one hypothesis has STRONG confidence and others are WEAK → **clear winner**
@@ -251,7 +251,7 @@ Collect results. For each hypothesis, assess:
 ### Hypotheses Tested
 
 #### H1: [Hypothesis description]
-**Assigned to:** [Agent name]
+**Assigned to:** [Agent role]
 **Confidence:** STRONG / MODERATE / WEAK
 **Supporting evidence:**
 - [Evidence 1]

package/.claude/commands/doc-squad.md

@@ -1,5 +1,5 @@
 ---
-description: Document API endpoints with Lars and Marcus
+description: Document API endpoints with code analysis and documentation generation
 argument-hint: "endpoint or module to document"
 allowed-tools: Task, Bash
 ---
@@ -7,47 +7,47 @@ allowed-tools: Task, Bash
 
 Sequential pipeline: Code analysis, then generate documentation.
 
-**Agents:**
-1. **Lars** - LSP code analysis (inspect types, schemas, function signatures)
-2. **Marcus** - API documentation (generate endpoint docs from analysis)
+**Roles:**
+1. **Code Inspector** - LSP code analysis (inspect types, schemas, function signatures)
+2. **Documentation Generator** - API documentation (generate endpoint docs from analysis)
 
 **Goal:** $ARGUMENTS
 
 ## Protocol
 
-### Step 1: Lars (LSP Analysis)
+### Step 1: Code Analysis
 
-Spawn Lars to analyze code and extract types/schemas:
+Spawn a code inspector to analyze code and extract types/schemas:
 
 ```
-Task(subagent_type="agent-lars-code-inspector", prompt="Inspect code for: $ARGUMENTS. Extract:\n- Function signatures\n- Type definitions\n- Return types\n- Parameter schemas\n- Joi/Zod validation rules\n\nUse LSP if available. Return structured analysis with types and schemas.")
+Task(prompt="Load lsp-setup skill for code inspection.\n\nInspect code for: $ARGUMENTS. Extract:\n- Function signatures\n- Type definitions\n- Return types\n- Parameter schemas\n- Joi/Zod validation rules\n\nUse LSP if available. Return structured analysis with types and schemas.")
 ```
 
-Wait for result. Save the analysis output - Marcus needs these type definitions.
+Wait for result. Save the analysis output - the documentation generator needs these type definitions.
 
-### Step 2: Marcus (API Documentation)
+### Step 2: Generate Documentation
 
-Spawn Marcus with the code analysis from Lars:
+Spawn a documentation generator with the code analysis:
 
 ```
-Task(subagent_type="agent-marcus-api-documenter", prompt="Generate API documentation for: $ARGUMENTS.\n\nCode analysis from Lars:\n[PASTE LARS'S OUTPUT - types, schemas, function signatures]\n\nCreate comprehensive endpoint documentation including:\n- Endpoint path and method\n- Description\n- Parameters and types\n- Request/response examples\n- Error codes and handling\n- Usage examples with @hailer/cli")
+Task(prompt="Load api-documentation-patterns skill for creating API documentation.\n\nGenerate API documentation for: $ARGUMENTS.\n\nCode analysis from code inspector:\n[PASTE CODE INSPECTOR OUTPUT - types, schemas, function signatures]\n\nCreate comprehensive endpoint documentation including:\n- Endpoint path and method\n- Description\n- Parameters and types\n- Request/response examples\n- Error codes and handling\n- Usage examples with @hailer/cli")
 ```
 
 Wait for result. If `"status": "ready_to_push"`:
-- Run the push commands Marcus provides
+- Run the push commands provided
 
 ### Step 3: Report
 
 ```markdown
 ## Doc Squad Complete
 
-### Lars (Code Analysis)
+### Code Inspector
 - Files analyzed: [count]
 - Functions found: [count]
 - Types extracted: [count]
 - Schemas identified: [list]
 
-### Marcus (Documentation)
+### Documentation Generator
 - Endpoints documented: [count]
 - Examples created: [count]
 - Files generated: [list]
@@ -60,6 +60,6 @@ Wait for result. If `"status": "ready_to_push"`:
 
 ## Notes
 
-- Lars runs first to extract accurate types - never guess schemas
-- Marcus creates human-friendly docs from the type analysis
+- Code Inspector runs first to extract accurate types - never guess schemas
+- Documentation Generator creates human-friendly docs from the type analysis
 - Documentation stays in sync with actual code signatures