@kendoo.agentdesk/agentdesk 0.12.0 → 0.12.1

package/README.md

@@ -80,6 +80,8 @@ agentdesk update                       Update to the latest version
 |------|-------------|
 | `--description`, `-d` | Task description or requirements |
 | `--cwd` | Working directory (defaults to current) |
+| `--phased` | Run in phased mode (INTAKE → PLAN → EXECUTION) — each phase runs as a separate Claude process for better context handling. Also available as a toggle in the dashboard when starting a session. |
+| `--child-strategy` | How to handle child tasks: `inline` (default) or `branch` |
 
 ## Configuration
 

package/bin/agentdesk.mjs

@@ -71,6 +71,7 @@ if (!command || command === "help" || command === "--help") {
   Options:
     --description, -d    Task description or requirements
     --cwd                Working directory (defaults to current)
+    --phased             Run in phased mode (INTAKE → PLAN → EXECUTION)
     --child-strategy     How to handle child tasks: "inline" (default) or "branch"
 
 
@@ -84,6 +85,7 @@ if (!command || command === "help" || command === "--help") {
 
   Examples:
     agentdesk team KEN-517
+    agentdesk team KEN-517 --phased
     agentdesk team -d "Fix the checkout total calculation"
     agentdesk team -d "Add Google OAuth to the login page"
 

package/cli/agents.mjs

@@ -5,7 +5,7 @@ export const BUILT_IN_AGENTS = {
     badge: "●● JANE ●●",
     role: "Product Analyst / Team Lead",
     description: "leads the session, clarifies requirements, coordinates the team, manages tracker status, decomposes large tasks into subtasks",
-    groundRules: "Jane focuses on requirements, scope, and coordination — she does NOT read code, inspect functions, or reference technical implementation details (no file names, function names, variable names, or code snippets). She speaks from a product perspective: user impact, acceptance criteria, scope decisions. She creates tracker tasks when needed, manages status transitions, posts the session start/end comments, and decomposes large features into subtasks (basic vs deferred).",
+    groundRules: "Jane is strictly non-technical. She MUST NEVER: use tools (Read, Grep, Glob, Edit, Write, Bash), read or reference code, mention file names, function names, variable names, code snippets, terminal commands, or implementation details. She MUST NEVER write or modify code. Her language is product-only: user stories, acceptance criteria, scope, priorities, stakeholder impact. If she needs technical context, she asks Dennis or Sam to investigate and report back. She creates tracker tasks, manages status transitions, posts session start/end comments, and decomposes large features into subtasks.",
     planning: "Requirements: what we're building, acceptance criteria, scope. Flags UI tasks for Luna.",
     execution: {
       step: "Jane wraps up",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kendoo.agentdesk/agentdesk",
-  "version": "0.12.0",
+  "version": "0.12.1",
   "description": "AI team orchestrator for Claude Code — run collaborative agent sessions from your terminal",
   "type": "module",
   "bin": {

package/prompts/phased.md

@@ -189,7 +189,7 @@ Speaking order:
 
 ## YOUR MISSION: PLAN
 
-Jane restates the task concisely. Then each agent contributes their perspective:
+Jane restates the task in product terms (no code, no file names, no technical jargon). Then each agent contributes their perspective:
 
 {{PLANNING_ORDER}}
 

package/prompts/team.md

@@ -413,7 +413,7 @@ After assessing the task, Jane evaluates whether it is **too large for a single
 
 ## PLAN (1-2 rounds max)
 
-Jane restates the task concisely. Then each agent contributes their perspective in one pass:
+Jane restates the task in product terms (no code, no file names, no technical jargon). Then each agent contributes their perspective in one pass:
 
 {{PLANNING_ORDER}}