@hailer/mcp 1.1.16 → 1.1.17-beta.0

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

@@ -1,5 +1,5 @@
 ---
-description: Build backend integrations with Kenji, Ivan, and Tanya
+description: Build backend integrations with schema discovery and automation
 argument-hint: "integration description"
 allowed-tools: Task, Bash, Read
 ---
@@ -7,64 +7,64 @@ allowed-tools: Task, Bash, Read
 
 Sequential pipeline: Schema discovery, build integration, then verify with tests.
 
-**Agents:**
-1. **Kenji** - Schema discovery (workflow fields, types, IDs)
-2. **Ivan** - Build integration (monolith webhooks, scheduled jobs, automations)
-3. **Tanya** - Test runner (verify integration with tests)
+**Roles:**
+1. **Data Reader** - Schema discovery (workflow fields, types, IDs)
+2. **Automation Builder** - Build integration (monolith webhooks, scheduled jobs, automations)
+3. **Test Runner** - Test runner (verify integration with tests)
 
 **Goal:** $ARGUMENTS
 
 ## Protocol
 
-### Step 1: Kenji (Schema Discovery)
+### Step 1: Schema Discovery
 
-Start with Kenji to gather workflow schema and field IDs needed for the integration:
+Start with schema discovery to gather workflow schema and field IDs needed for the integration:
 
 ```
-Task(subagent_type="agent-kenji-data-reader", prompt="List all workflows and their fields relevant to: $ARGUMENTS. Include field IDs, types, and any existing integrations. Also identify webhook URLs and activity phase names needed.")
+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 any existing integrations. Also identify webhook URLs and activity phase names needed.")
 ```
 
-Wait for result. Save the schema output - Ivan needs these IDs.
+Wait for result. Save the schema output - the automation builder needs these IDs.
 
-### Step 2: Ivan (Build Integration)
+### Step 2: Build Integration
 
-Spawn Ivan with the schema context from Kenji:
+Spawn an automation builder with the schema context:
 
 ```
-Task(subagent_type="agent-ivan-monolith", prompt="Build a backend integration for: $ARGUMENTS.\n\nWorkflow schema from Kenji:\n[PASTE KENJI'S OUTPUT - workflow IDs, field IDs, types, phases]\n\nImplement in the hailer-integration monolith. Use correct IDs for webhooks, scheduled jobs, or automations.")
+Task(prompt="Load hailer-monolith-automations skill for building integrations.\n\nBuild a backend integration for: $ARGUMENTS.\n\nWorkflow schema from data reader:\n[PASTE SCHEMA DISCOVERY OUTPUT - workflow IDs, field IDs, types, phases]\n\nImplement in the hailer-integration monolith. Use correct IDs for webhooks, scheduled jobs, or automations.")
 ```
 
 Wait for result. If `"status": "ready_to_push"`:
-- Run the push commands Ivan provides
+- Run the push commands provided
 
-### Step 3: Tanya (Test Runner)
+### Step 3: Test Integration
 
-Spawn Tanya to verify the integration works:
+Spawn a test runner to verify the integration works:
 
 ```
-Task(subagent_type="agent-tanya-test-runner", prompt="Test the integration for: $ARGUMENTS.\n\nTest coverage needed:\n- Webhook payload validation (if webhook)\n- Scheduled job execution (if scheduled)\n- Activity creation/phase transitions\n- Error handling and edge cases\n\nRun tests and report pass/fail counts.")
+Task(prompt="Load testing-patterns skill for integration testing.\n\nTest the integration for: $ARGUMENTS.\n\nTest coverage needed:\n- Webhook payload validation (if webhook)\n- Scheduled job execution (if scheduled)\n- Activity creation/phase transitions\n- Error handling and edge cases\n\nRun tests and report pass/fail counts.")
 ```
 
-Wait for result. If tests fail, report which ones and offer to have Ivan fix issues.
+Wait for result. If tests fail, report which ones and offer to have the automation builder fix issues.
 
 ### Step 4: Report
 
 ```markdown
 ## Integration Squad Complete
 
-### Kenji (Schema Discovery)
+### Data Reader (Schema Discovery)
 - Workflows found: [list]
 - Fields mapped: [count]
 - Phases identified: [list]
 - Existing integrations: [list or "none"]
 
-### Ivan (Monolith Integration)
+### Automation Builder
 - Integration type: [webhook/scheduled/automation]
 - Files created/modified: [list]
 - Endpoints: [list if webhook]
 - Commands run: [list]
 
-### Tanya (Tests)
+### Test Runner
 - Tests: X passed, X failed
 - Build: Pass/Fail
 - [Failed test details if any]
@@ -77,6 +77,6 @@ Wait for result. If tests fail, report which ones and offer to have Ivan fix iss
 
 ## Notes
 
-- Kenji must run first to get real IDs - never let Ivan guess IDs
+- Data Reader must run first to get real IDs - never let automation builder guess IDs
 - Each agent in the pipeline depends on output from the previous step
-- If tests fail, Ivan may need to revise the integration code
+- If tests fail, the automation builder may need to revise the integration code

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

@@ -7,11 +7,11 @@ allowed-tools: Task, Bash
 
 Deep project cleanup across code, configuration, and data. Discovers dead patterns and auto-fixes clear-cut removals.
 
-**Agents:**
-- **Lars** - Dead code detection (unused imports, unreachable code, type errors via LSP)
-- **Bjorn** - Configuration audit (deprecated fields, broken references, unused workflows)
-- **Viktor** - Data analysis (unpopulated fields, zero-activity workflows, silent insights)
-- **Simple Writer** - Auto-fix confirmed dead code and unused imports (fix loop)
+**Roles:**
+- **Dead Code Inspector** - Dead code detection (unused imports, unreachable code, type errors via LSP)
+- **Config Auditor** - Configuration audit (deprecated fields, broken references, unused workflows)
+- **Data Analyzer** - Data analysis (unpopulated fields, zero-activity workflows, silent insights)
+- **Code Fixer** - Auto-fix confirmed dead code and unused imports (fix loop)
 - **Code Simplifier** - Simplify complex code blocks identified during discovery (fix loop)
 
 **Target:** $ARGUMENTS (if blank, scan full project)
@@ -26,12 +26,12 @@ If `$ARGUMENTS` has specific files/directories, use those as the target.
 Otherwise, scan the entire project.
 
 If `$ARGUMENTS` contains `--code-only`:
-- Skip Bjorn and Viktor
-- Only run Lars in discovery phase
+- Skip Config Auditor and Data Analyzer
+- Only run Dead Code Inspector in discovery phase
 
 If `$ARGUMENTS` contains `--config-only`:
-- Skip Lars and Viktor
-- Only run Bjorn in discovery phase
+- Skip Dead Code Inspector and Data Analyzer
+- Only run Config Auditor in discovery phase
 
 If `$ARGUMENTS` contains `--report-only`:
 - Skip all fix loop iterations
@@ -43,31 +43,31 @@ If `$ARGUMENTS` contains `--report-only`:
 
 Spawn all three discovery agents simultaneously using multiple Task tool calls in a single message:
 
-**Lars:**
+**Dead Code Inspector:**
 ```
-Task(subagent_type="agent-lars-code-inspector", prompt="Inspect the project for dead code patterns: [TARGET]. Find:\n- Unused imports\n- Unreachable code blocks\n- Unused variables and functions\n- Type errors\n\nUse LSP if available, fall back to tsc/eslint. Return detailed findings grouped by file.")
+Task(prompt="Load lsp-setup skill for code inspection.\n\nInspect the project for dead code patterns: [TARGET]. Find:\n- Unused imports\n- Unreachable code blocks\n- Unused variables and functions\n- Type errors\n\nUse LSP if available, fall back to tsc/eslint. Return detailed findings grouped by file.")
 ```
 
-**Bjorn:**
+**Config Auditor:**
 ```
-Task(subagent_type="agent-bjorn-config-audit", prompt="Audit workspace configuration for zombie patterns: [TARGET]. Check:\n- Deprecated fields in workspace/fields.ts\n- Broken field references in phases\n- Unused workflows (defined but zero activities)\n- Broken enum references\n- Orphaned configuration entries\n\nReturn issues grouped by category with severity.")
+Task(prompt="Audit workspace configuration for zombie patterns: [TARGET]. Check:\n- Deprecated fields in workspace/fields.ts\n- Broken field references in phases\n- Unused workflows (defined but zero activities)\n- Broken enum references\n- Orphaned configuration entries\n\nReturn issues grouped by category with severity.")
 ```
 
-**Viktor:**
+**Data Analyzer:**
 ```
-Task(subagent_type="agent-viktor-sql-insights", prompt="Analyze data patterns in workflows: [TARGET]. Find:\n- Fields that are defined but never populated (zero values across all activities)\n- Workflows with zero activities (created but unused)\n- Insights that return empty data (broken or obsolete)\n- Calculated fields that never execute\n- Orphaned data patterns\n\nReturn findings with field IDs, workflow IDs, and impact estimates.")
+Task(prompt="Load sdk-insight-queries skill for data analysis.\n\nAnalyze data patterns in workflows: [TARGET]. Find:\n- Fields that are defined but never populated (zero values across all activities)\n- Workflows with zero activities (created but unused)\n- Insights that return empty data (broken or obsolete)\n- Calculated fields that never execute\n- Orphaned data patterns\n\nReturn findings with field IDs, workflow IDs, and impact estimates.")
 ```
 
 ### Step 3: Categorize Findings
 
 Collect results from all three agents. Categorize each finding as:
 
-**AUTO-FIXABLE** (Simple Writer can safely remove):
-- Unused imports identified by Lars
+**AUTO-FIXABLE** (Code Fixer can safely remove):
+- Unused imports identified by Dead Code Inspector
 - Dead code blocks with no side effects
-- Workflow definitions with zero activities (from Viktor + Bjorn)
-- Deprecated enum references (from Bjorn)
-- Never-populated fields that can be safely archived (from Viktor + Bjorn)
+- Workflow definitions with zero activities (from Data Analyzer + Config Auditor)
+- Deprecated enum references (from Config Auditor)
+- Never-populated fields that can be safely archived (from Data Analyzer + Config Auditor)
 
 **NEEDS-HUMAN-REVIEW** (escalate to user):
 - Architecture concerns
@@ -78,16 +78,16 @@ Collect results from all three agents. Categorize each finding as:
 
 ### Step 4: Auto-Fix Loop (if auto-fixable items found AND `--report-only` not set AND `iteration < 3`)
 
-If critical auto-fixable items exist, spawn two agents to clean up. If Simple Writer's fixes introduce new issues detected by re-audit, escalate remaining issues to user after max 2 iterations.
+If critical auto-fixable items exist, spawn two agents to clean up. If the Code Fixer's fixes introduce new issues detected by re-audit, escalate remaining issues to user after max 2 iterations.
 
-**Simple Writer:**
+**Code Fixer:**
 ```
-Task(subagent_type="agent-simple-writer", prompt="Remove confirmed dead code and unused imports from the project:\n\n[LIST AUTO-FIXABLE ITEMS WITH FILE PATHS AND LINE NUMBERS]\n\nFrom Lars:\n- [Unused imports with files]\n- [Dead code blocks with files]\n\nFrom Bjorn:\n- [Deprecated enum references with files]\n- [Unused workflow definitions with IDs]\n\nFrom Viktor:\n- [Never-populated field definitions with IDs]\n\nApply minimal removals only. Do not refactor or improve beyond confirmed dead patterns.")
+Task(prompt="Remove confirmed dead code and unused imports from the project:\n\n[LIST AUTO-FIXABLE ITEMS WITH FILE PATHS AND LINE NUMBERS]\n\nFrom Dead Code Inspector:\n- [Unused imports with files]\n- [Dead code blocks with files]\n\nFrom Config Auditor:\n- [Deprecated enum references with files]\n- [Unused workflow definitions with IDs]\n\nFrom Data Analyzer:\n- [Never-populated field definitions with IDs]\n\nApply minimal removals only. Do not refactor or improve beyond confirmed dead patterns.")
 ```
 
 **Code Simplifier:**
 ```
-Task(subagent_type="agent-code-simplifier", prompt="After dead code removal, simplify complex code blocks identified as difficult to maintain: [TARGET].\n\nFocus on:\n- Variable naming clarity\n- Function complexity reduction\n- Comment clarity around remaining logic\n- Code organization in affected files\n\nReturn refactoring suggestions with before/after examples.")
+Task(prompt="After dead code removal, simplify complex code blocks identified as difficult to maintain: [TARGET].\n\nFocus on:\n- Variable naming clarity\n- Function complexity reduction\n- Comment clarity around remaining logic\n- Code organization in affected files\n\nReturn refactoring suggestions with before/after examples.")
 ```
 
 After both finish:
@@ -106,20 +106,20 @@ After both finish:
 - Auto-fixes applied: [yes/no]
 - Items removed: [count by category]
 
-### Lars (Dead Code Detection)
+### Dead Code Inspector
 - Unused imports: X (Y auto-removed)
 - Dead code blocks: X (Y auto-removed)
 - Type errors: X
 - [Remaining issues grouped by file]
 
-### Bjorn (Config Audit)
+### Config Auditor
 - Deprecated fields: X
 - Broken references: X (Y auto-removed)
 - Unused workflows: X (Y auto-removed)
 - Orphaned config: X
 - [Remaining issues grouped by category]
 
-### Viktor (Data Analysis)
+### Data Analyzer
 - Never-populated fields: X (Y marked for archival)
 - Zero-activity workflows: X (Y removed)
 - Silent insights: X
@@ -151,8 +151,8 @@ If any agent fails or times out, report partial results from successful agents,
 
 | Flag | Effect |
 |------|--------|
-| `--code-only` | Skip Bjorn and Viktor, just code cleanup via Lars |
-| `--config-only` | Skip Lars and Viktor, just workspace config audit via Bjorn |
+| `--code-only` | Skip Config Auditor and Data Analyzer, just code cleanup via Dead Code Inspector |
+| `--config-only` | Skip Dead Code Inspector and Data Analyzer, just workspace config audit via Config Auditor |
 | `--report-only` | Report findings only, no auto-fix loop (discovery phase only) |
 | `--bg` | Run all discovery agents in background mode |
 
@@ -161,7 +161,7 @@ If `--bg` is present, launch all discovery agents with `run_in_background: true`
 ## Notes
 
 - Max 2 re-discovery iterations (3 total) to prevent infinite loops
-- Simple Writer only removes clear-cut dead code - ambiguous items go to user review
-- Data cleanup (Viktor findings) may affect reports/history - always prompt user before removal
+- Code Fixer only removes clear-cut dead code - ambiguous items go to user review
+- Data cleanup (Data Analyzer findings) may affect reports/history - always prompt user before removal
 - Each re-discovery is a full parallel sweep across all enabled agents
 - The `--report-only` flag gives discovery results without auto-fixes

package/.claude/commands/learn-auto.md

@@ -62,8 +62,8 @@ If learnings found, present to user:
 ```
 Found [N] potential learnings from this session:
 
-1. [agent/kenji] Field lookup should check enums.ts first
-   Context: Kenji made API call when data was available locally
+1. [agent/data-reader] Field lookup should check enums.ts first
+   Context: Data Reader made API call when data was available locally
 
 2. [pattern] Date fields from Hailer come pre-formatted
    Context: Tried to format already-formatted date, got wrong output
@@ -96,10 +96,10 @@ If in project repo, write to `docs/learnings.md` or project's inbox location.
 
 ```
 Captured [N] learnings to inbox:
-- [agent/kenji] Field lookup should check enums.ts first
+- [agent/data-reader] Field lookup should check enums.ts first
 - [pattern] Date fields from Hailer come pre-formatted
 
-Review later with /learn to apply fixes, or let Ada auto-process.
+Review later with /learn to apply fixes, or let Skill Builder auto-process.
 ```
 
 ## No Learnings Found
@@ -114,7 +114,7 @@ To capture something manually: /learn <category> <description>
 
 ## Notes
 
-- This is DETECTION only - doesn't apply fixes (that's /learn or Ada's job)
+- This is DETECTION only - doesn't apply fixes (that's /learn's job)
 - User confirms before anything is saved
 - Bias toward false negatives (miss some) rather than false positives (noise)
 - Works best at end of session when there's context to analyze

package/.claude/commands/learn.md

@@ -10,7 +10,6 @@ Capture a learning, ask clarifying questions, then apply the fix to the right pl
 `/learn <category> <description>`
 
 ## Categories
-- `agent/<name>` - Agent behavior issue (e.g., `agent/kenji`)
 - `skill/<name>` - Skill missing pattern (e.g., `skill/function-fields`)
 - `pattern` - General pattern to document
 - `bug` - Bug in code/config
@@ -18,7 +17,7 @@ Capture a learning, ask clarifying questions, then apply the fix to the right pl
 
 ## Examples
 ```
-/learn agent/kenji should check enums.ts before API calls
+/learn skill/data-reader should check enums.ts before API calls
 /learn skill/insights JOIN syntax was wrong for linked fields
 /learn pattern always verify push succeeded before continuing
 /learn gotcha phase IDs change when workflow is copied
@@ -29,16 +28,16 @@ Capture a learning, ask clarifying questions, then apply the fix to the right pl
 ### Step 1: Parse & Understand
 
 Parse the input:
-- Category: first word (e.g., `agent/kenji`)
+- Category: first word (e.g., `skill/data-reader`)
 - Description: rest of the text
 
 ### Step 2: Ask Clarifying Questions
 
 Use AskUserQuestion to gather details:
 
-**For agent issues:**
+**For skill issues:**
 - "What was the symptom?" (wrong output, error, missed step)
-- "What should the agent do differently?"
+- "What should the skill do differently?"
 - "Should this be a rule, a skill addition, or both?"
 
 **For skill issues:**
@@ -55,11 +54,10 @@ Based on category and answers, decide where the fix goes:
 
 | Category | Likely Target |
 |----------|---------------|
-| `agent/X` | `.claude/agents/agent-X.md` |
 | `skill/X` | `.claude/skills/X/SKILL.md` |
 | `pattern` | Relevant skill or CLAUDE.md |
 | `bug` | Code fix + possibly skill |
-| `gotcha` | Skill or agent rules section |
+| `gotcha` | Skill or CLAUDE.md |
 
 ### Step 4: Apply the Fix
 
@@ -67,16 +65,10 @@ Based on category and answers, decide where the fix goes:
 - Edit the target file directly
 - Add to appropriate section (rules, patterns, examples)
 
-**Option B: Delegate to Ada (if complex)**
-For complex changes, invoke Ada agent:
+**Option B: Delegate to a sub-agent (if complex)**
+For complex changes requiring deep knowledge of skills or patterns:
 ```
-Task(subagent_type="agent-ada-skill-builder", prompt={
-  "task": "apply_learning",
-  "category": "<category>",
-  "learning": "<description>",
-  "details": "<clarification answers>",
-  "target": "<determined target>"
-})
+Task(prompt="Apply this learning to the appropriate skill or config file.\n\nCategory: <category>\nLearning: <description>\nDetails: <clarification answers>\nTarget: <determined target>\n\nEdit the target file to incorporate this learning.")
 ```
 
 ### Step 5: Log & Confirm
@@ -89,9 +81,9 @@ Task(subagent_type="agent-ada-skill-builder", prompt={
 2. Report what was done:
    ```
    Learning applied:
-   - Category: agent/kenji
+   - Category: role/data-reader
    - Fix: Added rule "Check enums.ts before making API calls"
-   - Location: .claude/agents/agent-kenji-data-reader.md
+   - Location: .claude/skills/<relevant-skill>/SKILL.md
    ```
 
 ## File Template
@@ -107,7 +99,7 @@ History of fixes applied from learnings.
 
 ## Log
 
-- [agent/kenji] Check enums.ts first → Added to rules _(2026-01-31)_
+- [skill/data-reader] Check enums.ts first → Added to SKILL.md _(2026-01-31)_
 - [skill/insights] JOIN syntax example → Added to SKILL.md _(2026-01-31)_
 ```
 
@@ -116,5 +108,5 @@ History of fixes applied from learnings.
 - This command APPLIES fixes, not just logs them
 - Ask questions to understand the real issue
 - Small fixes: edit directly
-- Complex fixes: delegate to Ada
+- Complex fixes: delegate to a general-purpose sub-agent
 - Always log what was done for history

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

@@ -7,11 +7,11 @@ allowed-tools: Task, Bash, Read
 
 Sequential pipeline: Create workspace infrastructure, scaffold the app, and verify everything is wired correctly.
 
-**Agents:**
-1. **Helga** - Workflow config (create workflows, fields, phases, teams, groups)
-2. **Alejandro** - Function fields and nameFunction
-3. **Giuseppe** - Scaffold first app with basic CRUD interface
-4. **Bjorn** - Audit config accuracy and field references
+**Roles:**
+1. **Workflow Config** - Workflow configuration (create workflows, fields, phases, teams, groups)
+2. **Function Fields** - Calculated fields and nameFunction
+3. **App Builder** - Scaffold first app with basic CRUD interface
+4. **Config Auditor** - Audit configuration accuracy and field references
 
 **Goal:** $ARGUMENTS
 
@@ -24,72 +24,62 @@ Parse `$ARGUMENTS` to determine input type:
 - **If it's a file path** (e.g., `docs/prd-onboarding.md`): Read it for requirements
 - **Otherwise:** Use it as a project description
 
-If `$ARGUMENTS` is a file path, read it first before proceeding to Helga.
+If `$ARGUMENTS` is a file path, read it first before proceeding to Workflow Config.
 
-### Step 2: Helga (Workspace Config)
+### Step 2: Workflow Config
 
-Spawn Helga to create workspace infrastructure:
+Spawn a workflow config agent to create workspace infrastructure:
 
 ```
-Task(subagent_type="agent-helga-workflow-config", prompt="Bootstrap a new Hailer project: $ARGUMENTS\n\nCreate: workflows (at least 1), fields for each workflow, phases, teams, and groups as needed.")
+Task(prompt="Load sdk-ws-config-skill for workspace setup.\n\nBootstrap a new Hailer project: $ARGUMENTS\n\nCreate: workflows (at least 1), fields for each workflow, phases, teams, and groups as needed.")
 ```
 
-Wait for result. If Helga returns `"status": "ready_to_push"`:
-- Run the push commands she provides (e.g., `npm run fields-push:force`)
+Wait for result. If the agent returns `"status": "ready_to_push"`:
+- Run the push commands provided (e.g., `npm run fields-push:force`)
 - Then run `npm run pull` to refresh local workspace with new IDs
-- **Important:** Helga ALWAYS spawns Alejandro for nameFunction. Check if her result indicates Alejandro was spawned and created nameFunction. If yes, Alejandro's work is done - skip to Step 3.
+- **Important:** Workflow config ALWAYS spawns a function fields agent for nameFunction. Check if the result indicates it was spawned and created nameFunction. If yes, function fields work is done - skip to Step 3.
 
-### Step 3: Alejandro (Function Fields) - Conditional
+### Step 3: Function Fields - Conditional
 
-Only spawn if Helga indicates additional function fields are needed beyond what was created by Helga+Alejandro auto-spawn.
+Only spawn if workflow config indicates additional function fields are needed beyond what was created by the auto-spawn.
 
-If needed, spawn Alejandro:
+If needed, spawn a function fields agent:
 
 ```
-Task(subagent_type="agent-alejandro-function-fields", prompt="Create additional function fields for workflows created in: [INSERT HELGA'S GOAL].\n\nHelga created these workflows: [SUMMARIZE HELGA'S RESULT - workflow names, IDs, field counts].\n\nFunction fields already created by Helga: [FROM HELGA'S RESULT].")
+Task(prompt="Load sdk-function-fields and sdk-ws-config-skill skills for creating calculated fields.\n\nCreate additional function fields for workflows created in: [INSERT WORKFLOW CONFIG GOAL].\n\nWorkflow config created these workflows: [SUMMARIZE WORKFLOW CONFIG RESULT - workflow names, IDs, field counts].\n\nFunction fields already created by workflow config: [FROM WORKFLOW CONFIG RESULT].")
 ```
 
 Wait for result. If `"status": "ready_to_push"`:
 - Run the push commands
 - Run `npm run pull` to refresh workspace
 
-### Step 4: Giuseppe (App Scaffold)
+### Step 4: App Scaffold
 
-**Before spawning Giuseppe, enable builder mode:**
-```
-Bash: node .claude/hooks/app-edit-guard.cjs --agent-on
-```
-
-Spawn Giuseppe to build the first app using the new workspace:
-
-```
-Task(subagent_type="agent-giuseppe-app-builder", prompt="Scaffold the first Hailer app for this new project: $ARGUMENTS\n\nWorkspace created by Helga: [SUMMARIZE HELGA'S RESULT - workflow names, IDs, field counts]. Giuseppe: read workspace/ directly to discover exact field IDs, types, and team configurations. Do not guess IDs.\n\nBuild a basic CRUD interface using @hailer/app-sdk and Chakra UI. Start with the primary workflow. Use the Hailer Design System.\n\nNote: Assume Local Dev app exists (orchestrator checks this before spawning you). Build for local development at http://localhost:3000.")
-```
+Spawn an app builder to build the first app using the new workspace:
 
-**After Giuseppe completes, disable builder mode:**
 ```
-Bash: node .claude/hooks/app-edit-guard.cjs --agent-off
+Task(prompt="Load hailer-app-builder and hailer-design-system skills for app development.\n\nScaffold the first Hailer app for this new project: $ARGUMENTS\n\nWorkspace created by workflow config: [SUMMARIZE WORKFLOW CONFIG RESULT - workflow names, IDs, field counts]. You: read workspace/ directly to discover exact field IDs, types, and team configurations. Do not guess IDs.\n\nBuild a basic CRUD interface using @hailer/app-sdk and Chakra UI. Start with the primary workflow. Use the Hailer Design System.\n\nNote: Assume Local Dev app exists (orchestrator checks this before spawning you). Build for local development at http://localhost:3000.")
 ```
 
-Wait for result. If Giuseppe returns `"status": "ready_to_push"`:
+Wait for result. If the builder returns `"status": "ready_to_push"`:
 - Run the push commands
 
-### Step 5: Bjorn (Config Audit)
+### Step 5: Config Audit
 
-Spawn Bjorn to verify everything is configured correctly:
+Spawn a config auditor to verify everything is configured correctly:
 
 ```
-Task(subagent_type="agent-bjorn-config-audit", prompt="Audit this new Hailer project setup:\n\n1. Verify CLAUDE.md accuracy (check that project type detection works)\n2. Verify workspace configuration: workflows, fields, phases, teams all match workspace/ files\n3. Verify field references in the new app match workspace/ field definitions\n4. Check for missing imports, incorrect IDs, or type mismatches\n5. Verify that nameFunction is set on the primary workflow\n\nProject goal: $ARGUMENTS\n\nReport any misconfigurations. If iteration <= 1, recommend fixes to the orchestrator.")
+Task(prompt="Audit this new Hailer project setup:\n\n1. Verify CLAUDE.md accuracy (check that project type detection works)\n2. Verify workspace configuration: workflows, fields, phases, teams all match workspace/ files\n3. Verify field references in the new app match workspace/ field definitions\n4. Check for missing imports, incorrect IDs, or type mismatches\n5. Verify that nameFunction is set on the primary workflow\n\nProject goal: $ARGUMENTS\n\nReport any misconfigurations. If iteration <= 1, recommend fixes to the orchestrator.")
 ```
 
 **Loop Control:**
-- If Bjorn finds no critical issues: proceed to Step 6 (report)
-- If Bjorn finds issues AND `iteration <= 1`:
+- If config auditor finds no critical issues: proceed to Step 6 (report)
+- If config auditor finds issues AND `iteration <= 1`:
   - Increment `iteration`
-  - Determine which agent to fix it (usually Helga or Giuseppe)
+  - Determine which agent to fix it (usually Workflow Config or App Builder)
   - Run appropriate agent with the issues to fix
-  - Return to Step 5 (Bjorn re-audits)
-- If Bjorn finds issues AND `iteration > 1`: escalate to user in Step 6
+  - Return to Step 5 (config audit re-checks)
+- If config auditor finds issues AND `iteration > 1`: escalate to user in Step 6
 
 ### Step 6: Report
 
@@ -98,30 +88,30 @@ Task(subagent_type="agent-bjorn-config-audit", prompt="Audit this new Hailer pro
 
 **Project Goal:** $ARGUMENTS
 
-### Workspace Setup (Helga)
+### Workspace Setup
 - Workflows created: [list with IDs]
 - Fields created: [count]
 - Phases: [count]
 - Teams: [count]
-- Alejandro auto-spawn: [nameFunction created? Y/N]
+- Function fields auto-spawn: [nameFunction created? Y/N]
 
-### Function Fields (Alejandro)
+### Function Fields
 - Additional function fields created: [list or "None needed"]
 - Skipped: [reason if skipped]
 
-### App Scaffold (Giuseppe)
+### App Scaffold
 - App path: [path to new app]
 - Build status: Pass/Fail
 - Files created: [count/list]
 - Local dev setup: [check local dev app name]
 
-### Verification (Bjorn)
+### Config Audit
 - Critical issues found: [count] or "None"
 - Status: VERIFIED / NEEDS FIXES (if iteration > 1, see below)
 
 [If iteration > 1 - escalated:]
 ### Remaining Issues
-[List issues Bjorn found that weren't resolved in 1 fix iteration]
+[List issues config auditor found that weren't resolved in 1 fix iteration]
 - Manual fixes recommended: [hints]
 
 ### Next Steps
@@ -133,8 +123,8 @@ Task(subagent_type="agent-bjorn-config-audit", prompt="Audit this new Hailer pro
 
 ## Notes
 
-- Each agent in the pipeline needs IDs from the previous step. Always `npm run pull` between Helga→Alejandro→Giuseppe to refresh local workspace.
-- Helga auto-spawns Alejandro for nameFunction. Check her result - only spawn Alejandro again in Step 3 if additional function fields are needed.
-- Giuseppe needs real workflow and field IDs from workspace/ - always read the files and paste actual IDs, never let him guess.
-- Bjorn's audit is the quality gate. If issues are found and you've iterated once, escalate remaining issues to the user rather than looping infinitely.
-- Set `iteration = 1` at the start. Increment after each Bjorn audit if fixes are attempted.
+- Each agent in the pipeline needs IDs from the previous step. Always `npm run pull` between Workflow Config→Function Fields→App Builder to refresh local workspace.
+- Workflow config auto-spawns function fields agent for nameFunction. Check the result - only spawn function fields separately in Step 3 if additional function fields are needed.
+- App builder needs real workflow and field IDs from workspace/ - always read the files and paste actual IDs, never let it guess.
+- Config auditor's audit is the quality gate. If issues are found and you've iterated once, escalate remaining issues to the user rather than looping infinitely.
+- Set `iteration = 1` at the start. Increment after each config audit if fixes are attempted.

package/.claude/commands/plan-workspace.md

@@ -707,8 +707,8 @@ Use the PRD templates from autoplan but with REAL DATA from the discovery:
 **Total components planned:** X
 
 **Recommended build order:**
-1. Core workflows (master data first) - Helga auto-spawns Alejandro for nameFunction
-2. Transactional workflows - Helga auto-spawns Alejandro for nameFunction + function fields
+1. Core workflows (master data first) - create nameFunction after workflow setup
+2. Transactional workflows - create nameFunction + function fields after workflow setup
 3. Cross-workflow function fields (if needed separately)
 4. Insights for apps/reports
 5. Document templates (PDF/CSV)