2025-09-28 23:17:07 -05:00
|
|
|
const path = require('node:path');
|
|
|
|
|
const { BaseIdeSetup } = require('./_base-ide');
|
|
|
|
|
const chalk = require('chalk');
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* iFlow CLI setup handler
|
|
|
|
|
* Creates commands in .iflow/commands/ directory structure
|
|
|
|
|
*/
|
|
|
|
|
class IFlowSetup extends BaseIdeSetup {
|
|
|
|
|
constructor() {
|
|
|
|
|
super('iflow', 'iFlow CLI');
|
|
|
|
|
this.configDir = '.iflow';
|
|
|
|
|
this.commandsDir = 'commands';
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Setup iFlow CLI 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}...`));
|
|
|
|
|
|
|
|
|
|
// Create .iflow/commands/bmad directory structure
|
|
|
|
|
const iflowDir = path.join(projectDir, this.configDir);
|
|
|
|
|
const commandsDir = path.join(iflowDir, this.commandsDir, 'bmad');
|
|
|
|
|
const agentsDir = path.join(commandsDir, 'agents');
|
|
|
|
|
const tasksDir = path.join(commandsDir, 'tasks');
|
|
|
|
|
|
|
|
|
|
await this.ensureDir(agentsDir);
|
|
|
|
|
await this.ensureDir(tasksDir);
|
|
|
|
|
|
|
|
|
|
// Get agents and tasks
|
|
|
|
|
const agents = await this.getAgents(bmadDir);
|
|
|
|
|
const tasks = await this.getTasks(bmadDir);
|
|
|
|
|
|
|
|
|
|
// Setup agents as commands
|
|
|
|
|
let agentCount = 0;
|
|
|
|
|
for (const agent of agents) {
|
|
|
|
|
const content = await this.readFile(agent.path);
|
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 commandContent = await this.createAgentCommand(agent, content);
|
2025-09-28 23:17:07 -05:00
|
|
|
|
|
|
|
|
const targetPath = path.join(agentsDir, `${agent.module}-${agent.name}.md`);
|
|
|
|
|
await this.writeFile(targetPath, commandContent);
|
|
|
|
|
agentCount++;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// Setup tasks as commands
|
|
|
|
|
let taskCount = 0;
|
|
|
|
|
for (const task of tasks) {
|
|
|
|
|
const content = await this.readFile(task.path);
|
|
|
|
|
const commandContent = this.createTaskCommand(task, content);
|
|
|
|
|
|
|
|
|
|
const targetPath = path.join(tasksDir, `${task.module}-${task.name}.md`);
|
|
|
|
|
await this.writeFile(targetPath, commandContent);
|
|
|
|
|
taskCount++;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
console.log(chalk.green(`✓ ${this.name} configured:`));
|
|
|
|
|
console.log(chalk.dim(` - ${agentCount} agent commands created`));
|
|
|
|
|
console.log(chalk.dim(` - ${taskCount} task commands created`));
|
|
|
|
|
console.log(chalk.dim(` - Commands directory: ${path.relative(projectDir, commandsDir)}`));
|
|
|
|
|
|
|
|
|
|
return {
|
|
|
|
|
success: true,
|
|
|
|
|
agents: agentCount,
|
|
|
|
|
tasks: taskCount,
|
|
|
|
|
};
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Create agent command content
|
|
|
|
|
*/
|
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
|
|
|
async createAgentCommand(agent, content) {
|
2025-09-28 23:17:07 -05:00
|
|
|
// Extract metadata
|
|
|
|
|
const titleMatch = content.match(/title="([^"]+)"/);
|
|
|
|
|
const title = titleMatch ? titleMatch[1] : this.formatTitle(agent.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
|
|
|
// Get the activation header from central template
|
|
|
|
|
const activationHeader = await this.getAgentCommandHeader();
|
|
|
|
|
|
2025-09-28 23:17:07 -05:00
|
|
|
let commandContent = `# /${agent.name} Command
|
|
|
|
|
|
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
|
|
|
${activationHeader}
|
2025-09-28 23:17:07 -05:00
|
|
|
|
|
|
|
|
## ${title} Agent
|
|
|
|
|
|
|
|
|
|
${content}
|
|
|
|
|
|
|
|
|
|
## Usage
|
|
|
|
|
|
|
|
|
|
This command activates the ${title} agent from the BMAD ${agent.module.toUpperCase()} module.
|
|
|
|
|
|
|
|
|
|
`;
|
|
|
|
|
|
|
|
|
|
return commandContent;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Create task command content
|
|
|
|
|
*/
|
|
|
|
|
createTaskCommand(task, content) {
|
|
|
|
|
// Extract task name
|
|
|
|
|
const nameMatch = content.match(/<name>([^<]+)<\/name>/);
|
|
|
|
|
const taskName = nameMatch ? nameMatch[1] : this.formatTitle(task.name);
|
|
|
|
|
|
|
|
|
|
let commandContent = `# /task-${task.name} Command
|
|
|
|
|
|
|
|
|
|
When this command is used, execute the following task:
|
|
|
|
|
|
|
|
|
|
## ${taskName} Task
|
|
|
|
|
|
|
|
|
|
${content}
|
|
|
|
|
|
|
|
|
|
## Usage
|
|
|
|
|
|
|
|
|
|
This command executes the ${taskName} task from the BMAD ${task.module.toUpperCase()} module.
|
|
|
|
|
|
|
|
|
|
## Module
|
|
|
|
|
|
|
|
|
|
Part of the BMAD ${task.module.toUpperCase()} module.
|
|
|
|
|
`;
|
|
|
|
|
|
|
|
|
|
return commandContent;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Cleanup iFlow configuration
|
|
|
|
|
*/
|
|
|
|
|
async cleanup(projectDir) {
|
|
|
|
|
const fs = require('fs-extra');
|
|
|
|
|
const bmadCommandsDir = path.join(projectDir, this.configDir, this.commandsDir, 'bmad');
|
|
|
|
|
|
|
|
|
|
if (await fs.pathExists(bmadCommandsDir)) {
|
|
|
|
|
await fs.remove(bmadCommandsDir);
|
|
|
|
|
console.log(chalk.dim(`Removed BMAD commands from iFlow CLI`));
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
module.exports = { IFlowSetup };
|