script improved to not require node packages installed

BETA-V3/build-agent-cfg.js

@@ -0,0 +1,10 @@
+// BETA-V3/build-agent-cfg.js
+// This file contains the configuration for the build-bmad-orchestrator.js script.
+// Paths are relative to the BETA-V3 directory (where this file and the script reside).
+
+module.exports = {
+  orchestrator_agent_prompt: "./bmad-agent/orchestrator-agent.md",
+  agent_cfg: "./samples/orchestrator-agent-cfg.gemini.yaml", // Note: This referenced file is still YAML
+  asset_root: "./bmad-agent/",
+  build_dir: "./bmad-agent/build/",
+};

BETA-V3/build-agent-cfg.yml

@@ -1,4 +0,0 @@
-orchestrator_agent_prompt: "./samples/orchestrator-agent.gemini.md"
-agent_cfg: "./samples/orchestrator-agent-cfg.gemini.yaml"
-asset_root: "./bmad-agent/"
-build_dir: "./bmad-agent/build/"

BETA-V3/build-bmad-orchestrator.js

@@ -1,10 +1,28 @@
 #!/usr/bin/env node
-const fs = require("fs");
+const fs = require("fs"); // fs is still needed for other operations
 const path = require("path");
-const yaml = require("js-yaml");
+// const yaml = require("js-yaml"); // YAML is no longer needed for the main config
 
 // --- Configuration ---
-const CONFIG_FILE_PATH = path.resolve(__dirname, "build-agent-cfg.yml");
+// const CONFIG_FILE_PATH = path.resolve(__dirname, "build-agent-cfg.yml"); // Old way
+const configFilePath = "./build-agent-cfg.js"; // Path relative to this script (__dirname)
+let config;
+try {
+  config = require(configFilePath);
+} catch (error) {
+  console.error(
+    `Error loading configuration file '${configFilePath}': ${error.message}`
+  );
+  if (error.code === "MODULE_NOT_FOUND") {
+    console.error(
+      `Ensure '${path.resolve(
+        __dirname,
+        configFilePath
+      )}' exists and is a valid JavaScript module.`
+    );
+  }
+  process.exit(1);
+}
 
 // --- Helper Functions ---
 function getBaseFilename(filePath) {
@@ -24,24 +42,11 @@ function ensureDirectoryExists(dirPath) {
 
 // --- Main Script Logic ---
 async function main() {
-  // 1. Load Configuration
+  // 1. Load Configuration - ALREADY DONE ABOVE
-  console.log(`Loading configuration from: ${CONFIG_FILE_PATH}`);
+  console.log(
-  let config;
+    `Loading configuration from: ${path.resolve(__dirname, configFilePath)}`
-  try {
+  );
-    if (!fs.existsSync(CONFIG_FILE_PATH)) {
+  // No need to check fs.existsSync(CONFIG_FILE_PATH) or read/parse, require() handles it.
-      console.error(
-        `Error: Configuration file not found at '${CONFIG_FILE_PATH}'.`
-      );
-      process.exit(1);
-    }
-    const configFileContents = fs.readFileSync(CONFIG_FILE_PATH, "utf8");
-    config = yaml.load(configFileContents);
-  } catch (error) {
-    console.error(
-      `Error loading or parsing configuration file: ${error.message}`
-    );
-    process.exit(1);
-  }
 
   if (
     !config ||
@@ -61,7 +66,7 @@ async function main() {
   const assetFolderRootInput = config.asset_root;
   let assetFolderRoot;
   try {
-    assetFolderRoot = path.resolve(workspaceRoot, assetFolderRootInput);
+    assetFolderRoot = path.resolve(__dirname, assetFolderRootInput);
     if (
       !fs.existsSync(assetFolderRoot) ||
       !fs.statSync(assetFolderRoot).isDirectory()
@@ -82,7 +87,7 @@ async function main() {
   const buildDirInput = config.build_dir;
   let buildDir;
   try {
-    buildDir = path.resolve(workspaceRoot, buildDirInput);
+    buildDir = path.resolve(__dirname, buildDirInput);
   } catch (error) {
     console.error(
       `Error: Could not resolve build directory '${buildDirInput}'. ${error.message}`
@@ -99,7 +104,7 @@ async function main() {
   let orchestratorPromptPath;
   try {
     orchestratorPromptPath = path.resolve(
-      workspaceRoot,
+      __dirname,
       orchestratorPromptPathInput
     );
     if (
@@ -262,7 +267,10 @@ Processing '${subdirName}' directory into '${targetFile}'`);
   console.log(`
 Script finished. Output files are in ${buildDir}`);
   console.log(
-    `To run this script: node ${path.relative(workspaceRoot, __filename)}`
+    `To run this script: node ${path.relative(
+      path.resolve(__dirname, "../.."),
+      __filename
+    )}`
   );
 }
 

BETA-V3/instruction.md

@@ -4,19 +4,105 @@
 - [IDE Agent Setup](#ide-agent-setup)
 - [Tasks Setup and Usage](#tasks)
 
-## Setting up Web-Mode Agents in Gemini Gem or ChatGPT Custom GPT
+## Setting up Agent Orchestrator
 
-To set up web-mode agents, please refer to the table below. It outlines the agent name, the source file for its description, and any checklist or template files that need to be attached.
+The Agent Orchestrator in V3 utilizes a build script to package various agent assets (personas, tasks, templates, etc.) into a structured format, primarily for use with web-based orchestrator agents that can leverage large context windows. This process involves consolidating files from specified source directories into bundled text files and preparing a main agent prompt.
 
-| Agent Name         | Description File Path                           | Attachment Files (Checklists/Templates)                                                                                                                                        |
+### Overview
-| ------------------ | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+
-| 0-bmad             | `BETA-V3/web-agent-modes/0-bmad.md`             |                                                                                                                                                                                |
+The build process is managed by the `BETA-V3/build-bmad-orchestrator.js` Node.js script. This script reads its configuration from `BETA-V3/build-agent-cfg.js`, processes files from an asset directory, and outputs the bundled assets into a designated build directory.
-| 1-analyst          | `BETA-V3/web-agent-modes/1-analyst.md`          | `BETA-V3/templates/project-brief-tmpl.txt`                                                                                                                                     |
+
-| 2-pm               | `BETA-V3/web-agent-modes/2-pm.md`               | `BETA-V3/checklists/pm-checklist.txt`, `BETA-V3/templates/prd-tmpl.txt`                                                                                                        |
+### Prerequisites
-| 3-architect        | `BETA-V3/web-agent-modes/3-architect.md`        | `BETA-V3/templates/architecture-tmpl.txt`, `BETA-V3/checklists/architect-checklist.txt`                                                                                        |
+
-| 4-design-architect | `BETA-V3/web-agent-modes/4-design-architect.md` | `BETA-V3/templates/front-end-architecture-tmpl.txt`, `BETA-V3/templates/front-end-spec-tmpl.txt`, `BETA-V3/checklists/frontend-architecture-checklist.txt`                     |
+- **Node.js**: Ensure you have Node.js installed to run the build script.
-| 5-posm             | `BETA-V3/web-agent-modes/5-posm.md`             | `BETA-V3/checklists/po-master-checklist.txt`, `BETA-V3/templates/story-tmpl.txt`, `BETA-V3/checklists/story-draft-checklist.txt`, `BETA-V3/checklists/story-dod-checklist.txt` |
+
-| 6-rte              | `BETA-V3/web-agent-modes/6-rte.md`              | `BETA-V3/checklists/rte-checklist.md`                                                                                                                                          |
+### Configuration (`BETA-V3/build-agent-cfg.js`)
+
+The build process is configured via `build-agent-cfg.js`. Key parameters include:
+
+- `orchestrator_agent_prompt`: Specifies the path to the main prompt file for the orchestrator agent. This file will be copied to `agent-prompt.txt` in the build directory.
+  - Example: `./bmad-agent/orchestrator-agent.md` (Path relative to `BETA-V3/`)
+- `asset_root`: Defines the root directory where your agent assets are stored. The script will look for subdirectories within this path.
+  - Example: `./bmad-agent/` (Path relative to `BETA-V3/`, meaning it will look for folders like `personas`, `tasks` inside `BETA-V3/bmad-agent/`)
+- `build_dir`: Specifies the directory where the bundled output files and the `agent-prompt.txt` will be created.
+  - Example: `./bmad-agent/build/` (Path relative to `BETA-V3/`, output will be in `BETA-V3/bmad-agent/build/`)
+- `agent_cfg`: Specifies the path to the YAML file that defines the agents the Orchestrator can embody.
+  - Example: `./samples/orchestrator-agent-cfg.gemini.yaml` (Path relative to `BETA-V3/`)
+
+Paths in the configuration file (`build-agent-cfg.js`) are relative to the `BETA-V3` directory (where `build-agent-cfg.js` and the build script `build-bmad-orchestrator.js` are located).
+
+### Asset Directory Structure
+
+The script expects a specific structure within the `asset_root` directory (e.g., `BETA-V3/bmad-agent/`):
+
+1.  **Subdirectories**: Create subdirectories directly under `asset_root` for each category of assets. Based on the `BMAD-METHOD/BETA-V3/bmad-agent` structure, these would be:
+    - `checklists/`
+    - `data/`
+    - `personas/`
+    - `tasks/`
+    - `templates/`
+2.  **Asset Files**: Place your individual asset files (e.g., `.md`, `.txt`) within these subdirectories.
+    - For example, persona definition files would go into `asset_root/personas/`, task files into `asset_root/tasks/`, etc.
+3.  **Filename Uniqueness**: Within each subdirectory, ensure that all files have unique base names (i.e., the filename without its final extension). For example, having `my-persona.md` and `my-persona.txt` in the _same_ subdirectory (e.g., `personas/`) will cause the script to halt with an error. However, `my-persona.md` and `another-persona.md` is fine.
+
+### Running the Build Script
+
+1.  **Navigate to the script's directory (optional but recommended for clarity)**:
+    ```bash
+    cd BETA-V3
+    ```
+2.  **Execute the script**:
+    ```bash
+    node build-bmad-orchestrator.js
+    ```
+    If you are in the workspace root, you would run:
+    ```bash
+    node BETA-V3/build-bmad-orchestrator.js
+    ```
+
+The script will log its progress, including discovered source directories, any issues found (like duplicate base filenames), and the output files being generated.
+
+### Output
+
+After running the script, the `build_dir` (e.g., `BETA-V3/bmad-agent/build/`) will contain:
+
+1.  **Bundled Asset Files**: For each subdirectory processed in `asset_root`, a corresponding `.txt` file will be created in `build_dir`. Each file concatenates the content of all files from its source subdirectory.
+    - Example: Files from `asset_root/personas/` will be bundled into `build_dir/personas.txt`.
+    - Each original file's content within the bundle is demarcated by `==================== START: [base_filename] ====================` and `==================== END: [base_filename] ====================`.
+2.  **`agent-prompt.txt`**: This file is a copy of the prompt specified by `orchestrator_agent_prompt` in the configuration.
+
+These bundled files and the agent prompt are then ready to be used by the Agent Orchestrator.
+
+### Orchestrator Agent Configuration (`BETA-V3/samples/orchestrator-agent-cfg.gemini.yaml`)
+
+While the `build-bmad-orchestrator.js` script handles the packaging of assets, the core behavior, agent definitions, and personality of the Orchestrator and its managed agents are defined in a separate YAML configuration file, typically `BETA-V3/samples/orchestrator-agent-cfg.gemini.yaml`. This file is **central** to the Orchestrator's power and flexibility.
+
+**Key Features and Configurability:**
+
+- **Agent Definitions**: This YAML file lists all the specialized agents the Orchestrator can embody. Each agent is defined with attributes such as:
+  - `title`: A user-friendly title (e.g., "Product Manager").
+  - `name`: A specific name for the agent (e.g., "John").
+  - `classification_label`: A label used for internal identification (e.g., "PM").
+  - `description`: A brief of the agent's purpose.
+  - `persona_core`: A reference to a specific section within a bundled asset file (e.g., `personas#pm` refers to the `pm` section in `personas.txt`). This defines the agent's core personality, instructions, and operational guidelines.
+  - `checklists`, `templates`, `data_sources`: Lists of references to specific sections in bundled asset files (e.g., `checklists#pm-checklist`) that provide the agent with its necessary knowledge base and tools.
+  - `operating_modes`: Defines different modes or phases the agent can operate in (e.g., "Outcome Focused PRD Generation", "Deep Research").
+  - `interaction_modes`: Specifies how the agent interacts (e.g., "Interactive", "YOLO" - which implies attempting to complete tasks autonomously).
+  - `available_tasks`: Links to specific task definitions (e.g., `tasks#story-draft-task`), imbuing the agent with the ability to perform predefined complex operations.
+- **Custom Instructions**: Each agent definition can include `custom_instructions`. This is a powerful feature allowing you to inject specific personality traits, quirks, or overriding behaviors directly into an agent. For example, an agent might be configured with `custom_instructions: "You are a bit of a know-it-all, and like to verbalize and emote as if you were a physical person."`
+  - As detailed in the `BETA-V3/bmad-agent/orchestrator-agent.md` (the main prompt for the orchestrator), these `custom_instructions` are layered on top of the agent's `persona_core` and take precedence if there are conflicts. This provides a fine-grained control over individual agent personalities without altering the base persona files.
+
+**How it Works (Conceptual Flow from `orchestrator-agent.md`):**
+
+1.  The Orchestrator (initially BMad) loads and parses `orchestrator-agent-cfg.gemini.yaml`.
+2.  When a user request matches an agent's `title`, `name`, `description`, or `classification_label`, the Orchestrator identifies the target agent.
+3.  It then loads the agent's `persona_core` and any associated `templates`, `checklists`, `data_sources`, and `tasks` by:
+    - Identifying the correct bundled `.txt` file (e.g., `personas.txt` for `personas#pm`).
+    - Extracting the specific content block (e.g., the `pm` section from `personas.txt`).
+4.  The `custom_instructions` from the YAML are applied, potentially modifying the agent's behavior.
+5.  The Orchestrator then _becomes_ that agent, adopting its complete persona, knowledge, and operational parameters defined in the YAML and the loaded asset sections.
+
+This system makes the Agent Orchestrator highly adaptable. You can easily define new agents, modify existing ones, tweak personalities with `custom_instructions` (in `orchestrator-agent-cfg.gemini.yaml`), or change their knowledge base, main prompt, and asset paths (in `build-agent-cfg.js` and the corresponding asset files), then re-running the build script if asset content was changed.
 
 ## IDE Agent Setup