Make lead the default routing agent

Author: juancarlosrodicio

README.md

@@ -8,7 +8,7 @@ This repository is not affiliated with OpenCode, Open Design, Impeccable, or Sup
 
 ## Architecture
 
-By default, free-form messages open with `developer` for small, clear, low-risk changes. Use slash commands when you want an explicit workflow.
+By default, free-form messages open with `lead` as a bounded router. Lead quickly chooses `developer`, `researcher`, `designer`, or `specifier`, and asks the user when ambiguity changes the correct flow. Small, clear, low-risk changes are usually delegated straight to `developer`.
 
 Core feature flow:
 

docs/agents.md

@@ -2,12 +2,12 @@
 
 ## Core agents
 
-- `lead`: orchestrates feature work and enforces phase barriers.
+- `lead`: default free-form router, feature orchestrator, and phase-barrier owner.
 - `scoper`: lightweight research -> spec orchestrator.
 - `designer`: uses PRODUCT.md/DESIGN.md, optional Impeccable, and Open Design.
 - `researcher`: verifies code, docs, APIs, alternatives, and risks.
 - `specifier`: produces specs, tasks, acceptance criteria, and validation plans.
-- `developer`: implements approved tasks and validates changes.
+- `developer`: implements approved tasks, including direct-mode work delegated by lead, and validates changes.
 - `reviewer`: reviews diffs against spec and returns verdicts.
 
 ## Optional AHE sidecars

docs/configuration.md

@@ -14,6 +14,6 @@ The kit is organized as an OpenCode config directory:
 
 The default permissions are conservative: reads are allowed, edits and bash ask by default, and external directories are denied.
 
-The default agent is `developer`, with `mode: all`, so free-form small changes can be implemented directly. Slash commands still route to their explicit agents, for example `/feature` and `/plan` to `lead`, `/scope` to `scoper`, and `/design` to `designer`.
+The default agent is `lead`, acting as a bounded router for free-form messages. For small, clear, low-risk work, lead delegates direct mode to `developer`; for technical uncertainty it delegates to `researcher`; for visual or interaction work it delegates to `designer`; and for planning gaps it delegates to `specifier`. Slash commands still route to their explicit agents, for example `/feature` and `/plan` to `lead`, `/scope` to `scoper`, and `/design` to `designer`.
 
 Run `node scripts/check-harness.mjs` from an installed OpenCode config directory to validate the core harness contracts. In this repository, `npm run check` runs the same validator against `opencode/`.

docs/quickstart.md

@@ -31,13 +31,13 @@ Expected flow: researcher -> scoper synthesis -> specifier.
 
 Expected flow: lead -> researcher -> specifier -> reviewer, with no implementation.
 
-## 5. Try direct mode
+## 5. Try bounded direct routing
 
 ```text
 Change the Settings heading to Account settings and run the smallest relevant validation.
 ```
 
-Expected flow: developer handles the small change directly. No full feature orchestration.
+Expected flow: lead chooses the direct path and delegates the small change to developer. No full feature orchestration.
 
 ## 6. Try design
 
@@ -61,4 +61,4 @@ Expected flow: lead decides research/design needs, then specifier -> developer -
 npm run check
 ```
 
-The check validates config JSON, agent/command frontmatter, the default `developer` direct mode, `/feature` sidecar boundaries, the `/plan` contract, and the agent-readable docs under `opencode/docs/ai/harness/`.
+The check validates config JSON, agent/command frontmatter, the default `lead` router contract, `/feature` sidecar boundaries, the `/plan` contract, and the agent-readable docs under `opencode/docs/ai/harness/`.

docs/workflows.md

@@ -2,9 +2,9 @@
 
 ## Direct mode
 
-Free-form messages without a slash command use `developer` by default. This is intended for small, clear, low-risk changes where a full product-development pipeline would be unnecessary.
+Free-form messages without a slash command use `lead` by default as a bounded router. This keeps the simplest path for small, clear, low-risk changes while avoiding silent guesses when the right flow is unclear.
 
-If the request has ambiguity, visual/product impact, medium or large scope, or critical missing context, switch to `/feature`, `/scope`, `/design`, or `/spec`.
+Lead decides quickly between `developer`, `researcher`, `designer`, or `specifier`. It delegates small direct work to `developer`, routes uncertainty to `researcher`, visual/product work to `designer`, planning gaps to `specifier`, and asks the user when ambiguity changes the right path.
 
 ## Feature
 

opencode/AGENTS.md

@@ -6,7 +6,7 @@ This file is the short map for the harness. Detailed contracts live in
 ## Work model
 
 - For normal messages without a slash command, use the simplest path.
-- If a change is small, clear, and low risk, direct mode goes to `developer`.
+- If a change is small, clear, and low risk, `lead` decides quickly and usually delegates direct mode to `developer`.
 - Full flows activate through slash commands such as `/feature`, `/plan`,
   `/scope`, `/design`, `/review`, or `/evolve`.
 - Before implementing, understand the stack, scope, and minimum validation.
@@ -29,7 +29,7 @@ See `docs/ai/harness/agents.md` for full contracts.
 
 ## Base flows
 
-- Small free-form request: `developer`.
+- Small free-form request: `lead` decides and usually delegates to `developer`.
 - Full feature: `lead -> designer if applicable -> researcher -> specifier -> developer -> reviewer`.
 - Plan without implementation: `lead -> researcher -> specifier -> reviewer`.
 - Scope/spec without implementation: `scoper -> researcher -> scoper synthesis -> specifier`.

opencode/agents/developer.md

@@ -34,7 +34,7 @@ You are the senior developer.
 
 ## Direct mode without slash commands
 
-When you are the default agent and the user asks for a small, clear, low-risk change without using a slash command, treat it as an approved implementation task.
+When `lead` delegates direct mode for a small, clear, low-risk change without using a slash command, treat it as an approved implementation task.
 
 Before editing, identify:
 

opencode/agents/lead.md

@@ -37,9 +37,19 @@ Your job is not to do every task yourself. Your job is to choose the correct ord
 
 ## Default behavior without slash commands
 
-Do not force the full orchestration flow when the user did not invoke an explicit command such as `/feature`, `/scope`, `/design`, `/spec`, `/implement`, `/review`, or `/evolve`.
+When the user did not invoke an explicit command such as `/feature`, `/scope`, `/design`, `/spec`, `/implement`, `/review`, or `/evolve`, act as a fast router. Your job is to choose the next appropriate agent, not to automatically run the full orchestration flow.
 
-For small, clear, low-risk requests, invoke `developer` directly with:
+Use lightweight inspection if you need to check the repo or context. Decide quickly. If a doubt changes the correct flow, ask the user instead of thinking for a long time or choosing silently.
+
+Routing decision:
+
+- `developer`: small, clear, localized, verifiable change.
+- `researcher`: technical/product uncertainty, APIs, libraries, architecture, risks, or need for real evidence before deciding.
+- `designer`: UX/UI, visual design, layout, brand, interaction, or visual criteria.
+- `specifier`: enough context exists, but the work still needs tasks, acceptance criteria, or a validation plan.
+- Ask the user: real ambiguity changes whether research, design, spec, or direct implementation is appropriate.
+
+If you choose direct mode, invoke `developer` with:
 
 - concrete objective;
 - minimum acceptance criteria;
@@ -67,7 +77,7 @@ Use explicit phase barriers:
 6. Review.
 7. Closure.
 
-Do not skip phases unless the work is genuinely trivial or the user made a small free-form request without a slash command.
+Do not skip phases unless the work is genuinely trivial or you explicitly routed a small free-form request without a slash command.
 
 ## Dependency rules
 

opencode/docs/ai/harness/agents.md

@@ -4,8 +4,8 @@
 
 | Agent | Use when | Do not use when | Expected evidence |
 | --- | --- | --- | --- |
-| `developer` | Change is small, clear, approved, or direct without slash command | Critical decision, design, or research is missing | Validation run or explicit reason |
-| `lead` | Slash workflow, coordination, or phase dependencies are needed | Free-form request is small and localized | Assumptions, criteria, and barriers respected |
+| `developer` | Change is small, clear, approved, or delegated by lead | Critical decision, design, or research is missing | Validation run or explicit reason |
+| `lead` | Free-form message without slash command, slash workflow, coordination, or phase dependencies | The task was already delegated to another agent | Routing decision, assumptions, criteria, and barriers respected |
 | `designer` | UX/UI, brand, layout, interaction, or Open Design matters | Technical change has no visual impact | Visual handoff with observable criteria |
 | `researcher` | Technical/product uncertainty, APIs, libraries, risks | Fact is already clear in repo | Sources reviewed and unknowns remaining |
 | `specifier` | There is enough context to turn goal into tasks | Critical research/design is pending | Acceptance criteria and validation plan |
@@ -17,8 +17,9 @@
 
 ## Invariants
 
-- `developer` is the harness `default_agent`.
+- `lead` is the harness `default_agent` and acts as a bounded router for free-form messages.
 - `lead` must not force the full flow for small free-form messages.
+- `developer` executes direct mode when `lead` delegates a small, clear, verifiable task.
 - `specifier` waits for research/design when those results affect requirements.
 - `reviewer` waits for a diff, reviewable implementation, or `/plan` artifact.
 - `evaluator`, `debugger`, and `evolver` are optional sidecars.

opencode/docs/ai/harness/checks.md

@@ -17,7 +17,7 @@ npm run check
 The harness check validates:
 
 - `opencode.json`;
-- `default_agent: developer`;
+- `default_agent: lead`;
 - minimum frontmatter in `agents/*.md` and `commands/*.md`;
 - local `/feature` contract;
 - local `/plan` contract;