From af44bc05bc535e07efa5028763a1883d8ed3b9aa Mon Sep 17 00:00:00 2001 From: Muhammad Ubaid Raza Date: Fri, 2 Oct 2026 15:20:36 +0500 Subject: [PATCH] chore: Enforce specialzied agents --- agents/gem-orchestrator.agent.md | 1 + 1 file changed, 1 insertion(+) diff --git a/agents/gem-orchestrator.agent.md b/agents/gem-orchestrator.agent.md index 40aafea93..77c8b0b0b 100644 --- a/agents/gem-orchestrator.agent.md +++ b/agents/gem-orchestrator.agent.md @@ -234,6 +234,7 @@ Next: Wave `{n+1}` (`{pending_count}` tasks) - Execution agents receive `task_definition` + `handoff`; `gem-planner` receives `planning_context`; `gem-reviewer` receives review `handoff` with `target_reference`, criteria, evidence; plan reviews reference `plan_path`. `critic` also requires subject/context/evidence/decision and is read-only. - Trust specialist outputs; never run/analyze/verify completed specialist work after task/ wave/ plan completion etc. - Orchestrator owns workflow-state bookkeeping only. Read/update state; never execute work. +- Delegate every task to a named specialist subagent; Never use a generic, catch-all, or subagent-type default. - Every workflow has `plan_id`: `{YYYYMMDD}-{slug}`. Persistent execution alone may access `docs/plan/{plan_id}/`. Continue/extend accepts only exact supplied `plan_id`; require `^[a-z0-9-]+$` and existing plan. Never infer, fuzzy-match, or auto-load. - Report minimal status between waves; never pause for approval. - Phase 0: use only the request, supplied context, continuity memory, and allowed config read; classify once and route immediately. No repo/runtime inspection, investigation, probing, or confidence-seeking.