opencode-orchestrator 1.0.13 → 1.0.14

package/dist/index.js

@@ -268,6 +268,52 @@ var WAL_ACTIONS = {
   DELETE: "DELETE"
 };
 
+// src/shared/core/constants/phases.ts
+var PHASES = {
+  PHASE_0: {
+    ID: "PHASE_0",
+    NAME: "DISCOVERY SWARM",
+    DESCRIPTION: "Parallel intelligence gathering and project mapping",
+    MANDATORY: true
+  },
+  PHASE_1: {
+    ID: "PHASE_1",
+    NAME: "THINK",
+    DESCRIPTION: "Analyze scope, decomposition, and delegation",
+    MANDATORY: true
+  },
+  PHASE_2: {
+    ID: "PHASE_2",
+    NAME: "TRIAGE",
+    DESCRIPTION: "Complexity assessment and execution path selection",
+    MANDATORY: true
+  },
+  PHASE_3: {
+    ID: "PHASE_3",
+    NAME: "PLAN",
+    DESCRIPTION: "Architectural roadmap and task grid creation",
+    MANDATORY: true
+  },
+  PHASE_4: {
+    ID: "PHASE_4",
+    NAME: "EXECUTE",
+    DESCRIPTION: "HPFA grid execution and worker coordination",
+    MANDATORY: true
+  },
+  PHASE_5: {
+    ID: "PHASE_5",
+    NAME: "VERIFY",
+    DESCRIPTION: "MSVP final gate and E2E system validation",
+    MANDATORY: true
+  },
+  PHASE_6: {
+    ID: "PHASE_6",
+    NAME: "SEAL",
+    DESCRIPTION: "Mission completion and deterministic output",
+    MANDATORY: true
+  }
+};
+
 // src/shared/core/constants/cli.ts
 var CLI_NAME = {
   NPX: "npx",
@@ -13859,65 +13905,69 @@ ${PROMPT_TAGS.TOOLS.close}`;
 
 // src/agents/prompts/commander/execution.ts
 var COMMANDER_EXECUTION = `${PROMPT_TAGS.EXECUTION_STRATEGY.open}
-## Phase 0: STRATEGIC SCOUT SWARM (Parallel Intelligence)
-**Launch Intelligence Scouts** to map the terrain before any strategic decisions.
-
-1. **Initialize \`${PATHS.OPENCODE}\`/ folder**: Clean start for synchronized context.
-2. **LAUNCH Scouts (background=true)**:
-   - **[Scout: Structure]**: Map directory tree and file patterns.
-   - **[Scout: Stack]**: Detect tech stack, build system, and dependencies.
-   - **[Scout: Docs]**: Analyze README, API docs, and architectural conventions.
-   - **[Scout: Infra]**: Identify CI/CD, Docker, and environment variables.
-3. **RECOVER & RETRIEVE**: Monitor scouts. Once finished, **READ \`${PATHS.CONTEXT}\` and \`ls -R\` outputs** to ingest all findings.
-
-## Phase 1: COMMANDER'S INTEL ANALYSIS (Strategic Mandate)
-**THINK FIRST**: Do not just blindly delegate. Analyze the gathered intelligence to set the mission trajectory.
-
-### 1.1 ARCHITECTURAL ANALYSIS
-- Based on Phase 0 reports, what is the existing architecture?
-- What are the core constraints and patterns I MUST enforce?
-- Identify potential bottlenecks or high-risk areas.
-
-### 1.2 THE STRATEGIC MANDATE
-- Define the **MISSION CHARTER** for the ${AGENT_NAMES.PLANNER}.
-- What is the specific architectural goal?
-- What are the non-negotiable success criteria?
-
-### 1.3 DECOMPOSITION
-- Break the mission into INDEPENDENT parallel streams.
-- Define the maximum concurrency slots for this specific mission.
+## ${PHASES.PHASE_0.ID}: ${PHASES.PHASE_0.NAME} (Cognitive Velocity Launch)
+**Mandatory High-Velocity Initialization**: Do not perform discovery sequentially. Launch a swarm of scouts immediately.
+
+1. **Initialize \`${PATHS.OPENCODE}\` folder**:
+   - Immediate setup for CONTEXT SHARING (DELETE existing if fresh start).
+2. **LAUNCH Parallel Discovery Tasks (background=true)**:
+   - **[Scout: Structure]**: Analyze project tree (ls, find) at depth 2-3.
+   - **[Scout: Stack]**: Parse package.json, Cargo.toml, or pyproject.toml for identity.
+   - **[Scout: Docs]**: Analyze README.md, CONTRIBUTING.md, and core architecture docs.
+   - **[Scout: Infra]**: Detect Docker, CI/CD pipelines, and environment variables.
+3. **BARRIER SYNC & RETRIEVE**: Monitor scouts. Once finished, **READ all scout results** and \`${PATHS.CONTEXT}\` to ingest all findings.
+4. **SET TARGET**: Use the unified context to proceed to Phase 1.
+
+## ${PHASES.PHASE_1.ID}: ${PHASES.PHASE_1.NAME} (Mandatory - Never Skip!)
+**THINK FIRST**: As ${AGENT_NAMES.COMMANDER}, think about ORCHESTRATION and synthesis before action.
+
+### 1.1 MISSION SCOPE
+- What is the FULL scope of this mission?
+- What are the deliverables and success criteria?
+- What does the user REALLY want (not just what they said)?
+
+### 1.2 DECOMPOSITION
+- How can I break this into INDEPENDENT sub-tasks?
+- Which tasks MUST be sequential (dependencies)?
+- What is the MAXIMUM parallelism I can achieve?
+
+### 1.3 DELEGATION
+- Which agent is BEST for each task? (${AGENT_NAMES.PLANNER}/${AGENT_NAMES.WORKER}/${AGENT_NAMES.REVIEWER})
+- What context does each agent NEED to succeed?
+- What could cause an agent to FAIL or get stuck?
 
 ### 1.4 RISK ASSESSMENT
 - What are the HIGH-RISK parts of this mission?
 - What is my FALLBACK if a task fails?
+- How will I DETECT and RECOVER from issues?
 - If agent fails \u2192 See ${PROMPT_TAGS.RECOVERY.open} section: DECOMPOSE and retry
 
-**ANTI-PATTERNS**: Starting without intellectual synthesis. Sequential execution when parallel is possible.
+**ANTI-PATTERNS**: Sequential execution when parallel is possible. Doing work yourself instead of delegating. Starting without clear decomposition or intellectual synthesis.
 
-## Phase 2: TRIAGE
+## ${PHASES.PHASE_2.ID}: ${PHASES.PHASE_2.NAME}
 | Type | Signal | Approach |
 |------|--------|----------|
 | ${WORK_STATUS.TRIAGE.TYPE.SIMPLE} | ${WORK_STATUS.TRIAGE.SIGNAL.ONE_FILE} | ${WORK_STATUS.TRIAGE.APPROACH.DIRECT} |
 | ${WORK_STATUS.TRIAGE.TYPE.MEDIUM} | ${WORK_STATUS.TRIAGE.SIGNAL.MULTI_FILE} | ${WORK_STATUS.TRIAGE.APPROACH.PLAN_EXECUTE_VERIFY} |
 | ${WORK_STATUS.TRIAGE.TYPE.COMPLEX} | ${WORK_STATUS.TRIAGE.SIGNAL.LARGE_SCOPE} | ${WORK_STATUS.TRIAGE.APPROACH.RESEARCH_PLAN_PARALLEL} |
 
-## Phase 3: PLAN (for ${WORK_STATUS.TRIAGE.TYPE.MEDIUM}/${WORK_STATUS.TRIAGE.TYPE.COMPLEX})
+## ${PHASES.PHASE_3.ID}: ${PHASES.PHASE_3.NAME} (for ${WORK_STATUS.TRIAGE.TYPE.MEDIUM}/${WORK_STATUS.TRIAGE.TYPE.COMPLEX})
 ${AGENT_NAMES.PLANNER} creates ${PATHS.TODO} with parallel groups
 
-## Phase 4: EXECUTE
+## ${PHASES.PHASE_4.ID}: ${PHASES.PHASE_4.NAME}
 1. LAUNCH all independent tasks simultaneously (background=true)
 2. MONITOR with ${TOOL_NAMES.LIST_TASKS}
 3. COLLECT results with ${TOOL_NAMES.GET_TASK_RESULT}
 4. CONTINUE with dependent tasks
 5. REPEAT until all [ ] become [x]
 
-## Phase 5: STAGE 2 INTEGRATION REVIEW (Final Gate)
-1. **SYNC BARRIER**: Ensure all [Work + Stage 1 Review] pairs in ${PATHS.TODO} are SUCCESS.
-2. **VERIFY INTEGRATION**: ${AGENT_NAMES.REVIEWER} validates cross-module consistency.
+## ${PHASES.PHASE_5.ID}: ${PHASES.PHASE_5.NAME}
+1. **STAGE 1 (Unit)**: Reviewers validate individual module changes (triggered by Workers).
+2. **STAGE 2 (Integration)**: ${AGENT_NAMES.REVIEWER} validates cross-module consistency.
 3. **E2E VALIDATION**: Run full system tests and build pass check.
 4. Only proceed to SEAL if all criteria are met with zero regressions.
 
-## Phase 6: SEAL
+## ${PHASES.PHASE_6.ID}: ${PHASES.PHASE_6.NAME}
 When ALL conditions met, output ${MISSION_SEAL.PATTERN}
 ${PROMPT_TAGS.EXECUTION_STRATEGY.close}`;
 

package/dist/shared/core/constants/index.d.ts

@@ -8,4 +8,5 @@ export { MEMORY_LIMITS } from "./memory-limits.js";
 export { STATUS_LABEL } from "./status-labels.js";
 export { LIMITS } from "./limits.js";
 export { WAL_ACTIONS } from "./wal-actions.js";
+export { PHASES } from "./phases.js";
 export * from "./cli.js";

package/dist/shared/core/constants/phases.d.ts

@@ -0,0 +1,47 @@
+/**
+ * Mission Phase Constants
+ */
+export declare const PHASES: {
+    readonly PHASE_0: {
+        readonly ID: "PHASE_0";
+        readonly NAME: "DISCOVERY SWARM";
+        readonly DESCRIPTION: "Parallel intelligence gathering and project mapping";
+        readonly MANDATORY: true;
+    };
+    readonly PHASE_1: {
+        readonly ID: "PHASE_1";
+        readonly NAME: "THINK";
+        readonly DESCRIPTION: "Analyze scope, decomposition, and delegation";
+        readonly MANDATORY: true;
+    };
+    readonly PHASE_2: {
+        readonly ID: "PHASE_2";
+        readonly NAME: "TRIAGE";
+        readonly DESCRIPTION: "Complexity assessment and execution path selection";
+        readonly MANDATORY: true;
+    };
+    readonly PHASE_3: {
+        readonly ID: "PHASE_3";
+        readonly NAME: "PLAN";
+        readonly DESCRIPTION: "Architectural roadmap and task grid creation";
+        readonly MANDATORY: true;
+    };
+    readonly PHASE_4: {
+        readonly ID: "PHASE_4";
+        readonly NAME: "EXECUTE";
+        readonly DESCRIPTION: "HPFA grid execution and worker coordination";
+        readonly MANDATORY: true;
+    };
+    readonly PHASE_5: {
+        readonly ID: "PHASE_5";
+        readonly NAME: "VERIFY";
+        readonly DESCRIPTION: "MSVP final gate and E2E system validation";
+        readonly MANDATORY: true;
+    };
+    readonly PHASE_6: {
+        readonly ID: "PHASE_6";
+        readonly NAME: "SEAL";
+        readonly DESCRIPTION: "Mission completion and deterministic output";
+        readonly MANDATORY: true;
+    };
+};

package/package.json

@@ -2,7 +2,7 @@
   "name": "opencode-orchestrator",
   "displayName": "OpenCode Orchestrator",
   "description": "Distributed Cognitive Architecture for OpenCode. Turns simple prompts into specialized multi-agent workflows (Planner, Coder, Reviewer).",
-  "version": "1.0.13",
+  "version": "1.0.14",
   "author": "agnusdei1207",
   "license": "MIT",
   "repository": {