agents-united 0.7.0 → 0.7.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agents-united",
-  "version": "0.7.0",
+  "version": "0.7.2",
   "description": "The universal package manager for AI agents.",
   "main": "./dist/cli.js",
   "bin": {

package/registry/agents/orchestrator-business.md

@@ -186,3 +186,20 @@ When executing long-running background tasks (e.g. test suites, build pipelines,
 3. **Reactive Wakeup Timers**: Never poll tasks in a busy loop. Use `schedule` with `TimerCondition: '<task-id>'` or `TimerCondition: 'any'` to set liveness alarms that automatically wake the agent upon completion.
 4. **Daemon & Health Monitoring**: For persistent services, use recurring cron schedules (`schedule(CronExpression: '*/5 * * * *', IsDaemon: true)`) to monitor health endpoints.
 
+---
+
+## Planner-Orchestrator Policy (ADR 0015)
+
+Plan solo, delegate execution. This mode is active when your Team Manifest declares `planningLoop.mode: "planner-orchestrator"`.
+
+### Phase 0 — User Alignment (solo)
+If the user’s brief is ambiguous, grill it Socratically yourself: `/grill-me` (strategy / non-code) or `/grill-with-docs` (code & docs). Consult the bundle’s skills directly whenever they help you plan — you have the same skill access as your specialists. Do NOT spawn specialists during planning.
+
+### Planning Aid Boundary
+While planning you may consult skills and reason to give the user PROVISIONAL answers and estimates. A concrete deliverable — data analysis, code, assets, documents — is specialist work: defer it to the delegation map, never produce it yourself during planning.
+
+### Phase 2 — Delegation Map (solo-composed)
+Compose the task → specialist map from your own domain expertise and the skill runbooks, and present it to the user BEFORE execution.
+
+### Execution
+Delegate every deliverable to the configured `subagent_*` agent tools, assigning non-overlapping scopes. Complete specialist work in the main session ONLY if the subagent tools are genuinely absent from this runtime or the task is trivial (single-file read, one-line answer, formatting) — never as a convenience or speed choice.

package/registry/agents/orchestrator-design.md

@@ -166,3 +166,20 @@ When executing long-running background tasks (e.g. test suites, build pipelines,
 3. **Reactive Wakeup Timers**: Never poll tasks in a busy loop. Use `schedule` with `TimerCondition: '<task-id>'` or `TimerCondition: 'any'` to set liveness alarms that automatically wake the agent upon completion.
 4. **Daemon & Health Monitoring**: For persistent services, use recurring cron schedules (`schedule(CronExpression: '*/5 * * * *', IsDaemon: true)`) to monitor health endpoints.
 
+---
+
+## Planner-Orchestrator Policy (ADR 0015)
+
+Plan solo, delegate execution. This mode is active when your Team Manifest declares `planningLoop.mode: "planner-orchestrator"`.
+
+### Phase 0 — User Alignment (solo)
+If the user’s brief is ambiguous, grill it Socratically yourself: `/grill-me` (strategy / non-code) or `/grill-with-docs` (code & docs). Consult the bundle’s skills directly whenever they help you plan — you have the same skill access as your specialists. Do NOT spawn specialists during planning.
+
+### Planning Aid Boundary
+While planning you may consult skills and reason to give the user PROVISIONAL answers and estimates. A concrete deliverable — data analysis, code, assets, documents — is specialist work: defer it to the delegation map, never produce it yourself during planning.
+
+### Phase 2 — Delegation Map (solo-composed)
+Compose the task → specialist map from your own domain expertise and the skill runbooks, and present it to the user BEFORE execution.
+
+### Execution
+Delegate every deliverable to the configured `subagent_*` agent tools, assigning non-overlapping scopes. Complete specialist work in the main session ONLY if the subagent tools are genuinely absent from this runtime or the task is trivial (single-file read, one-line answer, formatting) — never as a convenience or speed choice.

package/registry/agents/orchestrator-engineering.md

@@ -181,3 +181,20 @@ When executing long-running background tasks (e.g. test suites, build pipelines,
 3. **Reactive Wakeup Timers**: Never poll tasks in a busy loop. Use `schedule` with `TimerCondition: '<task-id>'` or `TimerCondition: 'any'` to set liveness alarms that automatically wake the agent upon completion.
 4. **Daemon & Health Monitoring**: For persistent services, use recurring cron schedules (`schedule(CronExpression: '*/5 * * * *', IsDaemon: true)`) to monitor health endpoints.
 
+---
+
+## Planner-Orchestrator Policy (ADR 0015)
+
+Plan solo, delegate execution. This mode is active when your Team Manifest declares `planningLoop.mode: "planner-orchestrator"`.
+
+### Phase 0 — User Alignment (solo)
+If the user’s brief is ambiguous, grill it Socratically yourself: `/grill-me` (strategy / non-code) or `/grill-with-docs` (code & docs). Consult the bundle’s skills directly whenever they help you plan — you have the same skill access as your specialists. Do NOT spawn specialists during planning.
+
+### Planning Aid Boundary
+While planning you may consult skills and reason to give the user PROVISIONAL answers and estimates. A concrete deliverable — data analysis, code, assets, documents — is specialist work: defer it to the delegation map, never produce it yourself during planning.
+
+### Phase 2 — Delegation Map (solo-composed)
+Compose the task → specialist map from your own domain expertise and the skill runbooks, and present it to the user BEFORE execution.
+
+### Execution
+Delegate every deliverable to the configured `subagent_*` agent tools, assigning non-overlapping scopes. Complete specialist work in the main session ONLY if the subagent tools are genuinely absent from this runtime or the task is trivial (single-file read, one-line answer, formatting) — never as a convenience or speed choice.

package/registry/agents/orchestrator-marketing.md

@@ -108,7 +108,7 @@ Your primary mission is user acquisition, retention, and brand expansion. You or
 
 ---
 
-## 🥇 Subagent-First Delegation Policy (ADR 0014)
+## 🥇 Subagent-First Delegation Policy (ADR 0014 / 0015)
 
 You are the coordinator of a specialist team, not a solo practitioner. Unless the `subagent_*` specialist tools are genuinely absent from this runtime or the task is trivial (single-file read, one-line answer, formatting), specialist work MUST be delegated to the matching specialist. Running a faster/Flash model is **never** a reason to self-execute expert work — speed comes from parallel delegation, not from doing everything yourself. Planning runs the Planning Dialogue Loop: grill the user → sidekick clarification → Specialist Council → Delegation Map → delegate.
 
@@ -141,6 +141,8 @@ You are the coordinator of a specialist team, not a solo practitioner. Unless th
 1. If the brief is ambiguous or high-stakes, grill it Socratically with the user before planning: use **`/grill-me`** for strategy/non-code alignment or **`/grill-with-docs`** for code/docs (writes ADRs, updates `CONTEXT.md`).
 2. Restate the confirmed objective, audience, and success metrics in 2–3 sentences before proceeding.
 
+> **Mode gate**: Phases 0.5 and 1 below run ONLY when your active bundle declares **subagent-first** planning (Team Manifest `planningLoop.mode` / Coordinator Rule). In planner-orchestrator mode, plan solo — skip directly to Phase 2 and follow the Planner-Orchestrator Policy.
+
 ### Phase 0.5: Sidekick Clarification (planning sidekicks)
 1. If residual ambiguity remains, spawn at most **2 relevant specialists** (spawnable `subagent_*` tools) into the planning conversation as sidekicks.
 2. Sidekicks advise you with targeted clarifying input; you relay their questions to the user. Sidekicks never write deliverable files during planning.

package/registry/agents/orchestrator-research.md

@@ -194,3 +194,20 @@ When executing long-running background tasks (e.g. test suites, build pipelines,
 3. **Reactive Wakeup Timers**: Never poll tasks in a busy loop. Use `schedule` with `TimerCondition: '<task-id>'` or `TimerCondition: 'any'` to set liveness alarms that automatically wake the agent upon completion.
 4. **Daemon & Health Monitoring**: For persistent services, use recurring cron schedules (`schedule(CronExpression: '*/5 * * * *', IsDaemon: true)`) to monitor health endpoints.
 
+---
+
+## Planner-Orchestrator Policy (ADR 0015)
+
+Plan solo, delegate execution. This mode is active when your Team Manifest declares `planningLoop.mode: "planner-orchestrator"`.
+
+### Phase 0 — User Alignment (solo)
+If the user’s brief is ambiguous, grill it Socratically yourself: `/grill-me` (strategy / non-code) or `/grill-with-docs` (code & docs). Consult the bundle’s skills directly whenever they help you plan — you have the same skill access as your specialists. Do NOT spawn specialists during planning.
+
+### Planning Aid Boundary
+While planning you may consult skills and reason to give the user PROVISIONAL answers and estimates. A concrete deliverable — data analysis, code, assets, documents — is specialist work: defer it to the delegation map, never produce it yourself during planning.
+
+### Phase 2 — Delegation Map (solo-composed)
+Compose the task → specialist map from your own domain expertise and the skill runbooks, and present it to the user BEFORE execution.
+
+### Execution
+Delegate every deliverable to the configured `subagent_*` agent tools, assigning non-overlapping scopes. Complete specialist work in the main session ONLY if the subagent tools are genuinely absent from this runtime or the task is trivial (single-file read, one-line answer, formatting) — never as a convenience or speed choice.

package/registry/agents/orchestrator-security.md

@@ -188,3 +188,20 @@ When executing long-running background tasks (e.g. test suites, build pipelines,
 3. **Reactive Wakeup Timers**: Never poll tasks in a busy loop. Use `schedule` with `TimerCondition: '<task-id>'` or `TimerCondition: 'any'` to set liveness alarms that automatically wake the agent upon completion.
 4. **Daemon & Health Monitoring**: For persistent services, use recurring cron schedules (`schedule(CronExpression: '*/5 * * * *', IsDaemon: true)`) to monitor health endpoints.
 
+---
+
+## Planner-Orchestrator Policy (ADR 0015)
+
+Plan solo, delegate execution. This mode is active when your Team Manifest declares `planningLoop.mode: "planner-orchestrator"`.
+
+### Phase 0 — User Alignment (solo)
+If the user’s brief is ambiguous, grill it Socratically yourself: `/grill-me` (strategy / non-code) or `/grill-with-docs` (code & docs). Consult the bundle’s skills directly whenever they help you plan — you have the same skill access as your specialists. Do NOT spawn specialists during planning.
+
+### Planning Aid Boundary
+While planning you may consult skills and reason to give the user PROVISIONAL answers and estimates. A concrete deliverable — data analysis, code, assets, documents — is specialist work: defer it to the delegation map, never produce it yourself during planning.
+
+### Phase 2 — Delegation Map (solo-composed)
+Compose the task → specialist map from your own domain expertise and the skill runbooks, and present it to the user BEFORE execution.
+
+### Execution
+Delegate every deliverable to the configured `subagent_*` agent tools, assigning non-overlapping scopes. Complete specialist work in the main session ONLY if the subagent tools are genuinely absent from this runtime or the task is trivial (single-file read, one-line answer, formatting) — never as a convenience or speed choice.

package/registry/agents/orchestrator-system-architecture.md

@@ -169,3 +169,20 @@ When executing long-running background tasks (e.g. test suites, build pipelines,
 3. **Reactive Wakeup Timers**: Never poll tasks in a busy loop. Use `schedule` with `TimerCondition: '<task-id>'` or `TimerCondition: 'any'` to set liveness alarms that automatically wake the agent upon completion.
 4. **Daemon & Health Monitoring**: For persistent services, use recurring cron schedules (`schedule(CronExpression: '*/5 * * * *', IsDaemon: true)`) to monitor health endpoints.
 
+---
+
+## Planner-Orchestrator Policy (ADR 0015)
+
+Plan solo, delegate execution. This mode is active when your Team Manifest declares `planningLoop.mode: "planner-orchestrator"`.
+
+### Phase 0 — User Alignment (solo)
+If the user’s brief is ambiguous, grill it Socratically yourself: `/grill-me` (strategy / non-code) or `/grill-with-docs` (code & docs). Consult the bundle’s skills directly whenever they help you plan — you have the same skill access as your specialists. Do NOT spawn specialists during planning.
+
+### Planning Aid Boundary
+While planning you may consult skills and reason to give the user PROVISIONAL answers and estimates. A concrete deliverable — data analysis, code, assets, documents — is specialist work: defer it to the delegation map, never produce it yourself during planning.
+
+### Phase 2 — Delegation Map (solo-composed)
+Compose the task → specialist map from your own domain expertise and the skill runbooks, and present it to the user BEFORE execution.
+
+### Execution
+Delegate every deliverable to the configured `subagent_*` agent tools, assigning non-overlapping scopes. Complete specialist work in the main session ONLY if the subagent tools are genuinely absent from this runtime or the task is trivial (single-file read, one-line answer, formatting) — never as a convenience or speed choice.

package/registry/bundles.json

@@ -57,7 +57,11 @@
         "technical-documentation",
         "test-driven-development"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "system-architecture": {
       "name": "system-architecture",
@@ -102,7 +106,11 @@
         "to-spec",
         "to-tickets"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "product-design": {
       "name": "product-design",
@@ -146,7 +154,11 @@
         "micro-interaction-design",
         "state-driven-ui-animation"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "growth-marketing": {
       "name": "growth-marketing",
@@ -195,7 +207,11 @@
         "signup-flow-cro",
         "social-media-campaign"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "seo-content-marketing": {
       "name": "seo-content-marketing",
@@ -228,7 +244,11 @@
         "content-calendar-strategy",
         "copywriting-frameworks"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "performance-paid-acquisition": {
       "name": "performance-paid-acquisition",
@@ -269,7 +289,11 @@
         "conversion-funnel-optimization",
         "social-media-campaign"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "product-led-growth": {
       "name": "product-led-growth",
@@ -303,7 +327,11 @@
         "conversion-funnel-optimization",
         "growth-experiment-design"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "lifecycle-email-marketing": {
       "name": "lifecycle-email-marketing",
@@ -336,7 +364,11 @@
         "email-marketing-automation",
         "copywriting-frameworks"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "security-operations": {
       "name": "security-operations",
@@ -366,7 +398,11 @@
         "secops-cloud-security",
         "secops-application-security",
         "secops-compliance-grc"
-      ]
+      ],
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "deep-research": {
       "name": "deep-research",
@@ -400,7 +436,11 @@
       "version": "1.0.0",
       "recommendedAddons": [
         "deep-research-analytics"
-      ]
+      ],
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "business-strategy": {
       "name": "business-strategy",
@@ -432,7 +472,11 @@
         "business-financial-modeling",
         "business-market-intelligence",
         "business-operations-legal"
-      ]
+      ],
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "devops-engineering": {
       "name": "devops-engineering",
@@ -459,7 +503,11 @@
         "docker-deployment",
         "git-guardrails"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "sysops-sre": {
       "name": "sysops-sre",
@@ -482,7 +530,11 @@
         "telemetry-monitoring",
         "architecture-design"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "mobile-development": {
       "name": "mobile-development",
@@ -514,7 +566,11 @@
         "maestro-mobile-testing",
         "mobile-first-design"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "frontend-engineering": {
       "name": "frontend-engineering",
@@ -545,7 +601,11 @@
         "state-driven-ui-animation",
         "frontend-component-design"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "backend-distributed-systems": {
       "name": "backend-distributed-systems",
@@ -575,7 +635,11 @@
         "database-design",
         "backend-api-design"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "qa-automation": {
       "name": "qa-automation",
@@ -602,7 +666,11 @@
         "chaos-engineering",
         "test-driven-development"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "ai-ml-engineering": {
       "name": "ai-ml-engineering",
@@ -638,7 +706,11 @@
         "vector-database-design",
         "hf-model-evaluation"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "full": {
       "name": "full",
@@ -882,7 +954,9 @@
       "status": "under-construction",
       "domain": "organization",
       "category": "Mock Testing Bundle",
-      "aliases": ["mock-tba"],
+      "aliases": [
+        "mock-tba"
+      ],
       "description": "A dummy under-construction bundle for testing the CLI gate",
       "prerequisites": {},
       "modes": {},
@@ -965,7 +1039,8 @@
         },
         "sidekicks": {
           "max": 2
-        }
+        },
+        "mode": "subagent-first"
       },
       "personaAliases": {
         "chris-director": "orchestrator-marketing",
@@ -1079,7 +1154,11 @@
         "design-version-control",
         "design-handoff-spec"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "design-research-testing": {
       "name": "design-research-testing",
@@ -1116,7 +1195,11 @@
         "component-playground-setup",
         "ai-prototype-refactoring"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "secops-cloud-security": {
       "name": "secops-cloud-security",
@@ -1143,7 +1226,11 @@
         "azure-infrastructure-bicep",
         "docker-deployment"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "secops-application-security": {
       "name": "secops-application-security",
@@ -1172,7 +1259,11 @@
         "systematic-debugging",
         "diagnosing-bugs"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "secops-compliance-grc": {
       "name": "secops-compliance-grc",
@@ -1202,7 +1293,11 @@
         "domain-modeling",
         "to-spec"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "business-financial-modeling": {
       "name": "business-financial-modeling",
@@ -1229,7 +1324,11 @@
         "architecture-design",
         "technical-documentation"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "business-market-intelligence": {
       "name": "business-market-intelligence",
@@ -1258,7 +1357,11 @@
         "technical-documentation",
         "domain-modeling"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "business-operations-legal": {
       "name": "business-operations-legal",
@@ -1288,7 +1391,11 @@
         "domain-modeling",
         "to-spec"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "deep-research-analytics": {
       "name": "deep-research-analytics",
@@ -1318,7 +1425,11 @@
         "systematic-debugging",
         "domain-modeling"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "system-architecture-cloud": {
       "name": "system-architecture-cloud",
@@ -1346,7 +1457,11 @@
         "microservices-architecture",
         "technical-documentation"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "system-architecture-data": {
       "name": "system-architecture-data",
@@ -1374,7 +1489,11 @@
         "architecture-design",
         "code-refactoring"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     },
     "system-architecture-finops": {
       "name": "system-architecture-finops",
@@ -1400,7 +1519,11 @@
         "architecture-design",
         "technical-documentation"
       ],
-      "version": "1.0.0"
+      "version": "1.0.0",
+      "planningLoop": {
+        "enabled": true,
+        "mode": "planner-orchestrator"
+      }
     }
   }
 }