JeremyDev87 · JeremyDev87 · Apr 4, 2026 · Apr 4, 2026 · Apr 4, 2026
@@ -4,6 +4,7 @@
   "color": "#27AE60",
   "role": {
     "title": "Accessibility Engineer",
+    "type": "specialist",
     "expertise": [
       "WCAG 2.1 AA compliance planning and verification",
       "ARIA attributes planning and verification",

@@ -4,6 +4,7 @@
   "color": "#82B366",
   "role": {
     "title": "Act Mode Agent",
+    "type": "utility",
     "mode": "ACT",
     "purpose": "Mode Agent - delegates to Primary Developer Agent",
     "expertise": [

@@ -4,6 +4,7 @@
   "color": "#2C3E80",
   "role": {
     "title": "Architecture Engineer",
+    "type": "specialist",
     "expertise": [
       "Layer placement planning and verification",
       "Dependency direction design and verification",

@@ -4,6 +4,7 @@
   "color": "#B85450",
   "role": {
     "title": "Auto Mode Agent",
+    "type": "utility",
     "mode": "AUTO",
     "purpose": "Mode Agent - autonomously cycles through PLAN → ACT → EVAL, delegates to Primary Developer Agent",
     "expertise": [

@@ -4,6 +4,7 @@
   "color": "#8BC34A",
   "role": {
     "title": "Code Quality Engineer",
+    "type": "specialist",
     "expertise": [
       "SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion)",
       "DRY (Don't Repeat Yourself) principle",

@@ -4,6 +4,7 @@
   "color": "#673AB7",
   "role": {
     "title": "Senior Code Reviewer / Quality Engineer",
+    "type": "specialist",
     "expertise": [
       "Multi-dimensional code quality evaluation",
       "Architecture and design pattern analysis",

@@ -4,6 +4,7 @@
   "color": "#607D8B",
   "role": {
     "title": "Documentation Engineer",
+    "type": "specialist",
     "expertise": [
       "Documentation planning and quality assessment",
       "Code comments planning and verification",

@@ -4,6 +4,7 @@
   "color": "#D4A843",
   "role": {
     "title": "Eval Mode Agent",
+    "type": "utility",
     "mode": "EVAL",
     "purpose": "Mode Agent - delegates to Code Reviewer Agent",
     "expertise": [

@@ -4,6 +4,7 @@
   "color": "#FF5722",
   "role": {
     "title": "Event Architecture Engineer",
+    "type": "specialist",
     "expertise": [
       "Message Queue Selection and Configuration (RabbitMQ, Kafka, SQS, Azure Service Bus)",
       "Event Sourcing and Event Store Design",

@@ -4,6 +4,7 @@
   "color": "#009688",
   "role": {
     "title": "Internationalization Engineer",
+    "type": "specialist",
     "expertise": [
       "i18n library setup and configuration",
       "Translation key structure design",

@@ -4,6 +4,7 @@
   "color": "#00BCD4",
   "role": {
     "title": "Integration Engineer",
+    "type": "specialist",
     "expertise": [
       "API Integration Patterns (retries, timeouts, circuit breakers)",
       "Webhook Security (HMAC, JWT signature verification)",

@@ -4,6 +4,7 @@
   "color": "#795548",
   "role": {
     "title": "Observability Engineer",
+    "type": "specialist",
     "expertise": [
       "OpenTelemetry instrumentation (traces, metrics, logs)",
       "Distributed tracing (Jaeger, Zipkin, Tempo, Grafana Tempo)",

@@ -4,6 +4,7 @@
   "color": "#E67E22",
   "role": {
     "title": "Performance Engineer",
+    "type": "specialist",
     "expertise": [
       "Bundle size optimization planning and verification",
       "Code splitting strategy planning and verification",

@@ -5,6 +5,7 @@
   "systemPrompt": "You are a Plan Mode Agent that follows a structured reasoning process for every planning task.\n\n## Structured Reasoning Process (MANDATORY)\n\nBefore producing any plan, you MUST complete all five steps in order:\n\n### Step 0: Research\nRead relevant source code, configuration files, and documentation BEFORE planning.\n- NEVER plan from memory alone — always verify current state by reading files.\n- Identify existing patterns, conventions, and dependencies in the codebase.\n- Check recent git history for related changes.\n\n### Step 1: Decompose\nBreak the problem into discrete sub-problems.\n- Each sub-problem should be independently understandable.\n- Identify dependencies between sub-problems.\n- Order sub-problems by dependency (independent first, dependent last).\n\n### Step 2: Design\nCreate a concrete solution for each sub-problem.\n- Specify exact file paths, function names, and data structures.\n- Define the TDD approach: which tests to write first, expected failures, minimal implementations.\n- Ensure each solution is minimal — YAGNI applies.\n\n### Step 3: Devil's Advocate\nActively argue against your own plan.\n- What could go wrong? What edge cases are missed?\n- Are there simpler alternatives you overlooked?\n- Does the plan introduce unnecessary complexity or coupling?\n- Would this plan survive a critical code review?\n- Document weaknesses found and how the plan addresses them.\n\n### Step 4: Verify\nAll file paths and references in the plan MUST be verified against the actual codebase.\n- Confirmed paths: mark as-is.\n- Unconfirmed paths (not yet verified or file does not exist yet): mark with ⚠️ UNVERIFIED.\n- New files to be created: mark with 🆕 NEW.\n- NEVER assume a file exists without checking.",
   "role": {
     "title": "Plan Mode Agent",
+    "type": "utility",
     "mode": "PLAN",
     "purpose": "Mode Agent - delegates to Primary Developer Agent",
     "expertise": [

@@ -4,6 +4,7 @@
   "color": "#C0392B",
   "role": {
     "title": "Security Engineer",
+    "type": "specialist",
     "expertise": [
       "OAuth 2.0 / OIDC protocols",
       "JWT token management and security",

@@ -4,6 +4,7 @@
   "color": "#16A085",
   "role": {
     "title": "SEO Engineer",
+    "type": "specialist",
     "expertise": [
       "Next.js Metadata API planning and verification",
       "Structured data (JSON-LD) planning and verification",

@@ -4,6 +4,7 @@
   "color": "#F1C40F",
   "role": {
     "title": "Test Strategy Engineer",
+    "type": "specialist",
     "expertise": [
       "TDD vs Test-After decision making and verification",
       "Test coverage planning and analysis (90%+ goal)",

@@ -4,6 +4,7 @@
   "color": "#E91E63",
   "role": {
     "title": "UI/UX Design Specialist",
+    "type": "specialist",
     "expertise": [
       "Visual Design Principles",
       "User Experience Patterns",

@@ -43,8 +43,8 @@
         },
         "type": {
           "type": "string",
-          "enum": ["primary", "specialist"],
-          "description": "Agent type: 'primary' uses top-level activation for PLAN/ACT workflow, 'specialist' uses modes for domain-specific guidance. RECOMMENDED: Always specify for new agents to ensure proper workflow integration."
+          "enum": ["primary", "specialist", "utility"],
+          "description": "Agent type: 'primary' uses top-level activation for PLAN/ACT workflow, 'specialist' uses modes for domain-specific guidance, 'utility' is for mode agents (PLAN/ACT/EVAL/AUTO). RECOMMENDED: Always specify for new agents to ensure proper workflow integration."
         },
         "expertise": {
           "type": "array",