@phi-code-admin/phi-code 0.61.6 → 0.61.8

package/extensions/phi/orchestrator.ts

@@ -438,67 +438,55 @@ export default function orchestratorExtension(pi: ExtensionAPI) {
 	// ─── /plan Command — Full workflow ───────────────────────────────
 
 	pi.registerCommand("plan", {
-		description: "Plan AND execute a project: creates spec + todo, then runs each task with isolated sub-agents",
+		description: "Plan AND execute a project with agents — describe what to build",
 		handler: async (args, ctx) => {
 			const description = args.trim();
 
 			if (!description) {
 				ctx.ui.notify(`**Usage:** \`/plan <project description>\`
 
-**Full workflow in one command:**
-1. LLM analyzes your description
-2. Creates spec.md + todo.md
-3. Executes each task with an isolated sub-agent
-4. Each agent has its own context, model, and system prompt
-5. Results saved to progress.md
-
 **Examples:**
   /plan Build a REST API for user authentication with JWT
+  /plan Create a cyberpunk Pong browser game
   /plan Add test coverage to the payment module
-  /plan Refactor the frontend to use TypeScript
 
 **Other commands:**
-  /run   — Re-execute an existing plan
-  /plans — List all plans and status`, "info");
+  /plans — List all plans`, "info");
 				return;
 			}
 
-			pi.sendUserMessage(
-				`Analyze this project and call the orchestrate tool. It will create the plan AND execute all tasks automatically with parallel sub-agents.
-
-## Project
-${description}
-
-## Instructions
-
-1. **Analyze** the project: identify goals, requirements, technical constraints, and architecture decisions.
-
-2. **Decompose** into tasks. Each task will be executed by an isolated sub-agent that has:
-   - NO access to this conversation
-   - NO shared memory or context
-   - Its own model and system prompt
-   - Full tool access (read, write, edit, bash, grep, find, ls)
-
-3. **Write self-contained task descriptions** using this pattern:
-   - CONTEXT: What exists, relevant file paths, current state
-   - TASK: Exactly what to implement/analyze/test
-   - FORMAT: Expected output (files created, test results, etc.)
-   - CONSTRAINTS: Rules, conventions, things to avoid
-
-4. **Assign agents**: explore (read-only analysis), plan (design), code (implementation), test (write+run tests), review (quality audit)
-
-5. **Set dependencies** to maximize parallelism:
-   - Tasks without dependencies → same wave → run simultaneously
-   - Only add a dependency when a task truly needs another's output
-   - Typical flow: explore(wave 1) → plan(wave 2) → code(wave 3) → test(wave 4) → review(wave 5)
-   - But independent code tasks can run in parallel within the same wave
+			// Create plan files
+			await ensurePlansDir();
+			const ts = timestamp();
+			const specFile = `spec-${ts}.md`;
+			await writeFile(join(plansDir, specFile), `# ${description}\n\n**Created:** ${new Date().toLocaleString()}\n`, "utf-8");
+
+			ctx.ui.notify(`📋 Plan created. Executing with agents...`, "info");
+
+			// Load agent definitions for system prompts
+			const agentDefs = loadAgentDefs();
+			const phases = [
+				{ agent: "explore", label: "🔍 Exploring", instruction: `Analyze the project requirements and existing codebase. Identify what exists, what's needed, and any constraints.\n\nProject: ${description}` },
+				{ agent: "plan", label: "📐 Planning", instruction: `Design the architecture, file structure, and implementation approach.\n\nProject: ${description}` },
+				{ agent: "code", label: "💻 Coding", instruction: `Implement the complete project. Create ALL necessary files with production-quality code.\n\nProject: ${description}\n\nCreate every file needed. Do NOT leave placeholders or TODOs. Complete implementation.` },
+				{ agent: "test", label: "🧪 Testing", instruction: `Test the implementation. Run the code, check for errors, verify it works.\n\nProject: ${description}` },
+				{ agent: "review", label: "🔍 Reviewing", instruction: `Review code quality, security, and performance. Fix any issues found.\n\nProject: ${description}` },
+			];
+
+			// Execute each phase sequentially using sendUserMessage + waitForIdle
+			for (const phase of phases) {
+				const agentDef = agentDefs.get(phase.agent);
+				const systemPromptNote = agentDef?.systemPrompt
+					? `\n\n[Agent: ${phase.agent}] ${agentDef.systemPrompt.slice(0, 200)}`
+					: "";
+
+				ctx.ui.notify(`\n${phase.label} (agent: ${phase.agent})...`, "info");
+
+				pi.sendUserMessage(phase.instruction + systemPromptNote);
+				await ctx.waitForIdle();
+			}
 
-6. **Call the orchestrate tool** with ALL fields in a SINGLE call:
-   - title, description, goals, requirements, constraints (project metadata)
-   - tasks (array of ALL task objects with title, description, agent, dependencies)
-   
-⚠️ CRITICAL: Include the \`tasks\` array in the SAME tool call as the project metadata. Do NOT make separate calls. All data must be in ONE orchestrate() invocation.`
-			);
+			ctx.ui.notify(`\n✅ **Project complete!** Plan: \`${specFile}\``, "info");
 		},
 	});
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@phi-code-admin/phi-code",
-	"version": "0.61.6",
+	"version": "0.61.8",
 	"description": "Coding agent CLI with read, bash, edit, write tools and session management",
 	"type": "module",
 	"piConfig": {