FaisalAlqarni

The Evaluate-Loop coordinator for soe. Runs the BRAINSTORM → PLAN → EVALUATE_PLAN → EXECUTE → EVALUATE_EXEC → (FIX↺ | COMPLETE) state machine for a track: dispatches leaf agents, dispatches workers into isolated worktrees and applies their validated returns serially, and is the SOLE writer of .soe/tracks/{id}/state.json. Resumes crash-safely from committed state and bounds its fix/plan loops. Use when: 'run the loop', 'orchestrate', 'run the track', 'evaluate-loop', 'drive the track to completion'.

Session-model-led multi-model tiering. Use in ANY conversation (ambient) or in the pipeline to decide which model tier does which slice of work, and to delegate to the right model-pinned agent (strategist/deep-reasoner/fast-worker). The session model you selected IS the orchestrator; it self-selects its topology from its own model identity.

Use when the orchestrator needs to delegate an implementation task to an isolated worker — dispatches each worker as a Task-tool subagent in its own git worktree, awaits its return as the completion signal, and applies results serially as the sole state.json writer behind a validated context firewall

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Use at run start to discover what reviewers/analyzers/generators any installed plugin provides and route work by ROLE. Builds a role→provider map via lib/capability-scan.js so the loop prefers the best-matching installed specialist (a Go reviewer, a Flutter reviewer, AgentShield, ...) and falls back to soe-core's generic (soe:code-reviewer, soe:security-reviewer, soe:architect, ...) when none is installed. soe-core is self-sufficient and NEVER hard-depends on packs.

Discover and reuse ANY installed MCP server by CAPABILITY (design §6, for MCP tools). At run start the orchestrator enumerates its available mcp__* tools and calls lib/mcp-discovery.js classifyMcpTools to build a capability map (docs/browser/graph/design/database/search/email/calendar/storage/…). When a needed capability has a discovered MCP, prefer it over doing the work manually — the four named providers (soe:using-graphify / using-codex / using-figma + chrome-devtools) take precedence when present; generic MCP discovery covers everything else. READ/analysis MCP tools auto-use + log; WRITE/irreversible MCP tools follow the confirm rule (soe:soe-modes / lib/escalation.js isIrreversible). Graceful, silent fallback to soe's native tools when no MCP matches. Registered as an optional provider by soe:capability-discovery.

Pattern for progressively refining context retrieval to solve the subagent context problem

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Extract learned patterns from session - invoked automatically by finishing-a-development-branch or manually anytime

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for review, delivery, or cleanup

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions