2025-09-28 23:17:07 -05:00
|
|
|
const path = require('node:path');
|
2025-10-05 15:52:48 -07:00
|
|
|
const fs = require('fs-extra');
|
|
|
|
|
const os = require('node:os');
|
2025-09-28 23:17:07 -05:00
|
|
|
const chalk = require('chalk');
|
2025-10-05 15:52:48 -07:00
|
|
|
const { BaseIdeSetup } = require('./_base-ide');
|
Major Enhancements:
- Installation path is now fully configurable, allowing users to specify custom installation directories during setup
- Default installation location changed to .bmad (hidden directory) for cleaner project root organization
Web Bundle Improvements:
- All web bundles (single agent and team) now include party mode support for multi-agent collaboration!
- Advanced elicitation capabilities integrated into standalone agents
- All bundles enhanced with party mode agent manifests
- Added default-party.csv files to bmm, bmgd, and cis module teams
- The default party file is what will be used with single agent bundles. teams can customize for different party configurations before web bundling through a setting in the team yaml file
- New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad)
Phase 4 Workflow Updates (In Progress):
- Initiated shift to separate phase 4 implementation artifacts from documentation
- Phase 4 implementation artifacts (stories, code review, sprint plan, context files) will move to dedicated location outside docs folder
- Installer questions and configuration added for artifact path selection
- Updated workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows to support this, but still might require some udpates
Additional Changes:
- New agent and action command header models for standardization
- Enhanced web-bundle-activation-steps fragment
- Updated web-bundler.js to support new structure
- VS Code settings updated for new .bmad directory
- Party mode instructions and workflow enhanced for better orchestration
IDE Installer Updates:
- Show version number of installer in cli
- improved Installer UX
- Gemini TOML Improved to have clear loading instructions with @ commands
- All tools agent launcher mds improved to use a central file template critical indication isntead of hardcoding in 2 different locations.
2025-11-09 17:39:05 -06:00
|
|
|
const { WorkflowCommandGenerator } = require('./shared/workflow-command-generator');
|
2025-11-09 20:24:56 -06:00
|
|
|
const { AgentCommandGenerator } = require('./shared/agent-command-generator');
|
|
|
|
|
const { getTasksFromBmad } = require('./shared/bmad-artifacts');
|
2025-09-28 23:17:07 -05:00
|
|
|
|
|
|
|
|
/**
|
Major Enhancements:
- Installation path is now fully configurable, allowing users to specify custom installation directories during setup
- Default installation location changed to .bmad (hidden directory) for cleaner project root organization
Web Bundle Improvements:
- All web bundles (single agent and team) now include party mode support for multi-agent collaboration!
- Advanced elicitation capabilities integrated into standalone agents
- All bundles enhanced with party mode agent manifests
- Added default-party.csv files to bmm, bmgd, and cis module teams
- The default party file is what will be used with single agent bundles. teams can customize for different party configurations before web bundling through a setting in the team yaml file
- New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad)
Phase 4 Workflow Updates (In Progress):
- Initiated shift to separate phase 4 implementation artifacts from documentation
- Phase 4 implementation artifacts (stories, code review, sprint plan, context files) will move to dedicated location outside docs folder
- Installer questions and configuration added for artifact path selection
- Updated workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows to support this, but still might require some udpates
Additional Changes:
- New agent and action command header models for standardization
- Enhanced web-bundle-activation-steps fragment
- Updated web-bundler.js to support new structure
- VS Code settings updated for new .bmad directory
- Party mode instructions and workflow enhanced for better orchestration
IDE Installer Updates:
- Show version number of installer in cli
- improved Installer UX
- Gemini TOML Improved to have clear loading instructions with @ commands
- All tools agent launcher mds improved to use a central file template critical indication isntead of hardcoding in 2 different locations.
2025-11-09 17:39:05 -06:00
|
|
|
* Codex setup handler (CLI mode)
|
2025-09-28 23:17:07 -05:00
|
|
|
*/
|
|
|
|
|
class CodexSetup extends BaseIdeSetup {
|
|
|
|
|
constructor() {
|
|
|
|
|
super('codex', 'Codex', true); // preferred IDE
|
|
|
|
|
}
|
|
|
|
|
|
2025-11-18 16:48:32 -08:00
|
|
|
/**
|
|
|
|
|
* Collect configuration choices before installation
|
|
|
|
|
* @param {Object} options - Configuration options
|
|
|
|
|
* @returns {Object} Collected configuration
|
|
|
|
|
*/
|
|
|
|
|
async collectConfiguration(options = {}) {
|
|
|
|
|
const inquirer = require('inquirer');
|
|
|
|
|
|
|
|
|
|
let confirmed = false;
|
|
|
|
|
let installLocation = 'global';
|
|
|
|
|
|
|
|
|
|
while (!confirmed) {
|
|
|
|
|
const { location } = await inquirer.prompt([
|
|
|
|
|
{
|
|
|
|
|
type: 'list',
|
|
|
|
|
name: 'location',
|
|
|
|
|
message: 'Where would you like to install Codex CLI prompts?',
|
|
|
|
|
choices: [
|
|
|
|
|
{
|
|
|
|
|
name: 'Global - Simple for single project ' + '(~/.codex/prompts, but references THIS project only)',
|
|
|
|
|
value: 'global',
|
|
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
name: `Project-specific - Recommended for real work (requires CODEX_HOME=<project-dir>${path.sep}.codex)`,
|
|
|
|
|
value: 'project',
|
|
|
|
|
},
|
|
|
|
|
],
|
|
|
|
|
default: 'global',
|
|
|
|
|
},
|
|
|
|
|
]);
|
|
|
|
|
|
|
|
|
|
installLocation = location;
|
|
|
|
|
|
|
|
|
|
// Display detailed instructions for the chosen option
|
|
|
|
|
console.log('');
|
|
|
|
|
if (installLocation === 'project') {
|
|
|
|
|
console.log(this.getProjectSpecificInstructions());
|
|
|
|
|
} else {
|
|
|
|
|
console.log(this.getGlobalInstructions());
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// Confirm the choice
|
|
|
|
|
const { proceed } = await inquirer.prompt([
|
|
|
|
|
{
|
|
|
|
|
type: 'confirm',
|
|
|
|
|
name: 'proceed',
|
|
|
|
|
message: 'Proceed with this installation option?',
|
|
|
|
|
default: true,
|
|
|
|
|
},
|
|
|
|
|
]);
|
|
|
|
|
|
|
|
|
|
confirmed = proceed;
|
|
|
|
|
|
|
|
|
|
if (!confirmed) {
|
|
|
|
|
console.log(chalk.yellow("\n Let's choose a different installation option.\n"));
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return { installLocation };
|
|
|
|
|
}
|
|
|
|
|
|
2025-09-28 23:17:07 -05:00
|
|
|
/**
|
|
|
|
|
* Setup Codex configuration
|
|
|
|
|
* @param {string} projectDir - Project directory
|
|
|
|
|
* @param {string} bmadDir - BMAD installation directory
|
|
|
|
|
* @param {Object} options - Setup options
|
|
|
|
|
*/
|
|
|
|
|
async setup(projectDir, bmadDir, options = {}) {
|
|
|
|
|
console.log(chalk.cyan(`Setting up ${this.name}...`));
|
|
|
|
|
|
Major Enhancements:
- Installation path is now fully configurable, allowing users to specify custom installation directories during setup
- Default installation location changed to .bmad (hidden directory) for cleaner project root organization
Web Bundle Improvements:
- All web bundles (single agent and team) now include party mode support for multi-agent collaboration!
- Advanced elicitation capabilities integrated into standalone agents
- All bundles enhanced with party mode agent manifests
- Added default-party.csv files to bmm, bmgd, and cis module teams
- The default party file is what will be used with single agent bundles. teams can customize for different party configurations before web bundling through a setting in the team yaml file
- New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad)
Phase 4 Workflow Updates (In Progress):
- Initiated shift to separate phase 4 implementation artifacts from documentation
- Phase 4 implementation artifacts (stories, code review, sprint plan, context files) will move to dedicated location outside docs folder
- Installer questions and configuration added for artifact path selection
- Updated workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows to support this, but still might require some udpates
Additional Changes:
- New agent and action command header models for standardization
- Enhanced web-bundle-activation-steps fragment
- Updated web-bundler.js to support new structure
- VS Code settings updated for new .bmad directory
- Party mode instructions and workflow enhanced for better orchestration
IDE Installer Updates:
- Show version number of installer in cli
- improved Installer UX
- Gemini TOML Improved to have clear loading instructions with @ commands
- All tools agent launcher mds improved to use a central file template critical indication isntead of hardcoding in 2 different locations.
2025-11-09 17:39:05 -06:00
|
|
|
// Always use CLI mode
|
|
|
|
|
const mode = 'cli';
|
2025-09-28 23:17:07 -05:00
|
|
|
|
2025-11-18 16:48:32 -08:00
|
|
|
// Get installation location from pre-collected config or default to global
|
|
|
|
|
const installLocation = options.preCollectedConfig?.installLocation || 'global';
|
|
|
|
|
|
2025-10-05 15:52:48 -07:00
|
|
|
const { artifacts, counts } = await this.collectClaudeArtifacts(projectDir, bmadDir, options);
|
2025-09-28 23:17:07 -05:00
|
|
|
|
2025-11-18 16:48:32 -08:00
|
|
|
const destDir = this.getCodexPromptDir(projectDir, installLocation);
|
2025-10-05 15:52:48 -07:00
|
|
|
await fs.ensureDir(destDir);
|
|
|
|
|
await this.clearOldBmadFiles(destDir);
|
|
|
|
|
const written = await this.flattenAndWriteArtifacts(artifacts, destDir);
|
2025-09-28 23:17:07 -05:00
|
|
|
|
|
|
|
|
console.log(chalk.green(`✓ ${this.name} configured:`));
|
Major Enhancements:
- Installation path is now fully configurable, allowing users to specify custom installation directories during setup
- Default installation location changed to .bmad (hidden directory) for cleaner project root organization
Web Bundle Improvements:
- All web bundles (single agent and team) now include party mode support for multi-agent collaboration!
- Advanced elicitation capabilities integrated into standalone agents
- All bundles enhanced with party mode agent manifests
- Added default-party.csv files to bmm, bmgd, and cis module teams
- The default party file is what will be used with single agent bundles. teams can customize for different party configurations before web bundling through a setting in the team yaml file
- New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad)
Phase 4 Workflow Updates (In Progress):
- Initiated shift to separate phase 4 implementation artifacts from documentation
- Phase 4 implementation artifacts (stories, code review, sprint plan, context files) will move to dedicated location outside docs folder
- Installer questions and configuration added for artifact path selection
- Updated workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows to support this, but still might require some udpates
Additional Changes:
- New agent and action command header models for standardization
- Enhanced web-bundle-activation-steps fragment
- Updated web-bundler.js to support new structure
- VS Code settings updated for new .bmad directory
- Party mode instructions and workflow enhanced for better orchestration
IDE Installer Updates:
- Show version number of installer in cli
- improved Installer UX
- Gemini TOML Improved to have clear loading instructions with @ commands
- All tools agent launcher mds improved to use a central file template critical indication isntead of hardcoding in 2 different locations.
2025-11-09 17:39:05 -06:00
|
|
|
console.log(chalk.dim(` - Mode: CLI`));
|
2025-10-05 15:52:48 -07:00
|
|
|
console.log(chalk.dim(` - ${counts.agents} agents exported`));
|
|
|
|
|
console.log(chalk.dim(` - ${counts.tasks} tasks exported`));
|
|
|
|
|
console.log(chalk.dim(` - ${counts.workflows} workflow commands exported`));
|
|
|
|
|
if (counts.workflowLaunchers > 0) {
|
|
|
|
|
console.log(chalk.dim(` - ${counts.workflowLaunchers} workflow launchers exported`));
|
|
|
|
|
}
|
|
|
|
|
console.log(chalk.dim(` - ${written} Codex prompt files written`));
|
|
|
|
|
console.log(chalk.dim(` - Destination: ${destDir}`));
|
2025-09-28 23:17:07 -05:00
|
|
|
|
|
|
|
|
return {
|
|
|
|
|
success: true,
|
|
|
|
|
mode,
|
2025-10-05 15:52:48 -07:00
|
|
|
artifacts,
|
|
|
|
|
counts,
|
|
|
|
|
destination: destDir,
|
|
|
|
|
written,
|
2025-11-18 16:48:32 -08:00
|
|
|
installLocation,
|
2025-09-28 23:17:07 -05:00
|
|
|
};
|
|
|
|
|
}
|
|
|
|
|
|
2025-10-05 20:13:11 -07:00
|
|
|
/**
|
|
|
|
|
* Detect Codex installation by checking for BMAD prompt exports
|
|
|
|
|
*/
|
2025-11-18 16:48:32 -08:00
|
|
|
async detect(projectDir) {
|
|
|
|
|
// Check both global and project-specific locations
|
|
|
|
|
const globalDir = this.getCodexPromptDir(null, 'global');
|
|
|
|
|
const projectDir_local = projectDir || process.cwd();
|
|
|
|
|
const projectSpecificDir = this.getCodexPromptDir(projectDir_local, 'project');
|
2025-10-05 20:13:11 -07:00
|
|
|
|
2025-11-18 16:48:32 -08:00
|
|
|
// Check global location
|
|
|
|
|
if (await fs.pathExists(globalDir)) {
|
|
|
|
|
const entries = await fs.readdir(globalDir);
|
|
|
|
|
if (entries.some((entry) => entry.startsWith('bmad-'))) {
|
|
|
|
|
return true;
|
|
|
|
|
}
|
2025-10-05 20:13:11 -07:00
|
|
|
}
|
|
|
|
|
|
2025-11-18 16:48:32 -08:00
|
|
|
// Check project-specific location
|
|
|
|
|
if (await fs.pathExists(projectSpecificDir)) {
|
|
|
|
|
const entries = await fs.readdir(projectSpecificDir);
|
|
|
|
|
if (entries.some((entry) => entry.startsWith('bmad-'))) {
|
|
|
|
|
return true;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return false;
|
2025-10-05 20:13:11 -07:00
|
|
|
}
|
|
|
|
|
|
2025-09-28 23:17:07 -05:00
|
|
|
/**
|
2025-10-05 15:52:48 -07:00
|
|
|
* Collect Claude-style artifacts for Codex export.
|
|
|
|
|
* Returns the normalized artifact list for further processing.
|
2025-09-28 23:17:07 -05:00
|
|
|
*/
|
2025-10-05 15:52:48 -07:00
|
|
|
async collectClaudeArtifacts(projectDir, bmadDir, options = {}) {
|
|
|
|
|
const selectedModules = options.selectedModules || [];
|
|
|
|
|
const artifacts = [];
|
2025-09-28 23:17:07 -05:00
|
|
|
|
2025-11-09 20:24:56 -06:00
|
|
|
// Generate agent launchers
|
|
|
|
|
const agentGen = new AgentCommandGenerator(this.bmadFolderName);
|
|
|
|
|
const { artifacts: agentArtifacts } = await agentGen.collectAgentArtifacts(bmadDir, selectedModules);
|
2025-10-05 15:52:48 -07:00
|
|
|
|
2025-11-09 20:24:56 -06:00
|
|
|
for (const artifact of agentArtifacts) {
|
2025-10-05 15:52:48 -07:00
|
|
|
artifacts.push({
|
|
|
|
|
type: 'agent',
|
2025-11-09 20:24:56 -06:00
|
|
|
module: artifact.module,
|
|
|
|
|
sourcePath: artifact.sourcePath,
|
|
|
|
|
relativePath: artifact.relativePath,
|
|
|
|
|
content: artifact.content,
|
2025-10-05 15:52:48 -07:00
|
|
|
});
|
2025-09-28 23:17:07 -05:00
|
|
|
}
|
|
|
|
|
|
2025-10-05 15:52:48 -07:00
|
|
|
const tasks = await getTasksFromBmad(bmadDir, selectedModules);
|
2025-09-28 23:17:07 -05:00
|
|
|
for (const task of tasks) {
|
2025-10-05 15:52:48 -07:00
|
|
|
const content = await this.readAndProcessWithProject(
|
|
|
|
|
task.path,
|
|
|
|
|
{
|
|
|
|
|
module: task.module,
|
|
|
|
|
name: task.name,
|
|
|
|
|
},
|
|
|
|
|
projectDir,
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
artifacts.push({
|
|
|
|
|
type: 'task',
|
|
|
|
|
module: task.module,
|
|
|
|
|
sourcePath: task.path,
|
|
|
|
|
relativePath: path.join(task.module, 'tasks', `${task.name}.md`),
|
|
|
|
|
content,
|
|
|
|
|
});
|
2025-09-28 23:17:07 -05:00
|
|
|
}
|
|
|
|
|
|
Major Enhancements:
- Installation path is now fully configurable, allowing users to specify custom installation directories during setup
- Default installation location changed to .bmad (hidden directory) for cleaner project root organization
Web Bundle Improvements:
- All web bundles (single agent and team) now include party mode support for multi-agent collaboration!
- Advanced elicitation capabilities integrated into standalone agents
- All bundles enhanced with party mode agent manifests
- Added default-party.csv files to bmm, bmgd, and cis module teams
- The default party file is what will be used with single agent bundles. teams can customize for different party configurations before web bundling through a setting in the team yaml file
- New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad)
Phase 4 Workflow Updates (In Progress):
- Initiated shift to separate phase 4 implementation artifacts from documentation
- Phase 4 implementation artifacts (stories, code review, sprint plan, context files) will move to dedicated location outside docs folder
- Installer questions and configuration added for artifact path selection
- Updated workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows to support this, but still might require some udpates
Additional Changes:
- New agent and action command header models for standardization
- Enhanced web-bundle-activation-steps fragment
- Updated web-bundler.js to support new structure
- VS Code settings updated for new .bmad directory
- Party mode instructions and workflow enhanced for better orchestration
IDE Installer Updates:
- Show version number of installer in cli
- improved Installer UX
- Gemini TOML Improved to have clear loading instructions with @ commands
- All tools agent launcher mds improved to use a central file template critical indication isntead of hardcoding in 2 different locations.
2025-11-09 17:39:05 -06:00
|
|
|
const workflowGenerator = new WorkflowCommandGenerator(this.bmadFolderName);
|
2025-10-05 15:52:48 -07:00
|
|
|
const { artifacts: workflowArtifacts, counts: workflowCounts } = await workflowGenerator.collectWorkflowArtifacts(bmadDir);
|
|
|
|
|
artifacts.push(...workflowArtifacts);
|
2025-09-28 23:17:07 -05:00
|
|
|
|
2025-10-05 15:52:48 -07:00
|
|
|
return {
|
|
|
|
|
artifacts,
|
|
|
|
|
counts: {
|
2025-11-09 20:24:56 -06:00
|
|
|
agents: agentArtifacts.length,
|
2025-10-05 15:52:48 -07:00
|
|
|
tasks: tasks.length,
|
|
|
|
|
workflows: workflowCounts.commands,
|
|
|
|
|
workflowLaunchers: workflowCounts.launchers,
|
|
|
|
|
},
|
|
|
|
|
};
|
|
|
|
|
}
|
2025-09-28 23:17:07 -05:00
|
|
|
|
2025-11-18 16:48:32 -08:00
|
|
|
getCodexPromptDir(projectDir = null, location = 'global') {
|
|
|
|
|
if (location === 'project' && projectDir) {
|
|
|
|
|
return path.join(projectDir, '.codex', 'prompts');
|
|
|
|
|
}
|
2025-10-05 15:52:48 -07:00
|
|
|
return path.join(os.homedir(), '.codex', 'prompts');
|
|
|
|
|
}
|
2025-09-28 23:17:07 -05:00
|
|
|
|
2025-10-05 15:52:48 -07:00
|
|
|
async flattenAndWriteArtifacts(artifacts, destDir) {
|
|
|
|
|
let written = 0;
|
2025-09-28 23:17:07 -05:00
|
|
|
|
2025-10-05 15:52:48 -07:00
|
|
|
for (const artifact of artifacts) {
|
|
|
|
|
const flattenedName = this.flattenFilename(artifact.relativePath);
|
|
|
|
|
const targetPath = path.join(destDir, flattenedName);
|
|
|
|
|
await fs.writeFile(targetPath, artifact.content);
|
|
|
|
|
written++;
|
|
|
|
|
}
|
2025-09-28 23:17:07 -05:00
|
|
|
|
2025-10-05 15:52:48 -07:00
|
|
|
return written;
|
2025-09-28 23:17:07 -05:00
|
|
|
}
|
|
|
|
|
|
2025-10-05 15:52:48 -07:00
|
|
|
async clearOldBmadFiles(destDir) {
|
|
|
|
|
if (!(await fs.pathExists(destDir))) {
|
|
|
|
|
return;
|
2025-09-28 23:17:07 -05:00
|
|
|
}
|
|
|
|
|
|
2025-10-05 15:52:48 -07:00
|
|
|
const entries = await fs.readdir(destDir);
|
2025-09-28 23:17:07 -05:00
|
|
|
|
2025-10-05 15:52:48 -07:00
|
|
|
for (const entry of entries) {
|
|
|
|
|
if (!entry.startsWith('bmad-')) {
|
|
|
|
|
continue;
|
2025-09-28 23:17:07 -05:00
|
|
|
}
|
|
|
|
|
|
2025-10-05 15:52:48 -07:00
|
|
|
const entryPath = path.join(destDir, entry);
|
|
|
|
|
const stat = await fs.stat(entryPath);
|
|
|
|
|
if (stat.isFile()) {
|
|
|
|
|
await fs.remove(entryPath);
|
|
|
|
|
} else if (stat.isDirectory()) {
|
|
|
|
|
await fs.remove(entryPath);
|
2025-09-28 23:17:07 -05:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2025-10-05 15:52:48 -07:00
|
|
|
async readAndProcessWithProject(filePath, metadata, projectDir) {
|
|
|
|
|
const content = await fs.readFile(filePath, 'utf8');
|
|
|
|
|
return super.processContent(content, metadata, projectDir);
|
|
|
|
|
}
|
|
|
|
|
|
2025-09-28 23:17:07 -05:00
|
|
|
/**
|
2025-11-18 16:48:32 -08:00
|
|
|
* Get instructions for global installation
|
|
|
|
|
* @returns {string} Instructions text
|
2025-09-28 23:17:07 -05:00
|
|
|
*/
|
2025-11-18 16:48:32 -08:00
|
|
|
getGlobalInstructions(destDir) {
|
|
|
|
|
const lines = [
|
|
|
|
|
'',
|
|
|
|
|
chalk.bold.cyan('═'.repeat(70)),
|
|
|
|
|
chalk.bold.yellow(' IMPORTANT: Codex Configuration'),
|
|
|
|
|
chalk.bold.cyan('═'.repeat(70)),
|
|
|
|
|
'',
|
|
|
|
|
chalk.white(' /prompts installed globally to your HOME DIRECTORY.'),
|
|
|
|
|
'',
|
|
|
|
|
chalk.yellow(' ⚠️ These prompts reference a specific .bmad path'),
|
|
|
|
|
chalk.dim(" To use with other projects, you'd need to copy the .bmad dir"),
|
|
|
|
|
'',
|
|
|
|
|
chalk.green(' ✓ You can now use /commands in Codex CLI'),
|
|
|
|
|
chalk.dim(' Example: /bmad-bmm-agents-pm'),
|
|
|
|
|
chalk.dim(' Type / to see all available commands'),
|
|
|
|
|
'',
|
|
|
|
|
chalk.bold.cyan('═'.repeat(70)),
|
|
|
|
|
'',
|
|
|
|
|
];
|
|
|
|
|
return lines.join('\n');
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Get instructions for project-specific installation
|
|
|
|
|
* @param {string} projectDir - Optional project directory
|
|
|
|
|
* @param {string} destDir - Optional destination directory
|
|
|
|
|
* @returns {string} Instructions text
|
|
|
|
|
*/
|
|
|
|
|
getProjectSpecificInstructions(projectDir = null, destDir = null) {
|
|
|
|
|
const isWindows = os.platform() === 'win32';
|
|
|
|
|
|
|
|
|
|
const commonLines = [
|
|
|
|
|
'',
|
|
|
|
|
chalk.bold.cyan('═'.repeat(70)),
|
|
|
|
|
chalk.bold.yellow(' Project-Specific Codex Configuration'),
|
|
|
|
|
chalk.bold.cyan('═'.repeat(70)),
|
|
|
|
|
'',
|
|
|
|
|
chalk.white(' Prompts will be installed to: ') + chalk.cyan(destDir || '<project>/.codex/prompts'),
|
|
|
|
|
'',
|
|
|
|
|
chalk.bold.yellow(' ⚠️ REQUIRED: You must set CODEX_HOME to use these prompts'),
|
|
|
|
|
'',
|
|
|
|
|
];
|
|
|
|
|
|
|
|
|
|
const windowsLines = [
|
|
|
|
|
chalk.bold(' Create a codex.cmd file in your project root:'),
|
|
|
|
|
'',
|
|
|
|
|
chalk.green(' @echo off'),
|
|
|
|
|
chalk.green(' set CODEX_HOME=%~dp0.codex'),
|
|
|
|
|
chalk.green(' codex %*'),
|
|
|
|
|
'',
|
|
|
|
|
chalk.dim(String.raw` Then run: .\codex instead of codex`),
|
|
|
|
|
chalk.dim(' (The %~dp0 gets the directory of the .cmd file)'),
|
|
|
|
|
];
|
|
|
|
|
|
|
|
|
|
const unixLines = [
|
|
|
|
|
chalk.bold(' Add this alias to your ~/.bashrc or ~/.zshrc:'),
|
|
|
|
|
'',
|
|
|
|
|
chalk.green(' alias codex=\'CODEX_HOME="$PWD/.codex" codex\''),
|
|
|
|
|
'',
|
|
|
|
|
chalk.dim(' After adding, run: source ~/.bashrc (or source ~/.zshrc)'),
|
|
|
|
|
chalk.dim(' (The $PWD uses your current working directory)'),
|
|
|
|
|
];
|
|
|
|
|
const closingLines = [
|
|
|
|
|
'',
|
|
|
|
|
chalk.dim(' This tells Codex CLI to use prompts from this project instead of ~/.codex'),
|
|
|
|
|
'',
|
|
|
|
|
chalk.bold.cyan('═'.repeat(70)),
|
|
|
|
|
'',
|
|
|
|
|
];
|
|
|
|
|
|
|
|
|
|
const lines = [...commonLines, ...(isWindows ? windowsLines : unixLines), ...closingLines];
|
|
|
|
|
|
|
|
|
|
return lines.join('\n');
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Cleanup Codex configuration
|
|
|
|
|
*/
|
|
|
|
|
async cleanup(projectDir = null) {
|
|
|
|
|
// Clean both global and project-specific locations
|
|
|
|
|
const globalDir = this.getCodexPromptDir(null, 'global');
|
|
|
|
|
await this.clearOldBmadFiles(globalDir);
|
|
|
|
|
|
|
|
|
|
if (projectDir) {
|
|
|
|
|
const projectSpecificDir = this.getCodexPromptDir(projectDir, 'project');
|
|
|
|
|
await this.clearOldBmadFiles(projectSpecificDir);
|
|
|
|
|
}
|
2025-09-28 23:17:07 -05:00
|
|
|
}
|
feat: Complete BMAD agent creation system with install tooling, references, and field guidance
## Overview
This commit represents a complete overhaul of the BMAD agent creation system, establishing clear standards for agent development, installation workflows, and persona design. The changes span documentation, tooling, reference implementations, and field-specific guidance.
## Key Components
### 1. Agent Installation Infrastructure
**New CLI Command: `agent-install`**
- Interactive agent installation with persona customization
- Supports Simple (single YAML), Expert (sidecar files), and Module agents
- Template variable processing with Handlebars-style syntax
- Automatic compilation from YAML to XML (.md) format
- Manifest tracking and IDE integration (Claude Code, Cursor, Windsurf, etc.)
- Source preservation in `_cfg/custom/agents/` for reinstallation
**Files Created:**
- `tools/cli/commands/agent-install.js` - Main CLI command
- `tools/cli/lib/agent/compiler.js` - YAML to XML compilation engine
- `tools/cli/lib/agent/installer.js` - Installation orchestration
- `tools/cli/lib/agent/template-engine.js` - Handlebars template processing
**Compiler Features:**
- Auto-injects frontmatter, activation, handlers, help/exit menu items
- Smart handler inclusion (only includes action/workflow/exec/tmpl handlers actually used)
- Proper XML escaping and formatting
- Persona name customization (e.g., "Fred the Commit Poet")
### 2. Documentation Overhaul
**Deleted Bloated/Outdated Docs (2,651 lines removed):**
- Old verbose architecture docs
- Redundant pattern files
- Outdated workflow guides
**Created Focused, Type-Specific Docs:**
- `src/modules/bmb/docs/understanding-agent-types.md` - Architecture vs capability distinction
- `src/modules/bmb/docs/simple-agent-architecture.md` - Self-contained agents
- `src/modules/bmb/docs/expert-agent-architecture.md` - Agents with sidecar files
- `src/modules/bmb/docs/module-agent-architecture.md` - Workflow-integrated agents
- `src/modules/bmb/docs/agent-compilation.md` - YAML → XML process
- `src/modules/bmb/docs/agent-menu-patterns.md` - Menu design patterns
- `src/modules/bmb/docs/index.md` - Documentation hub
**Net Result:** ~1,930 line reduction while adding MORE value through focused content
### 3. Create-Agent Workflow Enhancements
**Critical Persona Field Guidance Added to Step 4:**
Explains how the LLM interprets each persona field when the agent activates:
- **role** → "What knowledge, skills, and capabilities do I possess?"
- **identity** → "What background, experience, and context shape my responses?"
- **communication_style** → "What verbal patterns, word choice, quirks, and phrasing do I use?"
- **principles** → "What beliefs and operating philosophy drive my choices?"
**Key Insight:** `communication_style` should ONLY describe HOW the agent talks, not restate role/identity/principles. The `communication-presets.csv` provides 60 pure communication styles with NO role/identity/principles mixed in.
**Files Updated:**
- `src/modules/bmb/workflows/create-agent/instructions.md` - Added persona field interpretation guide
- `src/modules/bmb/workflows/create-agent/brainstorm-context.md` - Refined to 137 lines
- `src/modules/bmb/workflows/create-agent/communication-presets.csv` - 60 styles across 13 categories
### 4. Reference Agent Cleanup
**Removed install_config Personality Bloat:**
Understanding: Future installer will handle personality customization, so stripped all personality toggles from reference agents.
**commit-poet.agent.yaml** (Simple Agent):
- BEFORE: 36 personality combinations (3 enthusiasm × 3 depths × 4 styles) = decision fatigue
- AFTER: Single concise persona with pure communication style
- Changed from verbose conditionals to: "Poetic drama and flair with every turn of a phrase. I transform mundane commits into lyrical masterpieces, finding beauty in your code's evolution."
- Reduction: 248 lines → 153 lines (38% reduction)
**journal-keeper.agent.yaml** (Expert Agent):
- Stripped install_config, simplified communication_style
- Shows proper Expert agent structure with sidecar files
**security-engineer.agent.yaml & trend-analyst.agent.yaml** (Module Agents):
- Added header comments explaining WHY Module Agent (design intent, not just location)
- Clarified: Module agents are designed FOR ecosystem integration, not capability-limited
**Files Updated:**
- `src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml`
- `src/modules/bmb/reference/agents/expert-examples/journal-keeper/journal-keeper.agent.yaml`
- `src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml`
- `src/modules/bmb/reference/agents/module-examples/trend-analyst.agent.yaml`
### 5. BMM Agent Voice Enhancement
**Gave all 9 BMM agents distinct, memorable communication voices:**
**Mary (analyst)** - The favorite! Changed from generic "systematic and probing" to:
"Treats analysis like a treasure hunt - excited by every clue, thrilled when patterns emerge. Asks questions that spark 'aha!' moments while structuring insights with precision."
**Other Notable Voices:**
- **John (pm):** "Asks 'WHY?' relentlessly like a detective on a case. Direct and data-sharp, cuts through fluff to what actually matters."
- **Winston (architect):** "Speaks in calm, pragmatic tones, balancing 'what could be' with 'what should be.' Champions boring technology that actually works."
- **Amelia (dev):** "Ultra-succinct. Speaks in file paths and AC IDs - every statement citable. No fluff, all precision."
- **Bob (sm):** "Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity."
- **Sally (ux-designer):** "Paints pictures with words, telling user stories that make you FEEL the problem. Empathetic advocate with creative storytelling flair."
**Pattern Applied:** Moved behaviors from communication_style to principles, keeping communication_style as PURE verbal patterns.
**Files Updated:**
- `src/modules/bmm/agents/analyst.agent.yaml`
- `src/modules/bmm/agents/pm.agent.yaml`
- `src/modules/bmm/agents/architect.agent.yaml`
- `src/modules/bmm/agents/dev.agent.yaml`
- `src/modules/bmm/agents/sm.agent.yaml`
- `src/modules/bmm/agents/tea.agent.yaml`
- `src/modules/bmm/agents/tech-writer.agent.yaml`
- `src/modules/bmm/agents/ux-designer.agent.yaml`
- `src/modules/bmm/agents/frame-expert.agent.yaml`
### 6. Linting Fixes
**ESLint Compliance:**
- Replaced all `'utf-8'` with `'utf8'` (unicorn/text-encoding-identifier-case)
- Changed `variables.hasOwnProperty(varName)` to `Object.hasOwn(variables, varName)` (unicorn/prefer-object-has-own)
- Replaced `JSON.parse(JSON.stringify(...))` with `structuredClone(...)` (unicorn/prefer-structured-clone)
- Fixed empty YAML mapping values in sample files
**Files Fixed:**
- 7 JavaScript files across agent tooling (compiler, installer, commands, IDE integration)
- 1 YAML sample file
## Architecture Decisions
### Agent Types Are About Architecture, Not Capability
- **Simple:** Self-contained in single YAML (NOT limited in capability)
- **Expert:** Includes sidecar files (templates, docs, etc.)
- **Module:** Designed for BMAD ecosystem integration (workflows, cross-agent coordination)
### Persona Field Separation Critical for LLM Interpretation
The LLM needs distinct fields to understand its role:
- Mixing role/identity/principles into communication_style confuses the persona
- Pure communication styles (from communication-presets.csv) have ZERO role/identity/principles content
- Example DON'T: "Experienced analyst who uses systematic approaches..." (mixing identity + style)
- Example DO: "Systematic and probing. Structures findings hierarchically." (pure style)
### Install-Time vs Runtime Configuration
- Template variables ({{var}}) resolve at compile-time
- Runtime variables ({user_name}, {bmad_folder}) resolve when agent activates
- Future installer will handle personality customization, so agents should ship with single default persona
## Testing
- All linting passes (ESLint with max-warnings=0)
- Agent compilation tested with commit-poet, journal-keeper examples
- Install workflow validated with Simple and Expert agent types
- Manifest tracking and IDE integration verified
## Impact
This establishes BMAD as having a complete, production-ready agent creation and installation system with:
- Clear documentation for all agent types
- Automated compilation and installation
- Strong persona design guidance
- Reference implementations showing best practices
- Distinct, memorable agent voices throughout BMM module
Co-Authored-By: BMad Builder <builder@bmad.dev>
Co-Authored-By: Mary the Analyst <analyst@bmad.dev>
Co-Authored-By: Paige the Tech Writer <tech-writer@bmad.dev>
2025-11-17 22:25:15 -06:00
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Install a custom agent launcher for Codex
|
|
|
|
|
* @param {string} projectDir - Project directory (not used, Codex installs to home)
|
|
|
|
|
* @param {string} agentName - Agent name (e.g., "fred-commit-poet")
|
|
|
|
|
* @param {string} agentPath - Path to compiled agent (relative to project root)
|
|
|
|
|
* @param {Object} metadata - Agent metadata
|
|
|
|
|
* @returns {Object|null} Info about created command
|
|
|
|
|
*/
|
|
|
|
|
async installCustomAgentLauncher(projectDir, agentName, agentPath, metadata) {
|
2025-11-23 08:50:36 -06:00
|
|
|
const destDir = this.getCodexPromptDir(projectDir, 'project');
|
feat: Complete BMAD agent creation system with install tooling, references, and field guidance
## Overview
This commit represents a complete overhaul of the BMAD agent creation system, establishing clear standards for agent development, installation workflows, and persona design. The changes span documentation, tooling, reference implementations, and field-specific guidance.
## Key Components
### 1. Agent Installation Infrastructure
**New CLI Command: `agent-install`**
- Interactive agent installation with persona customization
- Supports Simple (single YAML), Expert (sidecar files), and Module agents
- Template variable processing with Handlebars-style syntax
- Automatic compilation from YAML to XML (.md) format
- Manifest tracking and IDE integration (Claude Code, Cursor, Windsurf, etc.)
- Source preservation in `_cfg/custom/agents/` for reinstallation
**Files Created:**
- `tools/cli/commands/agent-install.js` - Main CLI command
- `tools/cli/lib/agent/compiler.js` - YAML to XML compilation engine
- `tools/cli/lib/agent/installer.js` - Installation orchestration
- `tools/cli/lib/agent/template-engine.js` - Handlebars template processing
**Compiler Features:**
- Auto-injects frontmatter, activation, handlers, help/exit menu items
- Smart handler inclusion (only includes action/workflow/exec/tmpl handlers actually used)
- Proper XML escaping and formatting
- Persona name customization (e.g., "Fred the Commit Poet")
### 2. Documentation Overhaul
**Deleted Bloated/Outdated Docs (2,651 lines removed):**
- Old verbose architecture docs
- Redundant pattern files
- Outdated workflow guides
**Created Focused, Type-Specific Docs:**
- `src/modules/bmb/docs/understanding-agent-types.md` - Architecture vs capability distinction
- `src/modules/bmb/docs/simple-agent-architecture.md` - Self-contained agents
- `src/modules/bmb/docs/expert-agent-architecture.md` - Agents with sidecar files
- `src/modules/bmb/docs/module-agent-architecture.md` - Workflow-integrated agents
- `src/modules/bmb/docs/agent-compilation.md` - YAML → XML process
- `src/modules/bmb/docs/agent-menu-patterns.md` - Menu design patterns
- `src/modules/bmb/docs/index.md` - Documentation hub
**Net Result:** ~1,930 line reduction while adding MORE value through focused content
### 3. Create-Agent Workflow Enhancements
**Critical Persona Field Guidance Added to Step 4:**
Explains how the LLM interprets each persona field when the agent activates:
- **role** → "What knowledge, skills, and capabilities do I possess?"
- **identity** → "What background, experience, and context shape my responses?"
- **communication_style** → "What verbal patterns, word choice, quirks, and phrasing do I use?"
- **principles** → "What beliefs and operating philosophy drive my choices?"
**Key Insight:** `communication_style` should ONLY describe HOW the agent talks, not restate role/identity/principles. The `communication-presets.csv` provides 60 pure communication styles with NO role/identity/principles mixed in.
**Files Updated:**
- `src/modules/bmb/workflows/create-agent/instructions.md` - Added persona field interpretation guide
- `src/modules/bmb/workflows/create-agent/brainstorm-context.md` - Refined to 137 lines
- `src/modules/bmb/workflows/create-agent/communication-presets.csv` - 60 styles across 13 categories
### 4. Reference Agent Cleanup
**Removed install_config Personality Bloat:**
Understanding: Future installer will handle personality customization, so stripped all personality toggles from reference agents.
**commit-poet.agent.yaml** (Simple Agent):
- BEFORE: 36 personality combinations (3 enthusiasm × 3 depths × 4 styles) = decision fatigue
- AFTER: Single concise persona with pure communication style
- Changed from verbose conditionals to: "Poetic drama and flair with every turn of a phrase. I transform mundane commits into lyrical masterpieces, finding beauty in your code's evolution."
- Reduction: 248 lines → 153 lines (38% reduction)
**journal-keeper.agent.yaml** (Expert Agent):
- Stripped install_config, simplified communication_style
- Shows proper Expert agent structure with sidecar files
**security-engineer.agent.yaml & trend-analyst.agent.yaml** (Module Agents):
- Added header comments explaining WHY Module Agent (design intent, not just location)
- Clarified: Module agents are designed FOR ecosystem integration, not capability-limited
**Files Updated:**
- `src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml`
- `src/modules/bmb/reference/agents/expert-examples/journal-keeper/journal-keeper.agent.yaml`
- `src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml`
- `src/modules/bmb/reference/agents/module-examples/trend-analyst.agent.yaml`
### 5. BMM Agent Voice Enhancement
**Gave all 9 BMM agents distinct, memorable communication voices:**
**Mary (analyst)** - The favorite! Changed from generic "systematic and probing" to:
"Treats analysis like a treasure hunt - excited by every clue, thrilled when patterns emerge. Asks questions that spark 'aha!' moments while structuring insights with precision."
**Other Notable Voices:**
- **John (pm):** "Asks 'WHY?' relentlessly like a detective on a case. Direct and data-sharp, cuts through fluff to what actually matters."
- **Winston (architect):** "Speaks in calm, pragmatic tones, balancing 'what could be' with 'what should be.' Champions boring technology that actually works."
- **Amelia (dev):** "Ultra-succinct. Speaks in file paths and AC IDs - every statement citable. No fluff, all precision."
- **Bob (sm):** "Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity."
- **Sally (ux-designer):** "Paints pictures with words, telling user stories that make you FEEL the problem. Empathetic advocate with creative storytelling flair."
**Pattern Applied:** Moved behaviors from communication_style to principles, keeping communication_style as PURE verbal patterns.
**Files Updated:**
- `src/modules/bmm/agents/analyst.agent.yaml`
- `src/modules/bmm/agents/pm.agent.yaml`
- `src/modules/bmm/agents/architect.agent.yaml`
- `src/modules/bmm/agents/dev.agent.yaml`
- `src/modules/bmm/agents/sm.agent.yaml`
- `src/modules/bmm/agents/tea.agent.yaml`
- `src/modules/bmm/agents/tech-writer.agent.yaml`
- `src/modules/bmm/agents/ux-designer.agent.yaml`
- `src/modules/bmm/agents/frame-expert.agent.yaml`
### 6. Linting Fixes
**ESLint Compliance:**
- Replaced all `'utf-8'` with `'utf8'` (unicorn/text-encoding-identifier-case)
- Changed `variables.hasOwnProperty(varName)` to `Object.hasOwn(variables, varName)` (unicorn/prefer-object-has-own)
- Replaced `JSON.parse(JSON.stringify(...))` with `structuredClone(...)` (unicorn/prefer-structured-clone)
- Fixed empty YAML mapping values in sample files
**Files Fixed:**
- 7 JavaScript files across agent tooling (compiler, installer, commands, IDE integration)
- 1 YAML sample file
## Architecture Decisions
### Agent Types Are About Architecture, Not Capability
- **Simple:** Self-contained in single YAML (NOT limited in capability)
- **Expert:** Includes sidecar files (templates, docs, etc.)
- **Module:** Designed for BMAD ecosystem integration (workflows, cross-agent coordination)
### Persona Field Separation Critical for LLM Interpretation
The LLM needs distinct fields to understand its role:
- Mixing role/identity/principles into communication_style confuses the persona
- Pure communication styles (from communication-presets.csv) have ZERO role/identity/principles content
- Example DON'T: "Experienced analyst who uses systematic approaches..." (mixing identity + style)
- Example DO: "Systematic and probing. Structures findings hierarchically." (pure style)
### Install-Time vs Runtime Configuration
- Template variables ({{var}}) resolve at compile-time
- Runtime variables ({user_name}, {bmad_folder}) resolve when agent activates
- Future installer will handle personality customization, so agents should ship with single default persona
## Testing
- All linting passes (ESLint with max-warnings=0)
- Agent compilation tested with commit-poet, journal-keeper examples
- Install workflow validated with Simple and Expert agent types
- Manifest tracking and IDE integration verified
## Impact
This establishes BMAD as having a complete, production-ready agent creation and installation system with:
- Clear documentation for all agent types
- Automated compilation and installation
- Strong persona design guidance
- Reference implementations showing best practices
- Distinct, memorable agent voices throughout BMM module
Co-Authored-By: BMad Builder <builder@bmad.dev>
Co-Authored-By: Mary the Analyst <analyst@bmad.dev>
Co-Authored-By: Paige the Tech Writer <tech-writer@bmad.dev>
2025-11-17 22:25:15 -06:00
|
|
|
await fs.ensureDir(destDir);
|
|
|
|
|
|
|
|
|
|
const launcherContent = `---
|
|
|
|
|
name: '${agentName}'
|
|
|
|
|
description: '${agentName} agent'
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
|
|
|
|
|
|
|
|
|
|
<agent-activation CRITICAL="TRUE">
|
|
|
|
|
1. LOAD the FULL agent file from @${agentPath}
|
|
|
|
|
2. READ its entire contents - this contains the complete agent persona, menu, and instructions
|
|
|
|
|
3. FOLLOW every step in the <activation> section precisely
|
|
|
|
|
4. DISPLAY the welcome/greeting as instructed
|
|
|
|
|
5. PRESENT the numbered menu
|
|
|
|
|
6. WAIT for user input before proceeding
|
|
|
|
|
</agent-activation>
|
|
|
|
|
`;
|
|
|
|
|
|
|
|
|
|
const fileName = `bmad-custom-agents-${agentName}.md`;
|
|
|
|
|
const launcherPath = path.join(destDir, fileName);
|
|
|
|
|
await fs.writeFile(launcherPath, launcherContent, 'utf8');
|
|
|
|
|
|
|
|
|
|
return {
|
2025-11-23 08:50:36 -06:00
|
|
|
path: path.relative(projectDir, launcherPath),
|
feat: Complete BMAD agent creation system with install tooling, references, and field guidance
## Overview
This commit represents a complete overhaul of the BMAD agent creation system, establishing clear standards for agent development, installation workflows, and persona design. The changes span documentation, tooling, reference implementations, and field-specific guidance.
## Key Components
### 1. Agent Installation Infrastructure
**New CLI Command: `agent-install`**
- Interactive agent installation with persona customization
- Supports Simple (single YAML), Expert (sidecar files), and Module agents
- Template variable processing with Handlebars-style syntax
- Automatic compilation from YAML to XML (.md) format
- Manifest tracking and IDE integration (Claude Code, Cursor, Windsurf, etc.)
- Source preservation in `_cfg/custom/agents/` for reinstallation
**Files Created:**
- `tools/cli/commands/agent-install.js` - Main CLI command
- `tools/cli/lib/agent/compiler.js` - YAML to XML compilation engine
- `tools/cli/lib/agent/installer.js` - Installation orchestration
- `tools/cli/lib/agent/template-engine.js` - Handlebars template processing
**Compiler Features:**
- Auto-injects frontmatter, activation, handlers, help/exit menu items
- Smart handler inclusion (only includes action/workflow/exec/tmpl handlers actually used)
- Proper XML escaping and formatting
- Persona name customization (e.g., "Fred the Commit Poet")
### 2. Documentation Overhaul
**Deleted Bloated/Outdated Docs (2,651 lines removed):**
- Old verbose architecture docs
- Redundant pattern files
- Outdated workflow guides
**Created Focused, Type-Specific Docs:**
- `src/modules/bmb/docs/understanding-agent-types.md` - Architecture vs capability distinction
- `src/modules/bmb/docs/simple-agent-architecture.md` - Self-contained agents
- `src/modules/bmb/docs/expert-agent-architecture.md` - Agents with sidecar files
- `src/modules/bmb/docs/module-agent-architecture.md` - Workflow-integrated agents
- `src/modules/bmb/docs/agent-compilation.md` - YAML → XML process
- `src/modules/bmb/docs/agent-menu-patterns.md` - Menu design patterns
- `src/modules/bmb/docs/index.md` - Documentation hub
**Net Result:** ~1,930 line reduction while adding MORE value through focused content
### 3. Create-Agent Workflow Enhancements
**Critical Persona Field Guidance Added to Step 4:**
Explains how the LLM interprets each persona field when the agent activates:
- **role** → "What knowledge, skills, and capabilities do I possess?"
- **identity** → "What background, experience, and context shape my responses?"
- **communication_style** → "What verbal patterns, word choice, quirks, and phrasing do I use?"
- **principles** → "What beliefs and operating philosophy drive my choices?"
**Key Insight:** `communication_style` should ONLY describe HOW the agent talks, not restate role/identity/principles. The `communication-presets.csv` provides 60 pure communication styles with NO role/identity/principles mixed in.
**Files Updated:**
- `src/modules/bmb/workflows/create-agent/instructions.md` - Added persona field interpretation guide
- `src/modules/bmb/workflows/create-agent/brainstorm-context.md` - Refined to 137 lines
- `src/modules/bmb/workflows/create-agent/communication-presets.csv` - 60 styles across 13 categories
### 4. Reference Agent Cleanup
**Removed install_config Personality Bloat:**
Understanding: Future installer will handle personality customization, so stripped all personality toggles from reference agents.
**commit-poet.agent.yaml** (Simple Agent):
- BEFORE: 36 personality combinations (3 enthusiasm × 3 depths × 4 styles) = decision fatigue
- AFTER: Single concise persona with pure communication style
- Changed from verbose conditionals to: "Poetic drama and flair with every turn of a phrase. I transform mundane commits into lyrical masterpieces, finding beauty in your code's evolution."
- Reduction: 248 lines → 153 lines (38% reduction)
**journal-keeper.agent.yaml** (Expert Agent):
- Stripped install_config, simplified communication_style
- Shows proper Expert agent structure with sidecar files
**security-engineer.agent.yaml & trend-analyst.agent.yaml** (Module Agents):
- Added header comments explaining WHY Module Agent (design intent, not just location)
- Clarified: Module agents are designed FOR ecosystem integration, not capability-limited
**Files Updated:**
- `src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml`
- `src/modules/bmb/reference/agents/expert-examples/journal-keeper/journal-keeper.agent.yaml`
- `src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml`
- `src/modules/bmb/reference/agents/module-examples/trend-analyst.agent.yaml`
### 5. BMM Agent Voice Enhancement
**Gave all 9 BMM agents distinct, memorable communication voices:**
**Mary (analyst)** - The favorite! Changed from generic "systematic and probing" to:
"Treats analysis like a treasure hunt - excited by every clue, thrilled when patterns emerge. Asks questions that spark 'aha!' moments while structuring insights with precision."
**Other Notable Voices:**
- **John (pm):** "Asks 'WHY?' relentlessly like a detective on a case. Direct and data-sharp, cuts through fluff to what actually matters."
- **Winston (architect):** "Speaks in calm, pragmatic tones, balancing 'what could be' with 'what should be.' Champions boring technology that actually works."
- **Amelia (dev):** "Ultra-succinct. Speaks in file paths and AC IDs - every statement citable. No fluff, all precision."
- **Bob (sm):** "Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity."
- **Sally (ux-designer):** "Paints pictures with words, telling user stories that make you FEEL the problem. Empathetic advocate with creative storytelling flair."
**Pattern Applied:** Moved behaviors from communication_style to principles, keeping communication_style as PURE verbal patterns.
**Files Updated:**
- `src/modules/bmm/agents/analyst.agent.yaml`
- `src/modules/bmm/agents/pm.agent.yaml`
- `src/modules/bmm/agents/architect.agent.yaml`
- `src/modules/bmm/agents/dev.agent.yaml`
- `src/modules/bmm/agents/sm.agent.yaml`
- `src/modules/bmm/agents/tea.agent.yaml`
- `src/modules/bmm/agents/tech-writer.agent.yaml`
- `src/modules/bmm/agents/ux-designer.agent.yaml`
- `src/modules/bmm/agents/frame-expert.agent.yaml`
### 6. Linting Fixes
**ESLint Compliance:**
- Replaced all `'utf-8'` with `'utf8'` (unicorn/text-encoding-identifier-case)
- Changed `variables.hasOwnProperty(varName)` to `Object.hasOwn(variables, varName)` (unicorn/prefer-object-has-own)
- Replaced `JSON.parse(JSON.stringify(...))` with `structuredClone(...)` (unicorn/prefer-structured-clone)
- Fixed empty YAML mapping values in sample files
**Files Fixed:**
- 7 JavaScript files across agent tooling (compiler, installer, commands, IDE integration)
- 1 YAML sample file
## Architecture Decisions
### Agent Types Are About Architecture, Not Capability
- **Simple:** Self-contained in single YAML (NOT limited in capability)
- **Expert:** Includes sidecar files (templates, docs, etc.)
- **Module:** Designed for BMAD ecosystem integration (workflows, cross-agent coordination)
### Persona Field Separation Critical for LLM Interpretation
The LLM needs distinct fields to understand its role:
- Mixing role/identity/principles into communication_style confuses the persona
- Pure communication styles (from communication-presets.csv) have ZERO role/identity/principles content
- Example DON'T: "Experienced analyst who uses systematic approaches..." (mixing identity + style)
- Example DO: "Systematic and probing. Structures findings hierarchically." (pure style)
### Install-Time vs Runtime Configuration
- Template variables ({{var}}) resolve at compile-time
- Runtime variables ({user_name}, {bmad_folder}) resolve when agent activates
- Future installer will handle personality customization, so agents should ship with single default persona
## Testing
- All linting passes (ESLint with max-warnings=0)
- Agent compilation tested with commit-poet, journal-keeper examples
- Install workflow validated with Simple and Expert agent types
- Manifest tracking and IDE integration verified
## Impact
This establishes BMAD as having a complete, production-ready agent creation and installation system with:
- Clear documentation for all agent types
- Automated compilation and installation
- Strong persona design guidance
- Reference implementations showing best practices
- Distinct, memorable agent voices throughout BMM module
Co-Authored-By: BMad Builder <builder@bmad.dev>
Co-Authored-By: Mary the Analyst <analyst@bmad.dev>
Co-Authored-By: Paige the Tech Writer <tech-writer@bmad.dev>
2025-11-17 22:25:15 -06:00
|
|
|
command: `/${fileName.replace('.md', '')}`,
|
|
|
|
|
};
|
|
|
|
|
}
|
2025-09-28 23:17:07 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
module.exports = { CodexSetup };
|