@robbiesrobotics/alice-agents 1.2.1 → 1.2.3

package/lib/workspace-scaffolder.mjs

@@ -6,6 +6,7 @@ import { fileURLToPath } from 'node:url';
 const __dirname = dirname(fileURLToPath(import.meta.url));
 const TEMPLATES_DIR = join(__dirname, '..', 'templates', 'workspaces');
 const OPENCLAW_DIR = join(homedir(), '.openclaw');
+const SKILLS_DIR = join(OPENCLAW_DIR, 'skills');
 
 // Product files — always overwritten on install/upgrade
 const PRODUCT_FILES = ['SOUL.md', 'AGENTS.md', 'IDENTITY.md', 'TOOLS.md'];
@@ -99,6 +100,22 @@ export function scaffoldWorkspace(agent, userInfo, agentCount) {
   return { workspaceDir, written, skipped };
 }
 
+export function scaffoldSkills() {
+  // Install the claude-code skill into ~/.openclaw/skills/
+  const claudeCodeSkillDir = join(SKILLS_DIR, 'claude-code');
+  mkdirSync(claudeCodeSkillDir, { recursive: true });
+
+  const skillTemplatePath = join(__dirname, '..', 'templates', 'skills', 'claude-code', 'SKILL.md');
+  const skillDestPath = join(claudeCodeSkillDir, 'SKILL.md');
+
+  if (existsSync(skillTemplatePath)) {
+    const content = readFileSync(skillTemplatePath, 'utf8');
+    writeFileSync(skillDestPath, content, 'utf8');
+    return true;
+  }
+  return false;
+}
+
 export function scaffoldAll(agents, userInfo) {
   const agentCount = agents.length;
   const results = [];
@@ -108,5 +125,8 @@ export function scaffoldAll(agents, userInfo) {
     results.push({ agent: agent.id, ...result });
   }
 
+  // Install skills
+  scaffoldSkills();
+
   return results;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@robbiesrobotics/alice-agents",
-  "version": "1.2.1",
+  "version": "1.2.3",
   "description": "A.L.I.C.E. — 28 AI agents for OpenClaw. One conversation, one team.",
   "bin": {
     "alice-agents": "bin/alice-install.mjs"

package/templates/skills/claude-code/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: claude-code
+description: 'Delegate implementation tasks to Claude Code. Use when: (1) building new features or apps, (2) porting/refactoring code across multiple files, (3) fixing bugs that require file exploration, (4) any coding task that needs read+write+exec across a codebase. NOT for: planning/research (do that yourself), simple single-line edits (use edit tool directly), reading files (use read tool). Always give Claude Code a working directory and a precise task. Use background:true for long tasks and poll for completion.'
+metadata:
+  {
+    "openclaw": { "emoji": "⚡", "requires": { "anyBins": ["claude"] } }
+  }
+---
+
+# Claude Code Skill
+
+Runs Claude Code (`claude` CLI) in `--print --permission-mode bypassPermissions` mode.
+No PTY needed. Fully autonomous — reads, writes, edits, runs shell commands.
+
+## When to use this skill
+
+Use Claude Code when the task requires:
+- Creating or modifying **multiple files**
+- Running **build/test/lint** commands to verify correctness
+- Exploring an unfamiliar codebase before writing
+- Any implementation work that would take you many tool calls
+
+## Basic pattern
+
+```
+exec:
+  workdir: /path/to/project
+  command: claude --permission-mode bypassPermissions --print 'YOUR TASK HERE'
+```
+
+## Background pattern (for long tasks)
+
+```
+exec:
+  workdir: /path/to/project
+  background: true
+  command: claude --permission-mode bypassPermissions --print 'YOUR TASK HERE.
+
+When done, run: openclaw system event --text "Done: brief summary" --mode now'
+```
+
+Then poll with `process(action=log, sessionId=...)` to check progress.
+
+## Writing good prompts for Claude Code
+
+1. **Start with context** — tell it what the project is and what exists
+2. **Be specific** — name exact files, functions, behaviors expected
+3. **State success criteria** — "run npm run build and it must pass"
+4. **End with notification** — always append the `openclaw system event` line for long tasks
+
+## Example: Feature build
+
+```
+exec:
+  workdir: /Users/aliceclaw/.openclaw/workspace-olivia/mission-control
+  background: true
+  command: >
+    claude --permission-mode bypassPermissions --print '
+    This is a Next.js 16 + TypeScript + shadcn/ui app.
+    
+    Task: Add an AgentWizard modal to src/app/agents/page.tsx.
+    - Read src/app/agents/page.tsx first
+    - Read src/components/ui/ to see available components
+    - Build a multi-step Dialog: name → domain → preview → confirm
+    - On confirm, POST /api/agents with the form data
+    - The page should refresh the agent list after creation
+    
+    Run npm run build at the end and fix any TypeScript errors.
+    
+    When done: openclaw system event --text "AgentWizard complete" --mode now
+    '
+```
+
+## Example: Bug fix
+
+```
+exec:
+  workdir: /path/to/project
+  command: claude --permission-mode bypassPermissions --print 'Fix the TypeScript error in src/lib/openclaw.ts line 42. Run npm run build to verify.'
+```
+
+## Example: Code review
+
+```
+exec:
+  workdir: /path/to/project
+  command: claude --permission-mode bypassPermissions --print 'Review src/app/agents/page.tsx for bugs, performance issues, and missing error handling. Output a numbered list of findings.'
+```
+
+## Rules for agents using this skill
+
+1. **Give a precise workdir** — Claude Code needs to know where it is
+2. **One task per invocation** — don't chain unrelated work in one prompt
+3. **Always verify** — ask Claude Code to run the build/tests before finishing
+4. **Background for >5min tasks** — use background:true and the notification line
+5. **Report results** — after Claude Code finishes, summarize what changed to Olivia
+6. **Never run in ~/.openclaw/ itself** — always in a project subdirectory
+
+## Agents authorized to use this skill
+
+All coding specialists: dylan, felix, isaac, caleb, darius, avery, devon, quinn, alex
+Orchestrator: olivia (for coordination tasks only)
+
+## Checking if claude is available
+
+```
+exec:
+  command: which claude && claude --version
+```
+
+If not found, tell Olivia — she'll handle escalation.

package/templates/workspaces/_shared/AGENTS-orchestrator.md

@@ -43,3 +43,34 @@ When responding to {{userName}}:
 - Don't do specialist work yourself — delegate it
 - Don't overwhelm {{userName}} with internal coordination details
 - Don't run destructive commands without explicit risk callout
+
+## Team-First Rule
+
+**Always route through the team before doing specialist work yourself.**
+
+Before spawning Claude Code directly or writing implementation code yourself:
+1. Identify which specialists own the domains involved
+2. Spawn them to spec, plan, or execute — then synthesize their output
+3. Only fall back to direct Claude Code if genuinely no specialist covers it
+
+### Domain routing map
+- **UI/design** → Nadia (design spec) → Felix (implementation) → Quinn (QA)
+- **Product/copy/positioning** → Morgan
+- **Backend/API/data** → Dylan
+- **Security/auth** → Selena
+- **Ops/infra/DevOps** → Owen
+- **Testing/QA** → Quinn
+- **Documentation** → Daphne
+- **Research/analysis** → Uma
+
+### Correct pattern for UI work
+1. Nadia specs the design (reads existing code, produces page-by-page UX spec)
+2. Morgan provides product positioning and copy direction
+3. Felix implements using Claude Code with Nadia's spec as the brief
+4. Quinn does a visual/functional QA pass
+5. Olivia synthesizes and presents to Rob
+
+**Wrong:** Olivia spawns Claude Code directly for UI without involving Nadia or Felix
+**Right:** Nadia → Felix → Claude Code → Quinn → Olivia
+
+This applies to every non-trivial request. Always ask: "who on the team owns this domain?"

package/templates/workspaces/_shared/PLAYBOOK.md

@@ -5,3 +5,18 @@ _Promoted from LEARNINGS.md — patterns that work consistently._
 ---
 
 _No entries yet. As you learn what works, promote reusable patterns here._
+
+## Delegation Patterns (default)
+
+- **UI/UX work** → Nadia (design) + Morgan (product) → Felix (implements) → Quinn (QA)
+- **Backend/API** → Dylan → Claude Code → Quinn (tests)
+- **Security review** → Selena first, always
+- **Full-stack builds** → Dylan + Felix + Quinn in parallel
+- **Research** → Uma for analysis, Morgan for positioning
+
+## Anti-Patterns (avoid these)
+
+- Don't spawn Claude Code directly for design work — route through Nadia first
+- Don't do specialist work yourself — if someone owns the domain, spawn them
+- Don't iterate on UI without a design spec
+- Don't ship without a QA pass from Quinn