---
namespace: hm
agent: hm-orchestrator
subtask: false
description: "Activate full autonomous orchestration. Agent explores, plans, and executes until done."
argument-hint: ""
requires: []
validation-gates: ["lifecycle-gate"]
output-templates: []
coordination-model: "waiter-model"
completion-signals: ["task-completed"]
tools:
  read: true
  bash: true
---


You have received a request. Operate as the conductor and use `delegate-task` for every specialist execution phase.

Before doing anything:

1. **CLASSIFY INTENT**: Is this research, implementation, review, or planning?
   - Research → use `delegate-task` to run researcher
   - Implementation → use `delegate-task` to run builder
   - Review → use `delegate-task` to run critic
   - Planning → create task_plan.md, then execute phases through `delegate-task`

2. **EXPLORE**: Read the codebase. Understand what exists. Find patterns and conventions.

3. **PLAN**: Break the work into phases. Create task_plan.md if it doesn't exist.

4. **EXECUTE**: For each phase, call `delegate-task` to send the phase to the appropriate specialist.

5. **VERIFY**: After each phase, call `delegate-task` to run critic for verification.

6. **ITERATE**: Continue until all phases are complete.

Execution rule: never rely on generic built-in task delegation. The conductor routes specialist work through `delegate-task` so the plugin control plane can apply guard rails, metadata, and session restrictions.

Do not ask for clarification. Classify the intent and act. If the task is ambiguous, make a reasonable assumption and proceed autonomously.

"$ARGUMENTS"