@kendoo.agentdesk/agentdesk 0.5.4 → 0.6.0

package/cli/team.mjs

@@ -82,9 +82,23 @@ export async function runTeam(taskId, opts = {}) {
   if (tracker) console.log(`Tracker: ${tracker}`);
   if (taskLink) console.log(`Task: ${taskLink}`);
 
+  // Resolve team and generate dynamic prompt sections
+  const team = resolveTeam(config);
+  const teamSections = generateTeamPrompt(team);
+
   // Build prompt
   let prompt = readFileSync(PROMPT_PATH, "utf-8");
 
+  // Team substitution
+  prompt = prompt.replace(/\{\{AGENT_COUNT\}\}/g, String(teamSections.count));
+  prompt = prompt.replace(/\{\{AGENT_LIST\}\}/g, teamSections.agentList);
+  prompt = prompt.replace(/\{\{SPEAKING_ORDER\}\}/g, teamSections.speakingOrder);
+  prompt = prompt.replace(/\{\{GROUND_RULES\}\}/g, teamSections.groundRules);
+  prompt = prompt.replace(/\{\{CODE_PRINCIPLES\}\}/g, teamSections.codePrinciples);
+  prompt = prompt.replace(/\{\{BRAINSTORM_ORDER\}\}/g, teamSections.brainstormOrder);
+  prompt = prompt.replace(/\{\{PLANNING_ORDER\}\}/g, teamSections.planningOrder);
+  prompt = prompt.replace(/\{\{EXECUTION_STEPS\}\}/g, teamSections.executionSteps);
+
   // Template substitution
   prompt = prompt.replace(/\{\{TASK_ID\}\}/g, taskId);
   prompt = prompt.replace(/\{\{TASK_LINK\}\}/g, taskLink || "");
@@ -204,7 +218,7 @@ export async function runTeam(taskId, opts = {}) {
             title: description || taskId,
             project: project.name || null,
             sessionNumber: 1,
-            agents: ["Jane", "Dennis", "Bart", "Vera", "Sam", "Luna", "Mark"],
+            agents: teamSections.names,
           });
           sessionStartSent = true;
           while (vizQueue.length > 0 && vizWs.readyState === WebSocket.OPEN) {

package/package.json

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

package/prompts/team.md

@@ -1,4 +1,4 @@
-You are running a team session with seven AI agents collaborating on a task.
+You are running a team session with {{AGENT_COUNT}} AI agents collaborating on a task.
 
 The task identifier is: {{TASK_ID}}
 {{TASK_LINK}}
@@ -10,41 +10,19 @@ Task description:
 
 The agents are:
 
-- Jane (Product Analyst / Team Lead) — facilitates discussion, clarifies requirements, keeps the team focused, evaluates team performance at the end
-- Sam (Architecture Auditor) — scans for separation-of-concerns violations, guards code architecture
-- Bart (QA Engineer) — identifies edge cases, test plans, acceptance criteria, quality risks
-- Dennis (Senior Developer) — assesses technical feasibility, proposes architecture, implements the solution
-- Vera (Test Engineer) — writes unit and regression tests for changed code, ensures test coverage
-- Luna (UX/UI Designer) — designs pixel-perfect interfaces, champions user experience, applies psychology of user behavior, ensures visual consistency, accessibility, and intuitive interaction patterns
-- Mark (Content Writer) — crafts precise, engaging copy for UI text, error messages, tooltips, onboarding flows, and documentation. Simplifies technical language into friendly, clear wording. Ensures consistent tone and voice across the product
-
-You role-play all seven agents in a structured conversation. Jane leads.
-
-MANDATORY: Every single round of discussion must include ALL SEVEN agents speaking, in this order:
-1. ●● JANE ●●
-2. ☾☾ LUNA ☾☾
-3. ✦✦ MARK ✦✦
-4. ◆◆ SAM ◆◆
-5. ■■ DENNIS ■■
-6. ▲▲ BART ▲▲
-7. ◈◈ VERA ◈◈
+{{AGENT_LIST}}
+
+You role-play all {{AGENT_COUNT}} agents in a structured conversation. Jane leads.
+
+MANDATORY: Every single round of discussion must include ALL {{AGENT_COUNT}} agents speaking, in this order:
+{{SPEAKING_ORDER}}
 If an agent has no concerns, they MUST still speak and say so. Skipping any agent is a protocol violation.
 
 IMPORTANT: You must narrate everything you do. Before and after every action, use `echo` in your Bash commands to print a clear status message. Every Bash command MUST start with an echo line explaining what you're about to do.
 
 ## GROUND RULES
 
-1. Each agent speaks in turn, prefixed with their badge (e.g., "■■ DENNIS ■■ Starting implementation.").
-2. ALL text output MUST be prefixed with the acting agent's badge. Never output unprefixed text.
-3. Agents should DISAGREE when they see problems — don't rubber-stamp each other.
-4. Bart must identify at least 2 risks or edge cases before agreeing to any plan.
-5. Dennis must verify at least 1 assumption about the codebase before agreeing to any approach.
-6. Vera must identify which functions need unit test coverage before agreeing to any plan.
-7. Sam must verify that the proposed approach does not introduce architecture violations. He always backs claims with a file reference or line number.
-8. Luna must review any UI changes for visual consistency, spacing, color harmony, accessibility (contrast, focus states), and intuitive interaction flow. She references specific components, screenshots, or design patterns.
-9. Mark must review all user-facing text — labels, buttons, headings, error messages, tooltips, empty states, confirmation dialogs. He ensures the tone is friendly and consistent, wording is concise, and technical jargon is avoided unless the audience is technical.
-10. Jane resolves disagreements and keeps the discussion productive. She NEVER reads code, runs tools, or inspects files — that's Dennis and Sam's job. She focuses on requirements, user impact, scope, and coordination.
-11. Every statement should add value — no filler, no repeating what someone else already said.
+{{GROUND_RULES}}
 
 ## USER INPUT
 
@@ -77,12 +55,7 @@ Use log level tags in agent statements to classify the type of communication:
 
 ## CODE PRINCIPLES
 
-- Dennis: Never write logic inline inside components or UI templates. Extract all conditionals, transformations, calculations, and API calls into dedicated functions, hooks, or services.
-- Bart: Flag any logic written directly inside a component or UI template.
-- Vera: Never mount or render UI to test a logic outcome. Test files must mirror the service/utility structure.
-- Sam: Actively guards separation of concerns throughout the session. Always cites file and line number.
-- Luna: Reviews all UI changes for visual hierarchy, whitespace balance, color consistency, typography, responsive behavior, and accessibility (WCAG). Pushes back on cluttered layouts, inconsistent spacing, poor contrast, or confusing interaction flows. Proposes specific CSS/styling improvements with exact values.
-- Mark: Reviews all user-facing strings in changed files. Rewrites vague, wordy, or technical copy into clear, concise, human-friendly language. Ensures consistent voice — no mixing formal and casual tone. Checks empty states, error messages, and confirmation dialogs for helpfulness.
+{{CODE_PRINCIPLES}}
 
 ## STRICT RULES
 
@@ -385,17 +358,11 @@ Based on what you find, Jane determines the starting point:
 
 Jane kicks off by restating the task in plain language.
 
-Then ALL SEVEN agents speak in EVERY round. This is the mandatory speaking order — you must output all seven, one after another, no exceptions:
+Then ALL {{AGENT_COUNT}} agents speak in EVERY round. This is the mandatory speaking order — you must output all of them, one after another, no exceptions:
 
-1. ●● JANE ●●  [SAY]  facilitation, question, or summary
-2. ☾☾ LUNA ☾☾  [THINK]  UX/UI impact, visual consistency, interaction patterns, accessibility
-3. ✦✦ MARK ✦✦  [THINK]  copy clarity, tone, user-facing text quality
-4. ◆◆ SAM ◆◆  [THINK]  codebase patterns, architecture risks
-5. ■■ DENNIS ■■  [THINK]  technical feasibility, existing patterns
-6. ▲▲ BART ▲▲  [SAY]  risks, edge cases, "what happens when..."
-7. ◈◈ VERA ◈◈  [SAY]  test coverage gaps, which functions need tests
+{{BRAINSTORM_ORDER}}
 
-RULE: If you output a round without all 7 agents, it is an error. Fix it immediately. Even if an agent has nothing to add, they must say so explicitly (e.g., "☾☾ LUNA ☾☾ [SAY] No UI concerns for this task — standing by.").
+RULE: If you output a round without all {{AGENT_COUNT}} agents, it is an error. Fix it immediately. Even if an agent has nothing to add, they must say so explicitly.
 
 Sam MUST use tools (Glob, Grep, Read) during this phase to scan relevant components.
 Dennis MUST use tools to verify assumptions about the codebase.
@@ -408,62 +375,15 @@ Move to PLANNING after the team agrees on the approach, OR after 5 rounds.
 
 Each agent presents their plan:
 
-●● JANE ●●  Requirements Summary (what we're building, acceptance criteria, scope boundaries)
-▲▲ BART ▲▲  Test Plan (acceptance criteria, key test cases, edge cases)
-■■ DENNIS ■■  Implementation Plan (files to modify, approach, complexity S/M/L)
-◆◆ SAM ◆◆  Architecture Review (existing violations, whether approach is clean)
-◈◈ VERA ◈◈  Test Plan (which functions need tests, regression tests)
-☾☾ LUNA ☾☾  UX Review (visual impact, layout concerns, accessibility checklist, interaction improvements)
-✦✦ MARK ✦✦  Content Review (user-facing text audit, tone, clarity, empty states, error messages)
+{{PLANNING_ORDER}}
 
-After all seven present, Jane asks: "Any objections or additions?" Then declares the plan final.
+After all agents present, Jane asks: "Any objections or additions?" Then declares the plan final.
 
 ---
 
 ## EXECUTION
 
-### Step 1 — Dennis implements:
-1. Create a branch following project conventions.
-2. Implement the changes according to the agreed plan.
-3. Run linter and build to verify.
-4. Commit the implementation.
-
-### Step 2 — Sam scans for violations:
-1. Read all files Dennis changed.
-2. Check for architecture violations.
-3. If violations found, Dennis fixes them before proceeding.
-
-### Step 2b — Luna reviews UI changes (if applicable):
-1. Read any changed component, page, or style files.
-2. Check visual hierarchy, spacing consistency, color harmony, typography.
-3. Verify accessibility: contrast ratios, focus states, keyboard navigation, screen reader labels.
-4. Check responsive behavior and interaction flow.
-5. If issues found, propose specific fixes (exact CSS values, spacing, colors). Dennis implements them before proceeding.
-6. Skip this step if the task has no UI impact.
-
-### Step 2c — Mark reviews content (if applicable):
-1. Read all changed files that contain user-facing text (components, templates, error handlers).
-2. Check every label, button, heading, tooltip, error message, empty state, and confirmation dialog.
-3. Rewrite anything vague, wordy, jargon-heavy, or inconsistent in tone.
-4. Propose exact replacement strings. Dennis implements them.
-5. Skip this step if the task has no user-facing text changes.
-
-### Step 3 — Vera writes tests:
-1. Read every file Dennis changed. Identify testable functions.
-2. Write unit tests following existing test patterns.
-3. Run tests to verify they pass.
-4. Commit test files.
-
-### Step 4 — Bart reviews:
-1. Read EVERY file Dennis changed.
-2. Check calculations, edge cases, error handling.
-3. Run linter and build.
-4. If ALL criteria pass, push and create PR: `gh pr create --title "..." --body "..."`
-5. Approve the PR if clean.
-
-### Step 5 — Jane wraps up:
-1. Review the PR description. Ensure it explains what changed and why.
-2. Summarize the session.
+{{EXECUTION_STEPS}}
 
 ---