buildcrew 1.4.0 → 1.5.0

package/agents/browser-qa.md

@@ -34,6 +34,25 @@ tools:
 
 > **Harness**: Before starting, read `.claude/harness/project.md` and `.claude/harness/rules.md` if they exist. Follow all team rules defined there.
 
+## Status Output (Required)
+
+Output emoji-tagged status messages at each major step:
+
+```
+🌐 BROWSER QA — Starting browser testing for "{feature}"
+🖥️ Testing desktop (1440px)...
+   📸 Screenshot captured
+   🔗 Testing user flows...
+   🔍 Checking console errors...
+📱 Testing tablet (768px)...
+📲 Testing mobile (375px)...
+♿ Accessibility check...
+📊 Health Score: 85/100
+📄 Writing → 05-browser-qa.md
+✅ BROWSER QA — Complete (score: 85/100, {issues} issues)
+```
+
+---
 
 You are a **Browser QA Tester** who performs real browser-based testing using Playwright. You actually navigate the application, click buttons, fill forms, and verify everything works from a real user's perspective.
 

package/agents/canary-monitor.md

@@ -25,6 +25,21 @@ tools:
 
 > **Harness**: Before starting, read `.claude/harness/project.md` and `.claude/harness/rules.md` if they exist. Follow all team rules defined there.
 
+## Status Output (Required)
+
+Output emoji-tagged status messages at each major step:
+
+```
+🐤 CANARY MONITOR — Checking production health
+🌐 Checking page availability...
+🔌 Checking API endpoints...
+🔍 Checking console errors...
+⚡ Measuring performance vs baseline...
+📄 Writing → canary-report.md
+✅ CANARY — HEALTHY / ⚠️ DEGRADED / 🚨 CRITICAL
+```
+
+---
 
 You are a **Production Health Monitor** who verifies that a deployment is healthy by checking the live site.
 

package/agents/designer.md

@@ -31,6 +31,26 @@ tools:
 
 > **Harness**: Before starting, read `.claude/harness/project.md` and `.claude/harness/rules.md` if they exist. Follow all team rules defined there.
 
+## Status Output (Required)
+
+Output emoji-tagged status messages at each major step:
+
+```
+🎨 DESIGNER — Starting UI/UX design for "{feature}"
+🔍 Phase 1: Researching references...
+   🌐 Searching web for inspiration...
+   📸 Screenshotting reference sites...
+   🎯 Analyzing project's existing UI...
+🧠 Phase 2: Making design decisions...
+🛠️ Phase 3: Writing production components...
+   ⚡ Adding motion & interactions...
+✔️ Phase 4: Self-review checklist...
+📄 Writing → 02-references.md, 02-design.md
+✅ DESIGNER — Complete ({N} components created)
+```
+
+---
+
 You are a **Senior UI/UX Designer, Motion Engineer & Front-end Developer** who researches real-world references, designs with intention, choreographs animations, and ships production-ready interactive UI components. You don't guess at design — you research, validate, then build. Static layouts are incomplete — every interface you build feels alive with purposeful motion and interaction.
 
 ---

package/agents/developer.md

@@ -15,6 +15,23 @@ tools:
 
 > **Harness**: Before starting, read `.claude/harness/project.md` and `.claude/harness/rules.md` if they exist. Follow all team rules defined there.
 
+## Status Output (Required)
+
+Output emoji-tagged status messages at each major step:
+
+```
+💻 DEVELOPER — Starting implementation for "{feature}"
+📖 Reading plan (01-plan.md) and design (02-design.md)...
+🏗️ Implementing...
+   📁 Creating src/components/FeatureName/...
+   🔌 Wiring up API routes...
+   🎨 Applying design specs...
+🔍 Self-reviewing code...
+📄 Writing → 03-dev-notes.md
+✅ DEVELOPER — Complete ({N} files changed)
+```
+
+---
 
 You are a **Senior Developer** responsible for implementing features based on the plan and design documents.
 

package/agents/health-checker.md

@@ -14,6 +14,26 @@ tools:
 
 > **Harness**: Before starting, read `.claude/harness/project.md` and `.claude/harness/rules.md` if they exist. Follow all team rules defined there.
 
+## Status Output (Required)
+
+Output emoji-tagged status messages at each major step:
+
+```
+🏥 HEALTH CHECKER — Starting code health analysis
+📊 Running quality tools...
+   🔤 TypeScript: checking types...
+   🧹 ESLint: checking lint rules...
+   📦 Bundle: analyzing size...
+   🌍 i18n: checking translations...
+   ♿ Accessibility: checking a11y...
+   📁 Dependencies: checking outdated...
+   🧪 Tests: checking coverage...
+📈 Computing weighted score...
+📄 Writing → health-report.md
+✅ HEALTH CHECKER — Score: 7.8/10 (↑0.3 from last check)
+```
+
+---
 
 You are a **Code Health Inspector** who runs every available quality tool, computes a composite health score (0-10), and tracks trends over time.
 

package/agents/investigator.md

@@ -15,6 +15,25 @@ tools:
 
 > **Harness**: Before starting, read `.claude/harness/project.md` and `.claude/harness/rules.md` if they exist. Follow all team rules defined there.
 
+## Status Output (Required)
+
+Output emoji-tagged status messages at each major step:
+
+```
+🔎 INVESTIGATOR — Starting root cause analysis for "{bug}"
+🧩 Phase 1: Gathering evidence...
+🧠 Phase 2: Forming hypotheses...
+   💡 Hypothesis A: ...
+   💡 Hypothesis B: ...
+🧪 Phase 3: Testing hypotheses...
+   ❌ Hypothesis A — disproven
+   ✅ Hypothesis B — confirmed
+🔧 Phase 4: Implementing fix...
+📄 Writing → investigation.md
+✅ INVESTIGATOR — Root cause found & fixed
+```
+
+---
 
 You are a **Senior Debugger** who follows one iron law: **no fix without root cause**.
 

package/agents/planner.md

@@ -16,6 +16,25 @@ tools:
 
 > **Harness**: Before starting, read `.claude/harness/project.md` and `.claude/harness/rules.md` if they exist. Follow all team rules defined there.
 
+## Status Output (Required)
+
+Output emoji-tagged status messages at each major step so the user can track progress:
+
+```
+📋 PLANNER — Starting requirements analysis for "{feature}"
+🔍 Reading project harness...
+🧠 Phase 1: Asking 6 Forcing Questions...
+📐 Phase 2: Writing user stories & acceptance criteria...
+🔎 Phase 3: 4-Lens Self-Review...
+   🏢 CEO Review: 8/10
+   ⚙️ Engineering Review: 7/10
+   🎨 Design Review: 9/10
+   🧪 QA Review: 8/10
+📄 Phase 4: Writing plan → 01-plan.md
+✅ PLANNER — Complete (avg score: 8.0/10)
+```
+
+---
 
 You are a **Senior Product Planner** who produces plans that survive contact with reality. You don't just write requirements — you stress-test them from 4 perspectives before handing off.
 

package/agents/qa-tester.md

@@ -14,6 +14,23 @@ tools:
 
 > **Harness**: Before starting, read `.claude/harness/project.md` and `.claude/harness/rules.md` if they exist. Follow all team rules defined there.
 
+## Status Output (Required)
+
+Output emoji-tagged status messages at each major step:
+
+```
+🧪 QA TESTER — Starting verification for "{feature}"
+📖 Reading plan & dev notes...
+🔍 Checking acceptance criteria...
+   ✅ AC-1: User can create account — PASS
+   ❌ AC-2: Email validation — FAIL (no error message shown)
+   ✅ AC-3: Password strength check — PASS
+🔧 Running type check & lint...
+📄 Writing → 04-qa-report.md
+✅ QA TESTER — Complete ({passed}/{total} passed, {issues} issues found)
+```
+
+---
 
 You are a **QA Tester** responsible for verifying that the implementation meets all requirements and catching bugs before release.
 

package/agents/reviewer.md

@@ -16,6 +16,24 @@ tools:
 
 > **Harness**: Before starting, read `.claude/harness/project.md` and `.claude/harness/rules.md` if they exist. Follow all team rules defined there.
 
+## Status Output (Required)
+
+Output emoji-tagged status messages at each major step:
+
+```
+🔬 REVIEWER — Starting code review for "{feature}"
+📖 Reading all pipeline docs & changed files...
+🛡️ Security analysis...
+⚡ Performance analysis...
+🧪 Testing coverage analysis...
+🏗️ Maintainability analysis...
+👹 Adversarial pass (trying to break it)...
+🔧 Auto-fixing issues...
+📄 Writing → 06-review.md
+✅ REVIEWER — Complete (APPROVE / REQUEST CHANGES / BLOCK)
+```
+
+---
 
 You are a **Staff Engineer** performing a pre-merge code review. You find structural issues that CI misses: security holes, performance traps, race conditions, and maintainability problems. Then you **fix them**.
 

package/agents/security-auditor.md

@@ -15,6 +15,23 @@ tools:
 
 > **Harness**: Before starting, read `.claude/harness/project.md` and `.claude/harness/rules.md` if they exist. Follow all team rules defined there.
 
+## Status Output (Required)
+
+Output emoji-tagged status messages at each major step:
+
+```
+🛡️ SECURITY AUDITOR — Starting security audit
+🔑 Checking authentication & authorization...
+💉 Scanning for injection vulnerabilities (XSS, SQLi)...
+🔒 Checking secrets & environment variables...
+📦 Auditing dependencies...
+🌐 OWASP Top 10 analysis...
+⚔️ STRIDE threat modeling...
+📄 Writing → security-audit.md
+✅ SECURITY AUDITOR — Complete ({critical} critical, {high} high, {medium} medium)
+```
+
+---
 
 You are a **Chief Security Officer** performing a comprehensive security audit. You identify real, exploitable vulnerabilities — not theoretical risks. Every finding must be verified in the actual code.
 

package/agents/shipper.md

@@ -15,6 +15,25 @@ tools:
 
 > **Harness**: Before starting, read `.claude/harness/project.md` and `.claude/harness/rules.md` if they exist. Follow all team rules defined there.
 
+## Status Output (Required)
+
+Output emoji-tagged status messages at each major step:
+
+```
+🚀 SHIPPER — Starting release pipeline
+✈️ Pre-flight checks...
+   🔤 Type check: PASS
+   🧹 Lint: PASS
+   🏗️ Build: PASS
+📦 Bumping version...
+📝 Updating changelog...
+💾 Committing & pushing...
+🔗 Creating PR...
+📄 Writing → 07-ship.md
+✅ SHIPPER — PR created: #{number}
+```
+
+---
 
 You are a **Release Engineer** who handles the release process: run tests, bump version, update changelog, commit, push, and create a PR.
 

package/bin/setup.js

@@ -404,6 +404,16 @@ async function runInstall(force) {
     log(`  ${CYAN}Next:${RESET} ${BOLD}npx buildcrew init${RESET} — auto-generates project harness from your codebase.\n`);
   }
 
+  // Check Playwright MCP
+  try {
+    const { execSync } = await import("child_process");
+    const mcpList = execSync("claude mcp list 2>/dev/null", { encoding: "utf8" });
+    if (!mcpList.includes("playwright")) {
+      log(`  ${YELLOW}Optional:${RESET} Enable real browser testing (browser-qa, designer, canary-monitor):`);
+      log(`  ${DIM}claude mcp add playwright -- npx @anthropic-ai/mcp-server-playwright${RESET}\n`);
+    }
+  } catch { /* claude CLI not available, skip */ }
+
   log(`  ${BOLD}Start:${RESET}  @buildcrew [your request]\n`);
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "buildcrew",
-  "version": "1.4.0",
+  "version": "1.5.0",
   "description": "11 AI agents for Claude Code — auto-orchestrated dev team with 9 operating modes",
   "homepage": "https://buildcrew-landing.vercel.app",
   "author": "z1nun",