@locusai/sdk 0.11.6 → 0.11.7

package/dist/index-node.js

@@ -5017,78 +5017,6 @@ init_config();
 init_knowledge_base();
 var import_node_fs10 = require("node:fs");
 
-// src/planning/agents/architect.ts
-function buildArchitectPrompt(input) {
-  let prompt = `# Role: Software Architect
-
-You are a Software Architect participating in an async sprint planning meeting. The Tech Lead has produced an initial task breakdown. Your job is to refine it.
-
-## CEO Directive
-> ${input.directive}
-`;
-  if (input.feedback) {
-    prompt += `
-## CEO Feedback on Previous Plan
-> ${input.feedback}
-
-IMPORTANT: Ensure the refined plan addresses this feedback.
-`;
-  }
-  prompt += `
-## Project Context
-${input.projectContext || "No project context available."}
-
-## Tech Lead's Task Breakdown
-${input.techLeadOutput}
-
-## Your Task
-
-Review and refine the Tech Lead's breakdown:
-
-1. **Ordering** — Order tasks so that foundational work comes first. Tasks that produce outputs consumed by later tasks must appear earlier in the list. Foundation tasks (schemas, config, shared code) must be listed before tasks that build on them. The array index IS the execution order.
-2. **Risk Assessment** — Flag tasks that are risky, underestimated, or have unknowns.
-3. **Task Merging** — If two tasks are trivially small and related, merge them.
-4. **Complexity Scoring** — Rate each task 1-5 (1=trivial, 5=very complex).
-5. **Missing Tasks** — Add any tasks the Tech Lead missed (database migrations, configuration, testing, etc.).
-6. **Description Quality** — Review and improve each task description to be a clear, actionable implementation guide. Each description must tell the executing agent exactly what to do, where to do it (specific files/modules), how to do it (patterns, utilities, data flow), and what is NOT in scope. Vague descriptions like "Add authentication" must be rewritten with specific file paths, implementation approach, and boundaries.
-
-## CRITICAL: Task Ordering & Dependencies
-
-Tasks are executed SEQUENTIALLY by a single agent on ONE branch. The agent works through tasks in array order. Each completed task's changes are available to subsequent tasks. You MUST enforce these rules:
-
-1. **Order tasks by dependency.** Foundation tasks (schemas, config, shared code) must come first. Tasks that build on earlier work must appear later in the list.
-2. **Each task must be self-contained for its scope.** A task can depend on earlier tasks (they run sequentially), but must include all changes needed for its own goal.
-3. **Split tasks at logical boundaries.** Since tasks run sequentially on the same branch, splitting is safe — later tasks see earlier changes. Split when it improves clarity and reviewability.
-4. **Flag risks.** In your risk assessment, call out tasks that are complex or have unknowns.
-
-## Output Format
-
-Your entire response must be a single JSON object — no text before it, no text after it, no markdown code blocks, no explanation. Start your response with the "{" character:
-
-{
-  "tasks": [
-    {
-      "title": "string",
-      "description": "string (detailed implementation guide: what to do, where to do it, how to do it, and boundaries)",
-      "assigneeRole": "BACKEND | FRONTEND | QA | PM | DESIGN",
-      "priority": "HIGH | MEDIUM | LOW | CRITICAL",
-      "labels": ["string"],
-      "acceptanceCriteria": ["string"],
-      "complexity": 3
-    }
-  ],
-  "risks": [
-    {
-      "description": "string",
-      "mitigation": "string",
-      "severity": "low | medium | high"
-    }
-  ],
-  "architectureNotes": "string (notes for the Sprint Organizer about parallelism opportunities and constraints)"
-}`;
-  return prompt;
-}
-
 // src/planning/agents/cross-task-reviewer.ts
 function buildCrossTaskReviewerPrompt(input) {
   let prompt = `# Role: Cross-Task Reviewer (Architect + Engineer + Planner)
@@ -5124,7 +5052,7 @@ IMPORTANT: Ensure the reviewed plan still addresses this feedback.
 ${input.projectContext || "No project context available."}
 
 ## Sprint Plan to Review
-${input.sprintOrganizerOutput}
+${input.plannerOutput}
 
 ## Your Review Checklist
 
@@ -5203,11 +5131,11 @@ IMPORTANT:
   return prompt;
 }
 
-// src/planning/agents/sprint-organizer.ts
-function buildSprintOrganizerPrompt(input) {
-  let prompt = `# Role: Sprint Organizer
+// src/planning/agents/planner.ts
+function buildPlannerPrompt(input) {
+  let prompt = `# Role: Sprint Planner
 
-You are a Sprint Organizer finalizing the sprint plan from a planning meeting. The Architect has refined the task breakdown. Your job is to produce the final sprint plan document.
+You are a Sprint Planner — an expert engineer, architect, and project organizer rolled into one. Your job is to take a CEO directive and produce a complete, ready-to-execute sprint plan in a single pass.
 
 ## CEO Directive
 > ${input.directive}
@@ -5217,40 +5145,64 @@ You are a Sprint Organizer finalizing the sprint plan from a planning meeting. T
 ## CEO Feedback on Previous Plan
 > ${input.feedback}
 
-IMPORTANT: The final plan must address this feedback.
+IMPORTANT: Incorporate this feedback into your plan. The CEO has reviewed a previous plan and wants changes.
 `;
   }
   prompt += `
-## Architect's Refined Task Breakdown
-${input.architectOutput}
+## Project Context
+${input.projectContext || "No project context available."}
+
+## Codebase Structure
+${input.codebaseIndex || "No codebase index available."}
 
 ## Your Task
 
-Produce the final sprint plan:
+Analyze the directive and produce a **complete sprint plan** with the following:
 
-1. **Sprint Name** — A concise, memorable name for this sprint (e.g., "User Authentication", "Payment Integration")
+1. **Sprint Name** — A concise, memorable name (2-4 words)
 2. **Sprint Goal** — One paragraph describing what this sprint delivers
-3. **Task Ordering** — Final ordering so that foundational work comes first. The position in the array IS the execution order — task at index 0 runs first, index 1 runs second, etc. Tasks are executed SEQUENTIALLY by a single agent on one branch.
-4. **Duration Estimate** — How many days this sprint will take with a single agent working sequentially
-5. **Final Task List** — Each task with all fields filled in, ordered by execution priority
-6. **Description Quality Check** — Ensure every task description is a clear, actionable implementation guide. Each description must specify: what to do, where to do it (specific files/modules/directories), how to do it (implementation approach, patterns to follow, existing utilities to use), and what is NOT in scope. If any description is vague or generic, rewrite it with specifics. Remember: an independent agent will receive ONLY the task title, description, and acceptance criteria — the description is its primary instruction.
-
-Guidelines:
-- The order of tasks in the array determines execution order. Tasks are dispatched sequentially from first to last.
-- Foundation tasks (schemas, config, shared code) must appear before tasks that build on them
-- Since tasks execute sequentially on one branch, later tasks can depend on earlier tasks' outputs
-- Ensure acceptance criteria are specific and testable
-- Keep the sprint focused — if it's too large (>12 tasks), consider reducing scope
-- Ensure every task description reads as a standalone implementation brief — not a summary
+3. **Duration Estimate** — How many days this sprint will take with a single agent working sequentially
+4. **Task Breakdown** — An ordered list of tasks that fully implement the directive
+5. **Risk Assessment** — Potential risks with mitigations
+
+### Task Requirements
+
+For each task, provide:
+- **Title** — Clear, action-oriented (e.g., "Implement user registration API endpoint")
+- **Description** — A detailed, actionable implementation guide (see below)
+- **Assignee Role** — BACKEND, FRONTEND, QA, PM, or DESIGN
+- **Priority** — CRITICAL, HIGH, MEDIUM, or LOW
+- **Complexity** — 1 (trivial) to 5 (very complex)
+- **Labels** — Relevant tags (e.g., "api", "database", "ui", "auth")
+- **Acceptance Criteria** — Specific, testable conditions for completion
+
+### CRITICAL: Task Description Requirements
+
+Each task description will be handed to an INDEPENDENT agent as its primary instruction. The agent will have access to the codebase but NO context about the planning meeting. Each description MUST include:
+
+1. **What to do** — Clearly state the goal and expected behavior/outcome
+2. **Where to do it** — List specific files, modules, or directories to modify or create. Reference existing code paths when extending functionality
+3. **How to do it** — Key implementation details: which patterns to follow, which existing utilities or services to use, what the data flow looks like
+4. **Boundaries** — What is NOT in scope for this task to prevent overlap with other tasks
 
-## CRITICAL: Task Ordering Validation
+Bad example: "Add authentication to the API."
+Good example: "Implement JWT-based authentication middleware in src/middleware/auth.ts. Create a verifyToken middleware that extracts the Bearer token from the Authorization header, validates it using the existing JWT_SECRET from env config, and attaches the decoded user payload to req.user. Apply this middleware to all routes in src/routes/protected/. This task does NOT include user registration or password reset — those are handled separately."
+
+### CRITICAL: Task Ordering Rules
+
+Tasks are executed SEQUENTIALLY by a single agent on ONE branch. The agent works through tasks in array order. Therefore:
+
+1. **Foundation first.** Place foundational tasks (schemas, config, shared code) at the beginning. Later tasks can build on earlier ones since they run in sequence.
+2. **No forward dependencies.** A task must NOT depend on a task that appears later in the list.
+3. **Each task is self-contained for its scope.** A task can depend on earlier tasks but must include all changes needed for its own goal.
+4. **Keep tasks focused.** Each task should do one logical unit of work. Avoid trivially small or overly large tasks.
+5. **Merge related trivial work.** If two pieces of work are trivially small and tightly related, combine them into one task.
 
-Before finalizing, validate that tasks are in the correct execution order:
+### Sprint Scope Guidelines
 
-1. **No forward dependencies.** A task must NOT depend on a task that appears later in the list.
-2. **Foundation first.** Config, schemas, and shared code must come before implementation tasks.
-3. **Each task is independently executable given prior tasks.** An agent working on task N must be able to complete it assuming tasks 1 through N-1 are already done.
-4. **Prefer focused, well-scoped tasks.** Each task should do one logical unit of work.
+- If the sprint would exceed 12 tasks, reduce scope or merge related tasks
+- Ensure acceptance criteria are specific and testable
+- Keep the sprint focused on the directive — avoid scope creep
 
 ## Output Format
 
@@ -5263,7 +5215,7 @@ Your entire response must be a single JSON object — no text before it, no text
   "tasks": [
     {
       "title": "string",
-      "description": "string (detailed implementation guide: what to do, where to do it, how to do it, and boundaries)",
+      "description": "string (detailed implementation guide: what, where, how, boundaries)",
       "assigneeRole": "BACKEND | FRONTEND | QA | PM | DESIGN",
       "priority": "CRITICAL | HIGH | MEDIUM | LOW",
       "labels": ["string"],
@@ -5284,89 +5236,6 @@ IMPORTANT: Tasks are executed sequentially by a single agent. The array order IS
   return prompt;
 }
 
-// src/planning/agents/tech-lead.ts
-function buildTechLeadPrompt(input) {
-  let prompt = `# Role: Senior Tech Lead
-
-You are a Senior Tech Lead participating in an async sprint planning meeting. Your job is to take the CEO's directive and produce an initial task breakdown.
-
-## CEO Directive
-> ${input.directive}
-`;
-  if (input.feedback) {
-    prompt += `
-## CEO Feedback on Previous Plan
-> ${input.feedback}
-
-IMPORTANT: Incorporate this feedback into your task breakdown. The CEO has reviewed a previous plan and wants changes.
-`;
-  }
-  prompt += `
-## Project Context
-${input.projectContext || "No project context available."}
-
-## Codebase Structure
-${input.codebaseIndex || "No codebase index available."}
-
-## Your Task
-
-Analyze the CEO's directive and produce a detailed task breakdown. For each task:
-
-1. **Title** — Clear, action-oriented (e.g., "Implement user registration API endpoint")
-2. **Description** — A detailed, actionable implementation guide (see description requirements below)
-3. **Assignee Role** — Who should work on this: BACKEND, FRONTEND, QA, PM, or DESIGN
-4. **Priority** — HIGH, MEDIUM, or LOW based on business impact
-5. **Labels** — Relevant tags (e.g., "api", "database", "ui", "auth")
-6. **Acceptance Criteria** — Specific, testable conditions for completion
-
-Think about:
-- What existing code can be reused or extended
-- Which tasks are independent vs. dependent
-- What the right granularity is (not too big, not too small)
-- What risks or unknowns exist
-
-## CRITICAL: Task Description Requirements
-
-Each task description will be handed to an INDEPENDENT agent as its primary instruction. The agent will have access to the codebase but NO context about the planning meeting. Descriptions must be clear enough for the agent to execute the task without ambiguity.
-
-Each description MUST include:
-1. **What to do** — Clearly state the goal and what needs to be implemented, changed, or created. Be specific about the expected behavior or outcome.
-2. **Where to do it** — List the specific files, modules, or directories that need to be modified or created. Reference existing code paths when extending functionality.
-3. **How to do it** — Provide key implementation details: which patterns to follow, which existing utilities or services to use, what the data flow looks like.
-4. **Boundaries** — Clarify what is NOT in scope for this task to prevent overlap with other tasks.
-
-Bad example: "Add authentication to the API."
-Good example: "Implement JWT-based authentication middleware in src/middleware/auth.ts. Create a verifyToken middleware that extracts the Bearer token from the Authorization header, validates it using the existing JWT_SECRET from env config, and attaches the decoded user payload to req.user. Apply this middleware to all routes in src/routes/protected/. Add a POST /auth/login endpoint in src/routes/auth.ts that accepts {email, password}, validates credentials against the users table, and returns a signed JWT. This task does NOT include user registration or password reset — those are handled separately."
-
-## CRITICAL: Task Ordering Rules
-
-Tasks are executed SEQUENTIALLY by a single agent on ONE branch. The agent works through tasks in the order they appear in the array. Therefore:
-
-1. **Foundation first.** Place foundational tasks (schemas, config, shared code) at the beginning of the list. Later tasks can build on earlier ones since they run in sequence on the same branch.
-2. **Each task must be self-contained.** A task must include ALL the code changes it needs to work — from config to implementation to tests. A task CAN depend on earlier tasks in the list since they will have already been completed.
-3. **Logical ordering matters.** Tasks are dispatched in the order they appear. Ensure dependent tasks come after their prerequisites.
-4. **Keep tasks focused.** Each task should do one logical unit of work. Since there are no parallel execution conflicts, tasks can be more granular — but avoid tasks that are too small or trivial.
-
-## Output Format
-
-Your entire response must be a single JSON object — no text before it, no text after it, no markdown code blocks, no explanation. Start your response with the "{" character:
-
-{
-  "tasks": [
-    {
-      "title": "string",
-      "description": "string (detailed implementation guide: what to do, where to do it, how to do it, and boundaries — see description requirements above)",
-      "assigneeRole": "BACKEND | FRONTEND | QA | PM | DESIGN",
-      "priority": "HIGH | MEDIUM | LOW",
-      "labels": ["string"],
-      "acceptanceCriteria": ["string"]
-    }
-  ],
-  "technicalNotes": "string (brief notes on architecture decisions, risks, or considerations for the Architect phase)"
-}`;
-  return prompt;
-}
-
 // src/planning/planning-meeting.ts
 class PlanningMeeting {
   projectPath;
@@ -5382,52 +5251,33 @@ class PlanningMeeting {
   async run(directive, feedback) {
     const projectContext = this.getProjectContext();
     const codebaseIndex = this.getCodebaseIndex();
-    this.log("Phase 1/4: Tech Lead analyzing directive...", "info");
-    const techLeadPrompt = buildTechLeadPrompt({
+    this.log("Phase 1/2: Planner building sprint plan...", "info");
+    const plannerPrompt = buildPlannerPrompt({
       directive,
       projectContext,
       codebaseIndex,
       feedback
     });
-    const techLeadOutput = await this.aiRunner.run(techLeadPrompt);
-    this.log("Tech Lead phase complete.", "success");
-    this.log("Phase 2/4: Architect refining task breakdown...", "info");
-    const architectPrompt = buildArchitectPrompt({
-      directive,
-      projectContext,
-      techLeadOutput,
-      feedback
-    });
-    const architectOutput = await this.aiRunner.run(architectPrompt);
-    this.log("Architect phase complete.", "success");
-    this.log("Phase 3/4: Sprint Organizer finalizing plan...", "info");
-    const sprintOrganizerPrompt = buildSprintOrganizerPrompt({
-      directive,
-      architectOutput,
-      feedback
-    });
-    const sprintOrganizerOutput = await this.aiRunner.run(sprintOrganizerPrompt);
-    this.log("Sprint Organizer phase complete.", "success");
-    this.log("Phase 4/4: Cross-Task Review checking for conflicts and overlaps...", "info");
+    const plannerOutput = await this.aiRunner.run(plannerPrompt);
+    this.log("Planner phase complete.", "success");
+    this.log("Phase 2/2: Reviewer checking for conflicts and quality...", "info");
     const crossTaskReviewerPrompt = buildCrossTaskReviewerPrompt({
       directive,
       projectContext,
-      sprintOrganizerOutput,
+      plannerOutput,
       feedback
     });
-    const crossTaskReviewOutput = await this.aiRunner.run(crossTaskReviewerPrompt);
-    this.log("Cross-Task Review phase complete.", "success");
-    const plan = parseSprintPlanFromAI(crossTaskReviewOutput, directive);
+    const reviewOutput = await this.aiRunner.run(crossTaskReviewerPrompt);
+    this.log("Review phase complete.", "success");
+    const plan = parseSprintPlanFromAI(reviewOutput, directive);
     if (feedback) {
       plan.feedback = feedback;
     }
     return {
       plan,
       phaseOutputs: {
-        techLead: techLeadOutput,
-        architect: architectOutput,
-        sprintOrganizer: sprintOrganizerOutput,
-        crossTaskReview: crossTaskReviewOutput
+        planner: plannerOutput,
+        review: reviewOutput
       }
     };
   }

package/dist/planning/agents/architect.d.ts

@@ -1,15 +1 @@
-/**
- * Architect Agent Persona
- *
- * Phase 2 of the planning meeting. Reviews the Tech Lead's task
- * breakdown and refines it with dependency analysis, risk assessment,
- * and task splitting/merging recommendations.
- */
-export interface ArchitectInput {
-    directive: string;
-    projectContext: string;
-    techLeadOutput: string;
-    feedback?: string;
-}
-export declare function buildArchitectPrompt(input: ArchitectInput): string;
 //# sourceMappingURL=architect.d.ts.map

package/dist/planning/agents/architect.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"architect.d.ts","sourceRoot":"","sources":["../../../src/planning/agents/architect.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,MAAM,WAAW,cAAc;IAC7B,SAAS,EAAE,MAAM,CAAC;IAClB,cAAc,EAAE,MAAM,CAAC;IACvB,cAAc,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB;AAED,wBAAgB,oBAAoB,CAAC,KAAK,EAAE,cAAc,GAAG,MAAM,CAwElE"}
+{"version":3,"file":"architect.d.ts","sourceRoot":"","sources":["../../../src/planning/agents/architect.ts"],"names":[],"mappings":""}

package/dist/planning/agents/cross-task-reviewer.d.ts

@@ -1,14 +1,14 @@
 /**
  * Cross-Task Reviewer Agent Persona
  *
- * Phase 4 (final) of the planning meeting. Reviews the Sprint Organizer's
- * finalized plan for task ordering issues, dependency correctness,
+ * Phase 2 (final) of the planning meeting. Reviews the Planner's
+ * sprint plan for task ordering issues, dependency correctness,
  * description quality, and overall plan coherence.
  */
 export interface CrossTaskReviewerInput {
     directive: string;
     projectContext: string;
-    sprintOrganizerOutput: string;
+    plannerOutput: string;
     feedback?: string;
 }
 export declare function buildCrossTaskReviewerPrompt(input: CrossTaskReviewerInput): string;

package/dist/planning/agents/cross-task-reviewer.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"cross-task-reviewer.d.ts","sourceRoot":"","sources":["../../../src/planning/agents/cross-task-reviewer.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,MAAM,WAAW,sBAAsB;IACrC,SAAS,EAAE,MAAM,CAAC;IAClB,cAAc,EAAE,MAAM,CAAC;IACvB,qBAAqB,EAAE,MAAM,CAAC;IAC9B,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB;AAED,wBAAgB,4BAA4B,CAC1C,KAAK,EAAE,sBAAsB,GAC5B,MAAM,CAkHR"}
+{"version":3,"file":"cross-task-reviewer.d.ts","sourceRoot":"","sources":["../../../src/planning/agents/cross-task-reviewer.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,MAAM,WAAW,sBAAsB;IACrC,SAAS,EAAE,MAAM,CAAC;IAClB,cAAc,EAAE,MAAM,CAAC;IACvB,aAAa,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB;AAED,wBAAgB,4BAA4B,CAC1C,KAAK,EAAE,sBAAsB,GAC5B,MAAM,CAkHR"}

package/dist/planning/agents/planner.d.ts

@@ -0,0 +1,15 @@
+/**
+ * Planner Agent Persona
+ *
+ * Phase 1 of the simplified planning meeting. Combines the responsibilities
+ * of the former Tech Lead, Architect, and Sprint Organizer into a single
+ * pass that produces a complete, ordered sprint plan from the CEO directive.
+ */
+export interface PlannerInput {
+    directive: string;
+    projectContext: string;
+    codebaseIndex: string;
+    feedback?: string;
+}
+export declare function buildPlannerPrompt(input: PlannerInput): string;
+//# sourceMappingURL=planner.d.ts.map

package/dist/planning/agents/planner.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"planner.d.ts","sourceRoot":"","sources":["../../../src/planning/agents/planner.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,MAAM,WAAW,YAAY;IAC3B,SAAS,EAAE,MAAM,CAAC;IAClB,cAAc,EAAE,MAAM,CAAC;IACvB,aAAa,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB;AAED,wBAAgB,kBAAkB,CAAC,KAAK,EAAE,YAAY,GAAG,MAAM,CAyG9D"}

package/dist/planning/agents/sprint-organizer.d.ts

@@ -1,14 +1 @@
-/**
- * Sprint Organizer Agent Persona
- *
- * Phase 3 of the planning meeting. Takes the Architect's
- * refined task list and produces the final sprint plan with
- * name, goal, estimated duration, and organized task assignments.
- */
-export interface SprintOrganizerInput {
-    directive: string;
-    architectOutput: string;
-    feedback?: string;
-}
-export declare function buildSprintOrganizerPrompt(input: SprintOrganizerInput): string;
 //# sourceMappingURL=sprint-organizer.d.ts.map

package/dist/planning/agents/sprint-organizer.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"sprint-organizer.d.ts","sourceRoot":"","sources":["../../../src/planning/agents/sprint-organizer.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,MAAM,WAAW,oBAAoB;IACnC,SAAS,EAAE,MAAM,CAAC;IAClB,eAAe,EAAE,MAAM,CAAC;IACxB,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB;AAED,wBAAgB,0BAA0B,CACxC,KAAK,EAAE,oBAAoB,GAC1B,MAAM,CAiFR"}
+{"version":3,"file":"sprint-organizer.d.ts","sourceRoot":"","sources":["../../../src/planning/agents/sprint-organizer.ts"],"names":[],"mappings":""}

package/dist/planning/agents/tech-lead.d.ts

@@ -1,15 +1 @@
-/**
- * Tech Lead Agent Persona
- *
- * Phase 1 of the planning meeting. Reads the CEO directive,
- * project context, and codebase structure to produce an initial
- * task breakdown with technical approach for each task.
- */
-export interface TechLeadInput {
-    directive: string;
-    projectContext: string;
-    codebaseIndex: string;
-    feedback?: string;
-}
-export declare function buildTechLeadPrompt(input: TechLeadInput): string;
 //# sourceMappingURL=tech-lead.d.ts.map

package/dist/planning/agents/tech-lead.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"tech-lead.d.ts","sourceRoot":"","sources":["../../../src/planning/agents/tech-lead.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,MAAM,WAAW,aAAa;IAC5B,SAAS,EAAE,MAAM,CAAC;IAClB,cAAc,EAAE,MAAM,CAAC;IACvB,aAAa,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB;AAED,wBAAgB,mBAAmB,CAAC,KAAK,EAAE,aAAa,GAAG,MAAM,CAmFhE"}
+{"version":3,"file":"tech-lead.d.ts","sourceRoot":"","sources":["../../../src/planning/agents/tech-lead.ts"],"names":[],"mappings":""}

package/dist/planning/planning-meeting.d.ts

@@ -1,6 +1,6 @@
 import type { AiRunner } from "../ai/runner.js";
 import { type SprintPlan } from "./sprint-plan.js";
-export type PlanningPhase = "tech-lead" | "architect" | "sprint-organizer" | "cross-task-review" | "complete";
+export type PlanningPhase = "planner" | "review" | "complete";
 export interface PlanningMeetingConfig {
     projectPath: string;
     aiRunner: AiRunner;
@@ -10,17 +10,15 @@ export interface PlanningMeetingResult {
     plan: SprintPlan;
     /** Raw outputs from each phase for debugging/transparency */
     phaseOutputs: {
-        techLead: string;
-        architect: string;
-        sprintOrganizer: string;
-        crossTaskReview: string;
+        planner: string;
+        review: string;
     };
 }
 /**
- * Orchestrates a multi-phase planning meeting where AI agent personas
+ * Orchestrates a two-phase planning meeting where AI agent personas
  * collaborate to produce a sprint plan.
  *
- * Flow: CEO Directive → Tech Lead → Architect → Sprint Organizer → Cross-Task Review → Sprint Plan
+ * Flow: CEO Directive → Planner → Cross-Task Review → Sprint Plan
  */
 export declare class PlanningMeeting {
     private projectPath;

package/dist/planning/planning-meeting.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"planning-meeting.d.ts","sourceRoot":"","sources":["../../src/planning/planning-meeting.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,iBAAiB,CAAC;AAOhD,OAAO,EAAyB,KAAK,UAAU,EAAE,MAAM,kBAAkB,CAAC;AAE1E,MAAM,MAAM,aAAa,GACrB,WAAW,GACX,WAAW,GACX,kBAAkB,GAClB,mBAAmB,GACnB,UAAU,CAAC;AAEf,MAAM,WAAW,qBAAqB;IACpC,WAAW,EAAE,MAAM,CAAC;IACpB,QAAQ,EAAE,QAAQ,CAAC;IACnB,GAAG,CAAC,EAAE,CACJ,OAAO,EAAE,MAAM,EACf,KAAK,CAAC,EAAE,MAAM,GAAG,SAAS,GAAG,MAAM,GAAG,OAAO,KAC1C,IAAI,CAAC;CACX;AAED,MAAM,WAAW,qBAAqB;IACpC,IAAI,EAAE,UAAU,CAAC;IACjB,6DAA6D;IAC7D,YAAY,EAAE;QACZ,QAAQ,EAAE,MAAM,CAAC;QACjB,SAAS,EAAE,MAAM,CAAC;QAClB,eAAe,EAAE,MAAM,CAAC;QACxB,eAAe,EAAE,MAAM,CAAC;KACzB,CAAC;CACH;AAED;;;;;GAKG;AACH,qBAAa,eAAe;IAC1B,OAAO,CAAC,WAAW,CAAS;IAC5B,OAAO,CAAC,QAAQ,CAAW;IAC3B,OAAO,CAAC,GAAG,CAGD;gBAEE,MAAM,EAAE,qBAAqB;IAMzC;;OAEG;IACG,GAAG,CACP,SAAS,EAAE,MAAM,EACjB,QAAQ,CAAC,EAAE,MAAM,GAChB,OAAO,CAAC,qBAAqB,CAAC;IAyEjC,OAAO,CAAC,iBAAiB;IAKzB,OAAO,CAAC,gBAAgB;CA8BzB"}
+{"version":3,"file":"planning-meeting.d.ts","sourceRoot":"","sources":["../../src/planning/planning-meeting.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,iBAAiB,CAAC;AAKhD,OAAO,EAAyB,KAAK,UAAU,EAAE,MAAM,kBAAkB,CAAC;AAE1E,MAAM,MAAM,aAAa,GAAG,SAAS,GAAG,QAAQ,GAAG,UAAU,CAAC;AAE9D,MAAM,WAAW,qBAAqB;IACpC,WAAW,EAAE,MAAM,CAAC;IACpB,QAAQ,EAAE,QAAQ,CAAC;IACnB,GAAG,CAAC,EAAE,CACJ,OAAO,EAAE,MAAM,EACf,KAAK,CAAC,EAAE,MAAM,GAAG,SAAS,GAAG,MAAM,GAAG,OAAO,KAC1C,IAAI,CAAC;CACX;AAED,MAAM,WAAW,qBAAqB;IACpC,IAAI,EAAE,UAAU,CAAC;IACjB,6DAA6D;IAC7D,YAAY,EAAE;QACZ,OAAO,EAAE,MAAM,CAAC;QAChB,MAAM,EAAE,MAAM,CAAC;KAChB,CAAC;CACH;AAED;;;;;GAKG;AACH,qBAAa,eAAe;IAC1B,OAAO,CAAC,WAAW,CAAS;IAC5B,OAAO,CAAC,QAAQ,CAAW;IAC3B,OAAO,CAAC,GAAG,CAGD;gBAEE,MAAM,EAAE,qBAAqB;IAMzC;;OAEG;IACG,GAAG,CACP,SAAS,EAAE,MAAM,EACjB,QAAQ,CAAC,EAAE,MAAM,GAChB,OAAO,CAAC,qBAAqB,CAAC;IA6CjC,OAAO,CAAC,iBAAiB;IAKzB,OAAO,CAAC,gBAAgB;CA8BzB"}

package/dist/planning/sprint-plan.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"sprint-plan.d.ts","sourceRoot":"","sources":["../../src/planning/sprint-plan.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,KAAK,YAAY,EACjB,KAAK,UAAU,EACf,KAAK,YAAY,EAElB,MAAM,iBAAiB,CAAC;AAGzB,MAAM,WAAW,WAAW;IAC1B,iDAAiD;IACjD,KAAK,EAAE,MAAM,CAAC;IACd,KAAK,EAAE,MAAM,CAAC;IACd,WAAW,EAAE,MAAM,CAAC;IACpB,YAAY,EAAE,YAAY,CAAC;IAC3B,QAAQ,EAAE,YAAY,CAAC;IACvB,2DAA2D;IAC3D,UAAU,EAAE,MAAM,CAAC;IACnB,kBAAkB,EAAE,MAAM,EAAE,CAAC;IAC7B,MAAM,EAAE,MAAM,EAAE,CAAC;CAClB;AAED,MAAM,WAAW,cAAc;IAC7B,WAAW,EAAE,MAAM,CAAC;IACpB,UAAU,EAAE,MAAM,CAAC;IACnB,QAAQ,EAAE,KAAK,GAAG,QAAQ,GAAG,MAAM,CAAC;CACrC;AAED,MAAM,WAAW,UAAU;IACzB,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,SAAS,EAAE,MAAM,CAAC;IAClB,KAAK,EAAE,WAAW,EAAE,CAAC;IACrB,KAAK,EAAE,cAAc,EAAE,CAAC;IACxB,aAAa,EAAE,MAAM,CAAC;IACtB,MAAM,EAAE,SAAS,GAAG,UAAU,GAAG,UAAU,GAAG,WAAW,CAAC;IAC1D,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,SAAS,EAAE,MAAM,CAAC;IAClB,SAAS,EAAE,MAAM,CAAC;CACnB;AAED;;GAEG;AACH,wBAAgB,oBAAoB,CAAC,IAAI,EAAE,UAAU,GAAG,MAAM,CAmE7D;AAED;;;GAGG;AACH,wBAAgB,4BAA4B,CAC1C,IAAI,EAAE,UAAU,EAChB,QAAQ,EAAE,MAAM,GACf,UAAU,EAAE,CAgBd;AAED;;;;GAIG;AACH,wBAAgB,qBAAqB,CACnC,GAAG,EAAE,MAAM,EACX,SAAS,EAAE,MAAM,GAChB,UAAU,CA0CZ"}
+{"version":3,"file":"sprint-plan.d.ts","sourceRoot":"","sources":["../../src/planning/sprint-plan.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,KAAK,YAAY,EACjB,KAAK,UAAU,EACf,KAAK,YAAY,EAElB,MAAM,iBAAiB,CAAC;AAGzB,MAAM,WAAW,WAAW;IAC1B,iDAAiD;IACjD,KAAK,EAAE,MAAM,CAAC;IACd,KAAK,EAAE,MAAM,CAAC;IACd,WAAW,EAAE,MAAM,CAAC;IACpB,YAAY,EAAE,YAAY,CAAC;IAC3B,QAAQ,EAAE,YAAY,CAAC;IACvB,2DAA2D;IAC3D,UAAU,EAAE,MAAM,CAAC;IACnB,kBAAkB,EAAE,MAAM,EAAE,CAAC;IAC7B,MAAM,EAAE,MAAM,EAAE,CAAC;CAClB;AAED,MAAM,WAAW,cAAc;IAC7B,WAAW,EAAE,MAAM,CAAC;IACpB,UAAU,EAAE,MAAM,CAAC;IACnB,QAAQ,EAAE,KAAK,GAAG,QAAQ,GAAG,MAAM,CAAC;CACrC;AAED,MAAM,WAAW,UAAU;IACzB,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,SAAS,EAAE,MAAM,CAAC;IAClB,KAAK,EAAE,WAAW,EAAE,CAAC;IACrB,KAAK,EAAE,cAAc,EAAE,CAAC;IACxB,aAAa,EAAE,MAAM,CAAC;IACtB,MAAM,EAAE,SAAS,GAAG,UAAU,GAAG,UAAU,GAAG,WAAW,CAAC;IAC1D,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,SAAS,EAAE,MAAM,CAAC;IAClB,SAAS,EAAE,MAAM,CAAC;CACnB;AAED;;GAEG;AACH,wBAAgB,oBAAoB,CAAC,IAAI,EAAE,UAAU,GAAG,MAAM,CAiE7D;AAED;;;GAGG;AACH,wBAAgB,4BAA4B,CAC1C,IAAI,EAAE,UAAU,EAChB,QAAQ,EAAE,MAAM,GACf,UAAU,EAAE,CAgBd;AAED;;;;GAIG;AACH,wBAAgB,qBAAqB,CACnC,GAAG,EAAE,MAAM,EACX,SAAS,EAAE,MAAM,GAChB,UAAU,CA0CZ"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@locusai/sdk",
-  "version": "0.11.6",
+  "version": "0.11.7",
   "type": "module",
   "main": "./src/index.ts",
   "types": "./src/index.ts",
@@ -30,7 +30,7 @@
     "clean": "rm -rf node_modules"
   },
   "dependencies": {
-    "@locusai/shared": "^0.11.6",
+    "@locusai/shared": "^0.11.7",
     "axios": "^1.13.2",
     "events": "^3.3.0",
     "globby": "^14.0.2"