Compare commits

...

4 Commits

Author SHA1 Message Date
Brian Madison a6f089cfd2 feat: add empty IDE selection warning and promote Antigravity to recommended
- Add persistent warning loop when no tools selected in installer
- Users must press spacebar to select, not just highlight
- Red warning explains the issue and offers to go back
- Only way to proceed without tools is explicit "No" confirmation
- Promote Google Antigravity to preferred/recommended IDE section
2025-11-19 22:12:45 -06:00
Alex Verkhovsky 09533e4abb
Chore/update gitignore (#945)
* feat: Add Google Antigravity IDE installer

Implements installer for Google Antigravity IDE with flattened slash command
naming to match Antigravity's namespace requirements.

Key features:
- Flattened file naming (bmad-module-agents-name.md) for proper slash commands
- Subagent installation support (project-level or user-level)
- Module-specific injection configuration
- Agent, workflow, task, and tool command generation

Implementation:
- Added AntigravitySetup class extending BaseIdeSetup
- Extracted flattenFilename() to BaseIdeSetup for reuse across IDE handlers
- Uses .agent/workflows directory structure
- Supports both interactive and non-interactive configuration

Fixes:
- Proper namespace isolation: /bmad-module-agents-dev instead of /dev
- Prevents conflicts between modules with same agent names

Note: This installer shares 95% of its code with claude-code.js.
Future refactoring could extract common patterns to IdeWithSlashCommandsSetup
base class (see design documents for details).

* chore: update gitignore for antigravity installer

---------

Co-authored-by: Brian <bmadcode@gmail.com>
2025-11-19 20:41:08 -06:00
Dicky Moore d7f045b11e
Align UX design workflow references (#935)
Co-authored-by: Brian <bmadcode@gmail.com>
2025-11-19 20:40:07 -06:00
Alex Verkhovsky e8e13a9aa3
feat: default installer username to system user (#939)
good idea here, thank you!
2025-11-19 20:36:54 -06:00
13 changed files with 93 additions and 31 deletions

2
.gitignore vendored
View File

@ -67,3 +67,5 @@ z*/
.bmad
.claude
.agent
.codex

View File

@ -321,7 +321,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
**Workflows:**
- `workflow-status` - Check what to do next
- `create-design` - Conduct design thinking workshop to define UX specification with:
- `create-ux-design` - Conduct design thinking workshop to define UX specification with:
- Visual exploration and generation
- Collaborative decision-making
- AI-assisted design tools (v0, Lovable)
@ -944,7 +944,7 @@ Quick reference for agent selection:
| ----------------------- | ---- | ------------------ | --------------------------------------------- | ------------------------------------- |
| **Analyst** | 📊 | 1 (Analysis) | brainstorm, brief, research, document-project | Discovery, requirements, brownfield |
| **PM** | 📋 | 2 (Planning) | prd, tech-spec, epics-stories | Planning, requirements docs |
| **UX Designer** | 🎨 | 2 (Planning) | create-design, validate-design | UX-heavy projects, design |
| **UX Designer** | 🎨 | 2 (Planning) | create-ux-design, validate-design | UX-heavy projects, design |
| **Architect** | 🏗️ | 3 (Solutioning) | architecture, implementation-readiness | Technical design, architecture |
| **SM** | 🏃 | 4 (Implementation) | sprint-planning, create-story, story-context | Story management, sprint coordination |
| **DEV** | 💻 | 4 (Implementation) | develop-story, code-review, story-done | Implementation, coding |

View File

@ -240,7 +240,7 @@ Continuous deployment to production
**UX Designer Workflow:**
```bash
bmad ux *create-design
bmad ux *create-ux-design
```
**BMad produces:**

View File

@ -295,7 +295,7 @@ These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks*
| Workflow Stage | Test Architect | Dev / Team | Outputs |
| -------------------------- | ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
| **Phase 1**: Discovery | - | Analyst `*research`, `*product-brief` | Domain research, compliance analysis, product brief |
| **Phase 2**: Planning | Run `*nfr-assess` | PM `*prd` (creates PRD with FRs/NFRs), UX `*create-design` | Enterprise PRD with FRs/NFRs, UX design, NFR documentation |
| **Phase 2**: Planning | Run `*nfr-assess` | PM `*prd` (creates PRD with FRs/NFRs), UX `*create-ux-design` | Enterprise PRD with FRs/NFRs, UX design, NFR documentation |
| **Phase 3**: Solutioning | Run `*framework`, `*ci` AFTER architecture and epic creation | Architect `*architecture`, `*create-epics-and-stories`, `*implementation-readiness` | Architecture, epics/stories, test framework, CI pipeline |
| **Phase 4**: Sprint Start | - | SM `*sprint-planning` | Sprint plan with all epics |
| **Phase 4**: Epic Planning | Run `*test-design` for THIS epic 🔄 (compliance focus) | Review epic scope and compliance requirements | `test-design-epic-N.md` with security/performance/compliance focus |

View File

@ -26,12 +26,12 @@
<check if="status file found">
<action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
<action>Parse workflow_status section</action>
<action>Check status of "create-design" workflow</action>
<action>Check status of "create-ux-design" workflow</action>
<action>Get project_level from YAML metadata</action>
<action>Find first non-completed workflow (next expected workflow)</action>
<check if="create-design status is file path (already completed)">
<output>⚠️ UX Design already completed: {{create-design status}}</output>
<check if="create-ux-design status is file path (already completed)">
<output>⚠️ UX Design already completed: {{create-ux-design status}}</output>
<ask>Re-running will overwrite the existing UX design. Continue? (y/n)</ask>
<check if="n">
<output>Exiting. Use workflow-status to see your next step.</output>
@ -39,7 +39,7 @@
</check>
</check>
<check if="create-design is not the next expected workflow">
<check if="create-ux-design is not the next expected workflow">
<output>⚠️ Next expected workflow: {{next_workflow}}. UX Design is out of sequence.</output>
<ask>Continue with UX Design anyway? (y/n)</ask>
<check if="n">
@ -1139,9 +1139,9 @@ Based on your deployment intent: {{recommendation}}
<check if="standalone_mode != true">
<action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
<action>Find workflow_status key "create-design"</action>
<action>Find workflow_status key "create-ux-design"</action>
<critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
<action>Update workflow_status["create-design"] = "{default_output_file}"</action>
<action>Update workflow_status["create-ux-design"] = "{default_output_file}"</action>
<action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
<action>Find first non-completed workflow in workflow_status (next workflow to do)</action>

View File

@ -652,7 +652,7 @@ Your PRD is complete!"
<action>Check workflow path to determine next expected workflows:
- Look for "create-epics-and-stories" as optional after PRD
- Look for "create-design" as conditional (if_has_ui)
- Look for "create-ux-design" as conditional (if_has_ui)
- Look for "create-epics-and-stories-after-ux" as optional
- Identify the required next phase workflow
</action>
@ -675,7 +675,7 @@ Based on your {{project_track}} workflow path, you can:
<check if="UI_exists">
**Option B: UX Design First** (Recommended if UI)
`workflow create-design`
`workflow create-ux-design`
- Design user experience and interactions
- Epic breakdown can incorporate UX details later
</check>
@ -691,7 +691,7 @@ Based on your {{project_track}} workflow path, you can:
<check if="standalone_mode == true">
**Typical next workflows:**
1. `workflow create-design` - UX Design (if UI exists)
1. `workflow create-ux-design` - UX Design (if UI exists)
2. `workflow create-architecture` - Technical architecture
3. `workflow create-epics-and-stories` - Epic breakdown

View File

@ -60,10 +60,10 @@ phases:
agent: "pm"
command: "validate-prd"
- id: "create-design"
- id: "create-ux-design"
recommended: true
agent: "ux-designer"
command: "create-design"
command: "create-ux-design"
note: "Recommended - must integrate with existing UX patterns"
- phase: 2

View File

@ -48,10 +48,10 @@ phases:
agent: "pm"
command: "validate-prd"
- id: "create-design"
- id: "create-ux-design"
recommended: true
agent: "ux-designer"
command: "create-design"
command: "create-ux-design"
note: "Highly recommended for enterprise - design system and patterns"
- phase: 2

View File

@ -59,10 +59,10 @@ phases:
agent: "pm"
command: "validate-prd"
- id: "create-design"
- id: "create-ux-design"
conditional: "if_has_ui"
agent: "ux-designer"
command: "create-design"
command: "create-ux-design"
- phase: 2
name: "Solutioning"

View File

@ -48,10 +48,10 @@ phases:
command: "validate-prd"
note: "Quality check for PRD completeness"
- id: "create-design"
- id: "create-ux-design"
conditional: "if_has_ui"
agent: "ux-designer"
command: "create-design"
command: "create-ux-design"
note: "Determined after PRD - user/agent decides if needed"
- phase: 2

View File

@ -359,6 +359,25 @@ class ConfigCollector {
return result;
}
/**
* Get the default username from the system
* @returns {string} Capitalized username\
*/
getDefaultUsername() {
let result = 'BMad';
try {
const os = require('node:os');
const userInfo = os.userInfo();
if (userInfo && userInfo.username) {
const username = userInfo.username;
result = username.charAt(0).toUpperCase() + username.slice(1);
}
} catch {
// Do nothing, just return 'BMad'
}
return result;
}
/**
* Collect configuration for a single module
* @param {string} moduleName - Module name
@ -604,6 +623,11 @@ class ConfigCollector {
}
}
// Special handling for user_name: default to system user
if (moduleName === 'core' && key === 'user_name' && !existingValue) {
item.default = this.getDefaultUsername();
}
// Determine question type and default value
let questionType = 'input';
let defaultValue = item.default;

View File

@ -20,7 +20,7 @@ const { getAgentsFromBmad, getAgentsFromDir } = require('./shared/bmad-artifacts
*/
class AntigravitySetup extends BaseIdeSetup {
constructor() {
super('antigravity', 'Google Antigravity', false);
super('antigravity', 'Google Antigravity', true);
this.configDir = '.agent';
this.workflowsDir = 'workflows';
}

View File

@ -201,7 +201,12 @@ class UI {
CLIUtils.displaySection('Tool Integration', 'Select AI coding assistants and IDEs to configure');
const answers = await inquirer.prompt([
let answers;
let userConfirmedNoTools = false;
// Loop until user selects at least one tool OR explicitly confirms no tools
while (!userConfirmedNoTools) {
answers = await inquirer.prompt([
{
type: 'checkbox',
name: 'ides',
@ -211,6 +216,37 @@ class UI {
},
]);
// If tools were selected, we're done
if (answers.ides && answers.ides.length > 0) {
break;
}
// Warn that no tools were selected - users often miss the spacebar requirement
console.log();
console.log(chalk.red.bold('⚠️ WARNING: No tools were selected!'));
console.log(chalk.red(' You must press SPACEBAR to select items, then ENTER to confirm.'));
console.log(chalk.red(' Simply highlighting an item does NOT select it.'));
console.log();
const { goBack } = await inquirer.prompt([
{
type: 'confirm',
name: 'goBack',
message: chalk.yellow('Would you like to go back and select at least one tool?'),
default: true,
},
]);
if (goBack) {
// Re-display the section header before looping back
console.log();
CLIUtils.displaySection('Tool Integration', 'Select AI coding assistants and IDEs to configure');
} else {
// User explicitly chose to proceed without tools
userConfirmedNoTools = true;
}
}
return {
ides: answers.ides || [],
skipIde: !answers.ides || answers.ides.length === 0,