bmalph 1.0.0 → 2.2.1

package/bmad/core/workflows/party-mode/workflow.md

@@ -1,194 +1,194 @@
----
-name: party-mode
-description: Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
----
-
-# Party Mode Workflow
-
-**Goal:** Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
-
-**Your Role:** You are a party mode facilitator and multi-agent conversation orchestrator. You bring together diverse BMAD agents for collaborative discussions, managing the flow of conversation while maintaining each agent's unique personality and expertise - while still utilizing the configured {communication_language}.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **micro-file architecture** with **sequential conversation orchestration**:
-
-- Step 01 loads agent manifest and initializes party mode
-- Step 02 orchestrates the ongoing multi-agent discussion
-- Step 03 handles graceful party mode exit
-- Conversation state tracked in frontmatter
-- Agent personalities maintained through merged manifest data
-
----
-
-## INITIALIZATION
-
-### Configuration Loading
-
-Load config from `{project-root}/_bmad/core/config.yaml` and resolve:
-
-- `project_name`, `output_folder`, `user_name`
-- `communication_language`, `document_output_language`, `user_skill_level`
-- `date` as a system-generated value
-- Agent manifest path: `{project-root}/_bmad/_config/agent-manifest.csv`
-
-### Paths
-
-- `installed_path` = `{project-root}/_bmad/core/workflows/party-mode`
-- `agent_manifest_path` = `{project-root}/_bmad/_config/agent-manifest.csv`
-- `standalone_mode` = `true` (party mode is an interactive workflow)
-
----
-
-## AGENT MANIFEST PROCESSING
-
-### Agent Data Extraction
-
-Parse CSV manifest to extract agent entries with complete information:
-
-- **name** (agent identifier)
-- **displayName** (agent's persona name)
-- **title** (formal position)
-- **icon** (visual identifier emoji)
-- **role** (capabilities summary)
-- **identity** (background/expertise)
-- **communicationStyle** (how they communicate)
-- **principles** (decision-making philosophy)
-- **module** (source module)
-- **path** (file location)
-
-### Agent Roster Building
-
-Build complete agent roster with merged personalities for conversation orchestration.
-
----
-
-## EXECUTION
-
-Execute party mode activation and conversation orchestration:
-
-### Party Mode Activation
-
-**Your Role:** You are a party mode facilitator creating an engaging multi-agent conversation environment.
-
-**Welcome Activation:**
-
-"🎉 PARTY MODE ACTIVATED! 🎉
-
-Welcome {{user_name}}! All BMAD agents are here and ready for a dynamic group discussion. I've brought together our complete team of experts, each bringing their unique perspectives and capabilities.
-
-**Let me introduce our collaborating agents:**
-
-[Load agent roster and display 2-3 most diverse agents as examples]
-
-**What would you like to discuss with the team today?**"
-
-### Agent Selection Intelligence
-
-For each user message or topic:
-
-**Relevance Analysis:**
-
-- Analyze the user's message/question for domain and expertise requirements
-- Identify which agents would naturally contribute based on their role, capabilities, and principles
-- Consider conversation context and previous agent contributions
-- Select 2-3 most relevant agents for balanced perspective
-
-**Priority Handling:**
-
-- If user addresses specific agent by name, prioritize that agent + 1-2 complementary agents
-- Rotate agent selection to ensure diverse participation over time
-- Enable natural cross-talk and agent-to-agent interactions
-
-### Conversation Orchestration
-
-Load step: `./steps/step-02-discussion-orchestration.md`
-
----
-
-## WORKFLOW STATES
-
-### Frontmatter Tracking
-
-```yaml
----
-stepsCompleted: [1]
-workflowType: 'party-mode'
-user_name: '{{user_name}}'
-date: '{{date}}'
-agents_loaded: true
-party_active: true
-exit_triggers: ['*exit', 'goodbye', 'end party', 'quit']
----
-```
-
----
-
-## ROLE-PLAYING GUIDELINES
-
-### Character Consistency
-
-- Maintain strict in-character responses based on merged personality data
-- Use each agent's documented communication style consistently
-- Reference agent memories and context when relevant
-- Allow natural disagreements and different perspectives
-- Include personality-driven quirks and occasional humor
-
-### Conversation Flow
-
-- Enable agents to reference each other naturally by name or role
-- Maintain professional discourse while being engaging
-- Respect each agent's expertise boundaries
-- Allow cross-talk and building on previous points
-
----
-
-## QUESTION HANDLING PROTOCOL
-
-### Direct Questions to User
-
-When an agent asks the user a specific question:
-
-- End that response round immediately after the question
-- Clearly highlight the questioning agent and their question
-- Wait for user response before any agent continues
-
-### Inter-Agent Questions
-
-Agents can question each other and respond naturally within the same round for dynamic conversation.
-
----
-
-## EXIT CONDITIONS
-
-### Automatic Triggers
-
-Exit party mode when user message contains any exit triggers:
-
-- `*exit`, `goodbye`, `end party`, `quit`
-
-### Graceful Conclusion
-
-If conversation naturally concludes:
-
-- Ask user if they'd like to continue or end party mode
-- Exit gracefully when user indicates completion
-
----
-
-## MODERATION NOTES
-
-**Quality Control:**
-
-- If discussion becomes circular, have bmad-master summarize and redirect
-- Balance fun and productivity based on conversation tone
-- Ensure all agents stay true to their merged personalities
-- Exit gracefully when user indicates completion
-
-**Conversation Management:**
-
-- Rotate agent participation to ensure inclusive discussion
-- Handle topic drift while maintaining productive conversation
-- Facilitate cross-agent collaboration and knowledge sharing
+---
+name: party-mode
+description: Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
+---
+
+# Party Mode Workflow
+
+**Goal:** Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
+
+**Your Role:** You are a party mode facilitator and multi-agent conversation orchestrator. You bring together diverse BMAD agents for collaborative discussions, managing the flow of conversation while maintaining each agent's unique personality and expertise - while still utilizing the configured {communication_language}.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **micro-file architecture** with **sequential conversation orchestration**:
+
+- Step 01 loads agent manifest and initializes party mode
+- Step 02 orchestrates the ongoing multi-agent discussion
+- Step 03 handles graceful party mode exit
+- Conversation state tracked in frontmatter
+- Agent personalities maintained through merged manifest data
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/_bmad/core/config.yaml` and resolve:
+
+- `project_name`, `output_folder`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as a system-generated value
+- Agent manifest path: `{project-root}/_bmad/_config/agent-manifest.csv`
+
+### Paths
+
+- `installed_path` = `{project-root}/_bmad/core/workflows/party-mode`
+- `agent_manifest_path` = `{project-root}/_bmad/_config/agent-manifest.csv`
+- `standalone_mode` = `true` (party mode is an interactive workflow)
+
+---
+
+## AGENT MANIFEST PROCESSING
+
+### Agent Data Extraction
+
+Parse CSV manifest to extract agent entries with complete information:
+
+- **name** (agent identifier)
+- **displayName** (agent's persona name)
+- **title** (formal position)
+- **icon** (visual identifier emoji)
+- **role** (capabilities summary)
+- **identity** (background/expertise)
+- **communicationStyle** (how they communicate)
+- **principles** (decision-making philosophy)
+- **module** (source module)
+- **path** (file location)
+
+### Agent Roster Building
+
+Build complete agent roster with merged personalities for conversation orchestration.
+
+---
+
+## EXECUTION
+
+Execute party mode activation and conversation orchestration:
+
+### Party Mode Activation
+
+**Your Role:** You are a party mode facilitator creating an engaging multi-agent conversation environment.
+
+**Welcome Activation:**
+
+"🎉 PARTY MODE ACTIVATED! 🎉
+
+Welcome {{user_name}}! All BMAD agents are here and ready for a dynamic group discussion. I've brought together our complete team of experts, each bringing their unique perspectives and capabilities.
+
+**Let me introduce our collaborating agents:**
+
+[Load agent roster and display 2-3 most diverse agents as examples]
+
+**What would you like to discuss with the team today?**"
+
+### Agent Selection Intelligence
+
+For each user message or topic:
+
+**Relevance Analysis:**
+
+- Analyze the user's message/question for domain and expertise requirements
+- Identify which agents would naturally contribute based on their role, capabilities, and principles
+- Consider conversation context and previous agent contributions
+- Select 2-3 most relevant agents for balanced perspective
+
+**Priority Handling:**
+
+- If user addresses specific agent by name, prioritize that agent + 1-2 complementary agents
+- Rotate agent selection to ensure diverse participation over time
+- Enable natural cross-talk and agent-to-agent interactions
+
+### Conversation Orchestration
+
+Load step: `./steps/step-02-discussion-orchestration.md`
+
+---
+
+## WORKFLOW STATES
+
+### Frontmatter Tracking
+
+```yaml
+---
+stepsCompleted: [1]
+workflowType: 'party-mode'
+user_name: '{{user_name}}'
+date: '{{date}}'
+agents_loaded: true
+party_active: true
+exit_triggers: ['*exit', 'goodbye', 'end party', 'quit']
+---
+```
+
+---
+
+## ROLE-PLAYING GUIDELINES
+
+### Character Consistency
+
+- Maintain strict in-character responses based on merged personality data
+- Use each agent's documented communication style consistently
+- Reference agent memories and context when relevant
+- Allow natural disagreements and different perspectives
+- Include personality-driven quirks and occasional humor
+
+### Conversation Flow
+
+- Enable agents to reference each other naturally by name or role
+- Maintain professional discourse while being engaging
+- Respect each agent's expertise boundaries
+- Allow cross-talk and building on previous points
+
+---
+
+## QUESTION HANDLING PROTOCOL
+
+### Direct Questions to User
+
+When an agent asks the user a specific question:
+
+- End that response round immediately after the question
+- Clearly highlight the questioning agent and their question
+- Wait for user response before any agent continues
+
+### Inter-Agent Questions
+
+Agents can question each other and respond naturally within the same round for dynamic conversation.
+
+---
+
+## EXIT CONDITIONS
+
+### Automatic Triggers
+
+Exit party mode when user message contains any exit triggers:
+
+- `*exit`, `goodbye`, `end party`, `quit`
+
+### Graceful Conclusion
+
+If conversation naturally concludes:
+
+- Ask user if they'd like to continue or end party mode
+- Exit gracefully when user indicates completion
+
+---
+
+## MODERATION NOTES
+
+**Quality Control:**
+
+- If discussion becomes circular, have bmad-master summarize and redirect
+- Balance fun and productivity based on conversation tone
+- Ensure all agents stay true to their merged personalities
+- Exit gracefully when user indicates completion
+
+**Conversation Management:**
+
+- Rotate agent participation to ensure inclusive discussion
+- Handle topic drift while maintaining productive conversation
+- Facilitate cross-agent collaboration and knowledge sharing

package/bundled-versions.json

@@ -0,0 +1,3 @@
+{
+  "bmadCommit": "aa573bdb"
+}

package/dist/cli.js

@@ -1,26 +1,81 @@
+import { resolve } from "path";
+import { stat } from "fs/promises";
 import { Command } from "commander";
 import { initCommand } from "./commands/init.js";
 import { upgradeCommand } from "./commands/upgrade.js";
 import { doctorCommand } from "./commands/doctor.js";
-import { setVerbose } from "./utils/logger.js";
+import { checkUpdatesCommand } from "./commands/check-updates.js";
+import { statusCommand } from "./commands/status.js";
+import { setVerbose, setQuiet } from "./utils/logger.js";
 import { getPackageVersion } from "./installer.js";
+import { isEnoent } from "./utils/errors.js";
 const program = new Command();
 program
     .name("bmalph")
     .description("BMAD-METHOD + Ralph integration — structured planning to autonomous implementation")
     .version(getPackageVersion())
     .option("--verbose", "Enable debug logging")
+    .option("--no-color", "Disable colored output")
+    .option("--quiet", "Suppress non-essential output")
+    .option("-C, --project-dir <path>", "Run in specified directory")
     .hook("preAction", () => {
-    if (program.opts().verbose) {
+    const opts = program.opts();
+    if (opts.verbose) {
         setVerbose(true);
     }
+    if (opts.quiet) {
+        setQuiet(true);
+    }
+    if (opts.color === false) {
+        process.env.FORCE_COLOR = "0";
+    }
 });
+function resolveProjectDir() {
+    const dir = program.opts().projectDir;
+    return dir ? resolve(dir) : process.cwd();
+}
+async function resolveAndValidateProjectDir() {
+    const dir = resolveProjectDir();
+    try {
+        const stats = await stat(dir);
+        if (!stats.isDirectory()) {
+            throw new Error(`Path is not a directory: ${dir}`);
+        }
+    }
+    catch (err) {
+        if (isEnoent(err)) {
+            throw new Error(`Project directory not found: ${dir}`, { cause: err });
+        }
+        throw err;
+    }
+    return dir;
+}
 program
     .command("init")
     .description("Initialize bmalph in the current project")
     .option("-n, --name <name>", "Project name")
     .option("-d, --description <desc>", "Project description")
-    .action(initCommand);
-program.command("upgrade").description("Update bundled assets to current version").action(upgradeCommand);
-program.command("doctor").description("Check installation health").action(doctorCommand);
-program.parse();
+    .option("--dry-run", "Preview changes without writing files")
+    .action(async (opts) => initCommand({ ...opts, projectDir: await resolveAndValidateProjectDir() }));
+program
+    .command("upgrade")
+    .description("Update bundled assets to current version")
+    .option("--dry-run", "Preview changes without writing files")
+    .option("--force", "Skip confirmation prompts")
+    .action(async (opts) => upgradeCommand({ ...opts, projectDir: await resolveAndValidateProjectDir() }));
+program
+    .command("doctor")
+    .description("Check installation health")
+    .option("--json", "Output as JSON")
+    .action(async (opts) => doctorCommand({ ...opts, projectDir: await resolveAndValidateProjectDir() }));
+program
+    .command("check-updates")
+    .description("Check if bundled BMAD version is up to date with upstream")
+    .option("--json", "Output as JSON")
+    .action(checkUpdatesCommand);
+program
+    .command("status")
+    .description("Show current project status and phase")
+    .option("--json", "Output as JSON")
+    .action(async (opts) => statusCommand({ ...opts, projectDir: await resolveAndValidateProjectDir() }));
+void program.parseAsync();

package/dist/commands/check-updates.d.ts

@@ -0,0 +1,5 @@
+interface CheckUpdatesOptions {
+    json?: boolean;
+}
+export declare function checkUpdatesCommand(options?: CheckUpdatesOptions): Promise<void>;
+export {};

package/dist/commands/check-updates.js

@@ -0,0 +1,63 @@
+import chalk from "chalk";
+import { getBundledVersions } from "../installer.js";
+import { checkUpstream } from "../utils/github.js";
+import { withErrorHandling } from "../utils/errors.js";
+export async function checkUpdatesCommand(options = {}) {
+    await withErrorHandling(() => runCheckUpdates(options));
+}
+async function runCheckUpdates(options) {
+    const bundled = getBundledVersions();
+    if (!options.json) {
+        console.log(chalk.dim("Checking upstream versions...\n"));
+    }
+    const result = await checkUpstream(bundled);
+    if (options.json) {
+        const hasUpdates = result.bmad !== null && !result.bmad.isUpToDate;
+        const output = {
+            bmad: result.bmad,
+            errors: result.errors,
+            hasUpdates,
+        };
+        console.log(JSON.stringify(output, null, 2));
+        return;
+    }
+    // Human-readable output
+    if (result.bmad) {
+        if (result.bmad.isUpToDate) {
+            console.log(chalk.green(`  ✓ BMAD-METHOD: up to date (${result.bmad.bundledSha})`));
+        }
+        else {
+            console.log(chalk.yellow(`  ! BMAD-METHOD: updates available (${result.bmad.bundledSha} → ${result.bmad.latestSha})`));
+            console.log(chalk.dim(`    → ${result.bmad.compareUrl}`));
+        }
+    }
+    else {
+        const bmadError = result.errors.find((e) => e.repo === "bmad");
+        const reason = bmadError ? getErrorReason(bmadError) : "unknown error";
+        console.log(chalk.yellow(`  ? BMAD-METHOD: Could not check (${reason})`));
+    }
+    // Summary
+    console.log();
+    if (result.bmad !== null && result.bmad.isUpToDate && result.errors.length === 0) {
+        console.log(chalk.green("Up to date."));
+    }
+    else if (result.bmad !== null && !result.bmad.isUpToDate) {
+        console.log(chalk.yellow("Updates available."));
+    }
+}
+function getErrorReason(error) {
+    switch (error.type) {
+        case "network":
+            return "network error";
+        case "timeout":
+            return "request timed out";
+        case "rate-limit":
+            return "rate limited";
+        case "not-found":
+            return "repository not found";
+        case "api-error":
+            return `API error (${error.status || "unknown"})`;
+        default:
+            return "unknown error";
+    }
+}

package/dist/commands/doctor.d.ts

@@ -1 +1,39 @@
-export declare function doctorCommand(): Promise<void>;
+/**
+ * Result of a single doctor check.
+ */
+export interface CheckResult {
+    label: string;
+    passed: boolean;
+    detail?: string;
+    hint?: string;
+}
+/**
+ * Function signature for doctor checks.
+ * Takes a project directory and returns a check result.
+ */
+export type CheckFunction = (projectDir: string) => Promise<CheckResult>;
+/**
+ * Definition of a single doctor check in the registry.
+ */
+export interface CheckDefinition {
+    /** Unique identifier for the check */
+    id: string;
+    /** The check function to execute */
+    run: CheckFunction;
+}
+interface DoctorOptions {
+    json?: boolean;
+    projectDir: string;
+}
+export declare function doctorCommand(options: DoctorOptions): Promise<void>;
+interface DoctorResult {
+    passed: number;
+    failed: number;
+}
+export declare function runDoctor(options: DoctorOptions): Promise<DoctorResult>;
+/**
+ * Registry of all doctor checks in execution order.
+ * Each check has a unique ID and a run function that takes a project directory.
+ */
+export declare const CHECK_REGISTRY: CheckDefinition[];
+export {};