@teammates/cli 0.3.1 → 0.3.2

package/dist/index.d.ts

@@ -2,6 +2,11 @@ export type { AgentAdapter, InstalledService, RecallContext, RosterEntry, } from
 export { buildTeammatePrompt, formatHandoffContext, queryRecallContext, syncRecallIndex, } from "./adapter.js";
 export { type AgentPreset, CliProxyAdapter, type CliProxyOptions, PRESETS, } from "./adapters/cli-proxy.js";
 export { EchoAdapter } from "./adapters/echo.js";
+export type { BannerInfo, ServiceInfo, ServiceStatus } from "./banner.js";
+export { AnimatedBanner } from "./banner.js";
+export type { CliArgs } from "./cli-args.js";
+export { findTeammatesDir, PKG_VERSION, parseCliArgs } from "./cli-args.js";
 export { Orchestrator, type OrchestratorConfig, type TeammateStatus, } from "./orchestrator.js";
 export { Registry } from "./registry.js";
-export type { DailyLog, HandoffEnvelope, OrchestratorEvent, OwnershipRules, SandboxLevel, TaskAssignment, TaskResult, TeammateConfig, } from "./types.js";
+export { tp } from "./theme.js";
+export type { DailyLog, HandoffEnvelope, OrchestratorEvent, OwnershipRules, QueueEntry, SandboxLevel, SlashCommand, TaskAssignment, TaskResult, TeammateConfig, } from "./types.js";

package/dist/index.js

@@ -2,5 +2,8 @@
 export { buildTeammatePrompt, formatHandoffContext, queryRecallContext, syncRecallIndex, } from "./adapter.js";
 export { CliProxyAdapter, PRESETS, } from "./adapters/cli-proxy.js";
 export { EchoAdapter } from "./adapters/echo.js";
+export { AnimatedBanner } from "./banner.js";
+export { findTeammatesDir, PKG_VERSION, parseCliArgs } from "./cli-args.js";
 export { Orchestrator, } from "./orchestrator.js";
 export { Registry } from "./registry.js";
+export { tp } from "./theme.js";

package/dist/onboard.js

@@ -225,82 +225,82 @@ export async function buildImportAdaptationPrompt(teammatesDir, teammateNames, s
         teammateSections.push(`### @${name}\n${soulBlock}${wisdomBlock}`);
     }
     const projectDir = dirname(teammatesDir);
-    return `You are adapting an imported team to a new project. This is a non-interactive session — complete ALL work without pausing. Do not ask for confirmation or wait for user input.
-
-**Source project:** \`${sourceProjectPath}\`
-**Target project:** \`${projectDir}\`
-**Target .teammates/ directory:** \`${teammatesDir}\`
-**Imported teammates:** ${teammateNames.map((n) => `@${n}`).join(", ")}
-
-> **IMPORTANT:** The \`example/\` directory inside \`.teammates/\` is a **template reference**, NOT a teammate. Do not adapt it, rename it, or treat it as a teammate. When creating new teammates, never use "example" as a folder name.
-
-## Imported Teammates (from source project)
-
-${teammateSections.join("\n\n---\n\n")}
-
-## Instructions
-
-Complete these steps in order. Do NOT pause, ask questions, or wait for approval. Make all changes directly.
-
-### Step 1: Scan This Project
-
-Read the project root to understand its structure:
-- Package manifest, README, config files
-- Major subsystems, languages, frameworks, file patterns
-- Dependency flow and architecture
-
-### Step 2: Adapt EVERY Imported Teammate
-
-This is the most important step. For EACH imported teammate listed above, you MUST edit their SOUL.md and WISDOM.md to reflect THIS project, not the source project.
-
-For each teammate's **SOUL.md**:
-
-1. **Add a "Previous Projects" section** (place it after Ethics). Compress what the teammate did in the source project:
-   \`\`\`markdown
-   ## Previous Projects
-
-   ### <source-project-name>
-   - **Role**: <one-line summary of what they did>
-   - **Stack**: <key technologies they worked with>
-   - **Domains**: <what they owned — file patterns or subsystem names>
-   - **Key learnings**: <1-3 bullets of notable patterns, decisions, or lessons>
-   \`\`\`
-
-2. **Rewrite project-specific sections** for THIS project:
-   - **Preserve**: Identity (name, personality), Core Principles, Ethics
-   - **Rewrite completely**: Ownership (primary/secondary file globs for THIS project's actual files), Boundaries, Capabilities (commands, file patterns, technologies for THIS project), Routing keywords, Quality Bar
-   - **Update**: All codebase-specific references — paths, package names, tools, teammate names must reference THIS project
-
-For each teammate's **WISDOM.md**:
-- Add a "Previous Projects" note at the top
-- Keep universal wisdom entries (general principles, patterns)
-- Remove entries that reference source project paths, architecture, or tools not used here
-- Adapt entries with transferable knowledge but old-project-specific details
-
-### Step 3: Evaluate Gaps and Create New Teammates
-
-After adapting all existing teammates, check if THIS project has major subsystems that no teammate covers. If so, create new teammates:
-- Create \`${teammatesDir}/<name>/\` with SOUL.md, WISDOM.md, and \`memory/\`
-- Use the template at \`${teammatesDir}/TEMPLATE.md\` for structure
-- WISDOM.md starts with one creation entry
-
-If a teammate's domain doesn't exist at all in this project and their skills aren't transferable, delete their directory under \`${teammatesDir}\`.
-
-### Step 4: Update Framework Files
-
-- Update \`${teammatesDir}/README.md\` with the final roster
-- Update \`${teammatesDir}/CROSS-TEAM.md\` ownership table
-
-### Step 5: Verify
-
-- Every teammate has SOUL.md and WISDOM.md adapted to THIS project
-- Ownership globs reference actual files in THIS project
-- Boundaries reference correct teammate names
-- Previous Projects sections are present for all imported teammates
-- CROSS-TEAM.md has one row per teammate
-
-## Critical Reminder
-
+    return `You are adapting an imported team to a new project. This is a non-interactive session — complete ALL work without pausing. Do not ask for confirmation or wait for user input.
+
+**Source project:** \`${sourceProjectPath}\`
+**Target project:** \`${projectDir}\`
+**Target .teammates/ directory:** \`${teammatesDir}\`
+**Imported teammates:** ${teammateNames.map((n) => `@${n}`).join(", ")}
+
+> **IMPORTANT:** The \`example/\` directory inside \`.teammates/\` is a **template reference**, NOT a teammate. Do not adapt it, rename it, or treat it as a teammate. When creating new teammates, never use "example" as a folder name.
+
+## Imported Teammates (from source project)
+
+${teammateSections.join("\n\n---\n\n")}
+
+## Instructions
+
+Complete these steps in order. Do NOT pause, ask questions, or wait for approval. Make all changes directly.
+
+### Step 1: Scan This Project
+
+Read the project root to understand its structure:
+- Package manifest, README, config files
+- Major subsystems, languages, frameworks, file patterns
+- Dependency flow and architecture
+
+### Step 2: Adapt EVERY Imported Teammate
+
+This is the most important step. For EACH imported teammate listed above, you MUST edit their SOUL.md and WISDOM.md to reflect THIS project, not the source project.
+
+For each teammate's **SOUL.md**:
+
+1. **Add a "Previous Projects" section** (place it after Ethics). Compress what the teammate did in the source project:
+   \`\`\`markdown
+   ## Previous Projects
+
+   ### <source-project-name>
+   - **Role**: <one-line summary of what they did>
+   - **Stack**: <key technologies they worked with>
+   - **Domains**: <what they owned — file patterns or subsystem names>
+   - **Key learnings**: <1-3 bullets of notable patterns, decisions, or lessons>
+   \`\`\`
+
+2. **Rewrite project-specific sections** for THIS project:
+   - **Preserve**: Identity (name, personality), Core Principles, Ethics
+   - **Rewrite completely**: Ownership (primary/secondary file globs for THIS project's actual files), Boundaries, Capabilities (commands, file patterns, technologies for THIS project), Routing keywords, Quality Bar
+   - **Update**: All codebase-specific references — paths, package names, tools, teammate names must reference THIS project
+
+For each teammate's **WISDOM.md**:
+- Add a "Previous Projects" note at the top
+- Keep universal wisdom entries (general principles, patterns)
+- Remove entries that reference source project paths, architecture, or tools not used here
+- Adapt entries with transferable knowledge but old-project-specific details
+
+### Step 3: Evaluate Gaps and Create New Teammates
+
+After adapting all existing teammates, check if THIS project has major subsystems that no teammate covers. If so, create new teammates:
+- Create \`${teammatesDir}/<name>/\` with SOUL.md, WISDOM.md, and \`memory/\`
+- Use the template at \`${teammatesDir}/TEMPLATE.md\` for structure
+- WISDOM.md starts with one creation entry
+
+If a teammate's domain doesn't exist at all in this project and their skills aren't transferable, delete their directory under \`${teammatesDir}\`.
+
+### Step 4: Update Framework Files
+
+- Update \`${teammatesDir}/README.md\` with the final roster
+- Update \`${teammatesDir}/CROSS-TEAM.md\` ownership table
+
+### Step 5: Verify
+
+- Every teammate has SOUL.md and WISDOM.md adapted to THIS project
+- Ownership globs reference actual files in THIS project
+- Boundaries reference correct teammate names
+- Previous Projects sections are present for all imported teammates
+- CROSS-TEAM.md has one row per teammate
+
+## Critical Reminder
+
 The PRIMARY goal is adapting the imported teammates. Every SOUL.md must be rewritten so the teammate understands THIS project's codebase, not the source project's. If you only have time for one thing, adapt the existing teammates — that is more important than creating new ones.`;
 }
 /**
@@ -326,95 +326,95 @@ export async function getOnboardingPrompt(projectDir) {
     return wrapPrompt(BUILTIN_ONBOARDING, projectDir);
 }
 function wrapPrompt(onboardingContent, projectDir) {
-    return `You are setting up the teammates framework for a project.
-
-**Target project directory:** ${projectDir}
-
-**Framework files have already been copied** into \`${projectDir}/.teammates/\` from the template. The following files are already in place:
-- CROSS-TEAM.md — fill in the Ownership Scopes table as you create teammates
-- PROTOCOL.md — team protocol (ready to use)
-- TEMPLATE.md — reference for creating teammate SOUL.md and WISDOM.md files
-- USER.md — user profile (gitignored, user fills in later)
-- README.md — update with project-specific roster and info
-- .gitignore — configured for USER.md and .index/
-- example/ — example SOUL.md and WISDOM.md for reference
-
-**Your job is to:**
-1. Analyze the codebase (Step 1)
-2. Design the team roster (Step 2)
-3. Create teammate folders with SOUL.md and WISDOM.md (Step 3) — use TEMPLATE.md for the structure
-4. Update README.md and CROSS-TEAM.md with the roster info (Step 3)
-5. Verify everything is in place (Step 4)
-
-You do NOT need to create the framework files listed above — they're already there.
-
-> **IMPORTANT:** The \`example/\` directory is a **template reference**, NOT a teammate. Do not modify it or treat it as a teammate. Never name a new teammate "example".
-
-Follow the onboarding instructions below. This is a non-interactive session — complete ALL work without pausing. Do not ask for confirmation or wait for user input. Work through each step and make all changes directly.
-
----
-
+    return `You are setting up the teammates framework for a project.
+
+**Target project directory:** ${projectDir}
+
+**Framework files have already been copied** into \`${projectDir}/.teammates/\` from the template. The following files are already in place:
+- CROSS-TEAM.md — fill in the Ownership Scopes table as you create teammates
+- PROTOCOL.md — team protocol (ready to use)
+- TEMPLATE.md — reference for creating teammate SOUL.md and WISDOM.md files
+- USER.md — user profile (gitignored, user fills in later)
+- README.md — update with project-specific roster and info
+- .gitignore — configured for USER.md and .index/
+- example/ — example SOUL.md and WISDOM.md for reference
+
+**Your job is to:**
+1. Analyze the codebase (Step 1)
+2. Design the team roster (Step 2)
+3. Create teammate folders with SOUL.md and WISDOM.md (Step 3) — use TEMPLATE.md for the structure
+4. Update README.md and CROSS-TEAM.md with the roster info (Step 3)
+5. Verify everything is in place (Step 4)
+
+You do NOT need to create the framework files listed above — they're already there.
+
+> **IMPORTANT:** The \`example/\` directory is a **template reference**, NOT a teammate. Do not modify it or treat it as a teammate. Never name a new teammate "example".
+
+Follow the onboarding instructions below. This is a non-interactive session — complete ALL work without pausing. Do not ask for confirmation or wait for user input. Work through each step and make all changes directly.
+
+---
+
 ${onboardingContent}`;
 }
-const BUILTIN_ONBOARDING = `# Teammates Onboarding
-
-You are going to analyze a codebase and create a set of AI teammates — persistent personas that each own a slice of the project. Follow these steps in order.
-
-## Step 1: Analyze the Codebase
-
-Read the project's entry points to understand its structure:
-- README, CONTRIBUTING, or similar docs
-- Package manifest (package.json, Cargo.toml, pyproject.toml, go.mod, etc.)
-- Top-level directory structure
-- Key configuration files
-
-Identify:
-1. **Major domains/subsystems** — distinct areas of the codebase
-2. **Dependency flow** — which layers depend on which
-3. **Key technologies** — languages, frameworks, tools per area
-4. **File patterns** — glob patterns for each domain
-
-## Step 2: Design the Team
-
-Based on your analysis, design a roster of teammates:
-- **Aim for 3–7 teammates.** Fewer for small projects, more for monorepos.
-- **Each teammate owns a distinct domain** with minimal overlap.
-- **Pick short, memorable names** — one word, evocative of the domain.
-
-For each teammate, define:
-- Name and one-line persona
-- Primary ownership (file patterns)
-- Key technologies
-- Boundaries (what they do NOT own)
-
-## Step 3: Create the Directory Structure
-
-Create teammate folders under \`.teammates/\`:
-
-### Teammate folders
-For each teammate, create \`.teammates/<name>/\` with:
-
-**SOUL.md** — Use the template from \`.teammates/TEMPLATE.md\`. Fill in identity, core principles, boundaries, capabilities, ownership, ethics.
-
-**WISDOM.md** — Start with one entry recording creation and key decisions.
-
-**memory/** — Empty directory for daily logs.
-
-### Update framework files
-- Update \`.teammates/README.md\` with the roster table, dependency flow, and routing guide
-- Update \`.teammates/CROSS-TEAM.md\` Ownership Scopes table with one row per teammate
-
-## Step 4: Verify
-
-Check:
-- Every roster teammate has a folder with SOUL.md and WISDOM.md
-- Ownership globs cover the codebase without major gaps
-- Boundaries reference the correct owning teammate
-- CROSS-TEAM.md Ownership Scopes table has one row per teammate with correct paths
-- .gitignore is in place (USER.md not committed)
-
-## Tips
-- Small projects are fine with 2–3 teammates
-- WISDOM.md starts light — just one creation entry
-- Prompt the user to fill in USER.md after setup
+const BUILTIN_ONBOARDING = `# Teammates Onboarding
+
+You are going to analyze a codebase and create a set of AI teammates — persistent personas that each own a slice of the project. Follow these steps in order.
+
+## Step 1: Analyze the Codebase
+
+Read the project's entry points to understand its structure:
+- README, CONTRIBUTING, or similar docs
+- Package manifest (package.json, Cargo.toml, pyproject.toml, go.mod, etc.)
+- Top-level directory structure
+- Key configuration files
+
+Identify:
+1. **Major domains/subsystems** — distinct areas of the codebase
+2. **Dependency flow** — which layers depend on which
+3. **Key technologies** — languages, frameworks, tools per area
+4. **File patterns** — glob patterns for each domain
+
+## Step 2: Design the Team
+
+Based on your analysis, design a roster of teammates:
+- **Aim for 3–7 teammates.** Fewer for small projects, more for monorepos.
+- **Each teammate owns a distinct domain** with minimal overlap.
+- **Pick short, memorable names** — one word, evocative of the domain.
+
+For each teammate, define:
+- Name and one-line persona
+- Primary ownership (file patterns)
+- Key technologies
+- Boundaries (what they do NOT own)
+
+## Step 3: Create the Directory Structure
+
+Create teammate folders under \`.teammates/\`:
+
+### Teammate folders
+For each teammate, create \`.teammates/<name>/\` with:
+
+**SOUL.md** — Use the template from \`.teammates/TEMPLATE.md\`. Fill in identity, core principles, boundaries, capabilities, ownership, ethics.
+
+**WISDOM.md** — Start with one entry recording creation and key decisions.
+
+**memory/** — Empty directory for daily logs.
+
+### Update framework files
+- Update \`.teammates/README.md\` with the roster table, dependency flow, and routing guide
+- Update \`.teammates/CROSS-TEAM.md\` Ownership Scopes table with one row per teammate
+
+## Step 4: Verify
+
+Check:
+- Every roster teammate has a folder with SOUL.md and WISDOM.md
+- Ownership globs cover the codebase without major gaps
+- Boundaries reference the correct owning teammate
+- CROSS-TEAM.md Ownership Scopes table has one row per teammate with correct paths
+- .gitignore is in place (USER.md not committed)
+
+## Tips
+- Small projects are fine with 2–3 teammates
+- WISDOM.md starts light — just one creation entry
+- Prompt the user to fill in USER.md after setup
 `;

package/dist/registry.test.js

@@ -142,18 +142,18 @@ describe("Registry role parsing", () => {
 });
 describe("Registry ownership parsing", () => {
     it("parses primary ownership patterns", async () => {
-        const soul = `# Beacon
-
-## Ownership
-
-### Primary
-
-- \`recall/src/**\` — All source files
-- \`recall/package.json\` — Package manifest
-
-### Secondary
-
-- \`.teammates/.index/**\` — Vector indexes
+        const soul = `# Beacon
+
+## Ownership
+
+### Primary
+
+- \`recall/src/**\` — All source files
+- \`recall/package.json\` — Package manifest
+
+### Secondary
+
+- \`.teammates/.index/**\` — Vector indexes
 `;
         await createTeammate("beacon", soul);
         const registry = new Registry(tempDir);
@@ -174,17 +174,17 @@ describe("Registry ownership parsing", () => {
 });
 describe("Registry routing keyword parsing", () => {
     it("parses routing keywords from ### Routing section", async () => {
-        const soul = `# Beacon
-
-## Ownership
-
-### Primary
-
-- \`recall/src/**\` — All source files
-
-### Routing
-
-- \`search\`, \`embeddings\`, \`vector\`, \`semantic\`
+        const soul = `# Beacon
+
+## Ownership
+
+### Primary
+
+- \`recall/src/**\` — All source files
+
+### Routing
+
+- \`search\`, \`embeddings\`, \`vector\`, \`semantic\`
 `;
         await createTeammate("beacon", soul);
         const registry = new Registry(tempDir);

package/dist/theme.d.ts

@@ -54,3 +54,16 @@ export declare function theme(): Theme;
 export declare function setTheme(t: Theme): void;
 /** Format a Color as a hex string for display. */
 export declare function colorToHex(c: Color): string;
+export declare const tp: {
+    accent: (s: string) => import("@teammates/consolonia").StyledSpan;
+    accentBright: (s: string) => import("@teammates/consolonia").StyledSpan;
+    accentDim: (s: string) => import("@teammates/consolonia").StyledSpan;
+    text: (s: string) => import("@teammates/consolonia").StyledSpan;
+    muted: (s: string) => import("@teammates/consolonia").StyledSpan;
+    dim: (s: string) => import("@teammates/consolonia").StyledSpan;
+    success: (s: string) => import("@teammates/consolonia").StyledSpan;
+    warning: (s: string) => import("@teammates/consolonia").StyledSpan;
+    error: (s: string) => import("@teammates/consolonia").StyledSpan;
+    info: (s: string) => import("@teammates/consolonia").StyledSpan;
+    bold: (s: string) => import("@teammates/consolonia").StyledSpan;
+};

package/dist/theme.js

@@ -52,3 +52,21 @@ export function colorToHex(c) {
     const b = c.b.toString(16).padStart(2, "0");
     return `#${r}${g}${b}`.toUpperCase();
 }
+// ── Themed pen shortcuts ────────────────────────────────────────────
+//
+// Thin wrappers that read from the active theme() at call time, so
+// every styled span picks up the current palette automatically.
+import { pen } from "@teammates/consolonia";
+export const tp = {
+    accent: (s) => pen.fg(theme().accent)(s),
+    accentBright: (s) => pen.fg(theme().accentBright)(s),
+    accentDim: (s) => pen.fg(theme().accentDim)(s),
+    text: (s) => pen.fg(theme().text)(s),
+    muted: (s) => pen.fg(theme().textMuted)(s),
+    dim: (s) => pen.fg(theme().textDim)(s),
+    success: (s) => pen.fg(theme().success)(s),
+    warning: (s) => pen.fg(theme().warning)(s),
+    error: (s) => pen.fg(theme().error)(s),
+    info: (s) => pen.fg(theme().info)(s),
+    bold: (s) => pen.bold.fg(theme().text)(s),
+};

package/dist/types.d.ts

@@ -103,3 +103,33 @@ export type OrchestratorEvent = {
     teammate: string;
     error: string;
 };
+/** A task queue entry — either an agent task or an internal operation. */
+export type QueueEntry = {
+    type: "agent";
+    teammate: string;
+    task: string;
+} | {
+    type: "compact";
+    teammate: string;
+    task: string;
+} | {
+    type: "retro";
+    teammate: string;
+    task: string;
+} | {
+    type: "btw";
+    teammate: string;
+    task: string;
+} | {
+    type: "debug";
+    teammate: string;
+    task: string;
+};
+/** A registered slash command. */
+export interface SlashCommand {
+    name: string;
+    aliases: string[];
+    usage: string;
+    description: string;
+    run: (args: string) => Promise<void>;
+}

package/package.json

@@ -1,48 +1,48 @@
-{
-  "name": "@teammates/cli",
-  "version": "0.3.1",
-  "description": "Agent-agnostic CLI for teammates. Routes tasks, manages handoffs, and plugs into any coding agent backend.",
-  "type": "module",
-  "main": "dist/index.js",
-  "types": "dist/index.d.ts",
-  "files": [
-    "dist",
-    "template"
-  ],
-  "bin": {
-    "teammates": "dist/cli.js"
-  },
-  "scripts": {
-    "build": "tsc",
-    "dev": "tsc --watch",
-    "test": "vitest run",
-    "test:coverage": "vitest run --coverage",
-    "test:watch": "vitest",
-    "typecheck": "tsc --noEmit"
-  },
-  "keywords": [
-    "teammates",
-    "ai",
-    "orchestrator",
-    "agent",
-    "handoff",
-    "cli"
-  ],
-  "license": "MIT",
-  "dependencies": {
-    "@github/copilot-sdk": "^0.1.32",
-    "@teammates/consolonia": "0.3.1",
-    "@teammates/recall": "0.3.1",
-    "chalk": "^5.6.2",
-    "ora": "^9.3.0"
-  },
-  "devDependencies": {
-    "@types/node": "^25.5.0",
-    "@vitest/coverage-v8": "^4.1.0",
-    "typescript": "^5.5.0",
-    "vitest": "^4.1.0"
-  },
-  "engines": {
-    "node": ">=20.0.0"
-  }
-}
+{
+  "name": "@teammates/cli",
+  "version": "0.3.2",
+  "description": "Agent-agnostic CLI for teammates. Routes tasks, manages handoffs, and plugs into any coding agent backend.",
+  "type": "module",
+  "main": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "files": [
+    "dist",
+    "template"
+  ],
+  "bin": {
+    "teammates": "dist/cli.js"
+  },
+  "scripts": {
+    "build": "tsc",
+    "dev": "tsc --watch",
+    "test": "vitest run",
+    "test:coverage": "vitest run --coverage",
+    "test:watch": "vitest",
+    "typecheck": "tsc --noEmit"
+  },
+  "keywords": [
+    "teammates",
+    "ai",
+    "orchestrator",
+    "agent",
+    "handoff",
+    "cli"
+  ],
+  "license": "MIT",
+  "dependencies": {
+    "@github/copilot-sdk": "^0.1.32",
+    "@teammates/consolonia": "0.3.2",
+    "@teammates/recall": "0.3.2",
+    "chalk": "^5.6.2",
+    "ora": "^9.3.0"
+  },
+  "devDependencies": {
+    "@types/node": "^25.5.0",
+    "@vitest/coverage-v8": "^4.1.0",
+    "typescript": "^5.5.0",
+    "vitest": "^4.1.0"
+  },
+  "engines": {
+    "node": ">=20.0.0"
+  }
+}