agentvibes 3.0.0 → 3.2.0

package/.bmad/bmm/workflows/{frame-expert → diagrams}/create-diagram/instructions.md

@@ -8,7 +8,7 @@
 <workflow>
 
   <step n="0" goal="Contextual Analysis">
-    <action>Review user's request and extract: diagram type, components/entities, relationships, notation preferences, save location</action>
+    <action>Review user's request and extract: diagram type, components/entities, relationships, notation preferences</action>
     <check if="ALL requirements clear"><action>Skip to Step 5</action></check>
     <check if="SOME requirements clear"><action>Only ask about missing info in Steps 1-2</action></check>
   </step>
@@ -24,15 +24,14 @@
       6. Network Diagram
       7. Other
     </action>
-    <action>WAIT for selection, store in {{diagram_type}}</action>
+    <action>WAIT for selection</action>
   </step>
 
   <step n="2" goal="Gather Requirements" elicit="true">
-    <action>Ask component count (Small/Medium/Large/Very Large)</action>
-    <action>Ask relationship types (Simple/Hierarchical/Many-to-many/Mixed)</action>
-    <action>Ask notation standard (Standard/Simplified/Strict UML-ERD/Company specific)</action>
-    <action>Ask save location (Default/Custom/Architecture folder/Specific folder)</action>
-    <action>Store all responses in variables</action>
+    <action>Ask: "Describe the components/entities and their relationships"</action>
+    <action>Ask: "What notation standard? (Standard/Simplified/Strict UML-ERD)"</action>
+    <action>WAIT for user input</action>
+    <action>Summarize what will be included and confirm with user</action>
   </step>
 
   <step n="3" goal="Check for Existing Theme" elicit="true">
@@ -117,12 +116,12 @@
 
   <step n="8" goal="Optimize and Save">
     <action>Strip unused elements and elements with isDeleted: true</action>
-    <action>Save to {{save_location}}</action>
+    <action>Save to {{default_output_file}}</action>
   </step>
 
   <step n="9" goal="Validate JSON Syntax">
     <critical>NEVER delete the file if validation fails - always fix syntax errors</critical>
-    <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{save_location}}', 'utf8')); console.log('✓ Valid JSON')"</action>
+    <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{default_output_file}}', 'utf8')); console.log('✓ Valid JSON')"</action>
     <check if="validation fails (exit code 1)">
       <action>Read the error message carefully - it shows the syntax error and position</action>
       <action>Open the file and navigate to the error location</action>
@@ -131,7 +130,7 @@
       <action>Re-run validation with the same command</action>
       <action>Repeat until validation passes</action>
     </check>
-    <action>Once validation passes, confirm: "Diagram created at {{save_location}}. Open to view?"</action>
+    <action>Once validation passes, confirm: "Diagram created at {{default_output_file}}. Open to view?"</action>
   </step>
 
   <step n="10" goal="Validate Content">

package/.bmad/bmm/workflows/diagrams/create-diagram/workflow.yaml

@@ -0,0 +1,26 @@
+name: create-excalidraw-diagram
+description: "Create system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format"
+author: "BMad"
+
+# Config values
+config_source: "{project-root}/.bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+
+# Workflow components
+installed_path: "{project-root}/.bmad/bmm/workflows/diagrams/create-diagram"
+shared_path: "{project-root}/.bmad/bmm/workflows/diagrams/_shared"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Core Excalidraw resources (universal knowledge)
+helpers: "{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md"
+json_validation: "{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md"
+
+# Domain-specific resources (technical diagrams)
+templates: "{shared_path}/excalidraw-templates.yaml"
+library: "{shared_path}/excalidraw-library.json"
+
+# Output file (respects user's configured output_folder)
+default_output_file: "{output_folder}/diagrams/diagram-{timestamp}.excalidraw"
+
+standalone: true

package/.bmad/bmm/workflows/{frame-expert → diagrams}/create-flowchart/instructions.md

@@ -38,7 +38,6 @@
       5. Other - Describe your specific flowchart needs
     </action>
     <action>WAIT for user selection (1-5)</action>
-    <action>Store selection in {{flowchart_type}}</action>
 
     <action>Ask Question 2: "How many main steps are in this flow?"</action>
     <action>Present numbered options:
@@ -72,7 +71,7 @@
       <action>Ask for specific path</action>
       <action>WAIT for user input</action>
     </check>
-    <action>Store final path in {{save_location}}</action>
+    <action>Store final path in {{default_output_file}}</action>
   </step>
 
   <step n="2" goal="Check for Existing Theme" elicit="true">
@@ -217,12 +216,12 @@
 
   <step n="7" goal="Optimize and Save">
     <action>Strip unused elements and elements with isDeleted: true</action>
-    <action>Save to {{save_location}}</action>
+    <action>Save to {{default_output_file}}</action>
   </step>
 
   <step n="8" goal="Validate JSON Syntax">
     <critical>NEVER delete the file if validation fails - always fix syntax errors</critical>
-    <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{save_location}}', 'utf8')); console.log('✓ Valid JSON')"</action>
+    <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{default_output_file}}', 'utf8')); console.log('✓ Valid JSON')"</action>
     <check if="validation fails (exit code 1)">
       <action>Read the error message carefully - it shows the syntax error and position</action>
       <action>Open the file and navigate to the error location</action>
@@ -231,7 +230,7 @@
       <action>Re-run validation with the same command</action>
       <action>Repeat until validation passes</action>
     </check>
-    <action>Once validation passes, confirm with user: "Flowchart created at {{save_location}}. Open to view?"</action>
+    <action>Once validation passes, confirm with user: "Flowchart created at {{default_output_file}}. Open to view?"</action>
   </step>
 
   <step n="9" goal="Validate Content">

package/.bmad/bmm/workflows/diagrams/create-flowchart/workflow.yaml

@@ -0,0 +1,26 @@
+name: create-excalidraw-flowchart
+description: "Create a flowchart visualization in Excalidraw format for processes, pipelines, or logic flows"
+author: "BMad"
+
+# Config values
+config_source: "{project-root}/.bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+
+# Workflow components
+installed_path: "{project-root}/.bmad/bmm/workflows/diagrams/create-flowchart"
+shared_path: "{project-root}/.bmad/bmm/workflows/diagrams/_shared"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Core Excalidraw resources (universal knowledge)
+helpers: "{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md"
+json_validation: "{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md"
+
+# Domain-specific resources (technical diagrams)
+templates: "{shared_path}/excalidraw-templates.yaml"
+library: "{shared_path}/excalidraw-library.json"
+
+# Output file (respects user's configured output_folder)
+default_output_file: "{output_folder}/diagrams/flowchart-{timestamp}.excalidraw"
+
+standalone: true

package/.bmad/bmm/workflows/{frame-expert → diagrams}/create-wireframe/instructions.md

@@ -21,7 +21,7 @@
       4. Tablet App
       5. Multi-platform
     </action>
-    <action>WAIT for selection, store in {{wireframe_type}}</action>
+    <action>WAIT for selection</action>
   </step>
 
   <step n="2" goal="Gather Requirements" elicit="true">
@@ -108,12 +108,12 @@
 
   <step n="8" goal="Optimize and Save">
     <action>Strip unused elements and elements with isDeleted: true</action>
-    <action>Save to {{save_location}}</action>
+    <action>Save to {{default_output_file}}</action>
   </step>
 
   <step n="9" goal="Validate JSON Syntax">
     <critical>NEVER delete the file if validation fails - always fix syntax errors</critical>
-    <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{save_location}}', 'utf8')); console.log('✓ Valid JSON')"</action>
+    <action>Run: node -e "JSON.parse(require('fs').readFileSync('{{default_output_file}}', 'utf8')); console.log('✓ Valid JSON')"</action>
     <check if="validation fails (exit code 1)">
       <action>Read the error message carefully - it shows the syntax error and position</action>
       <action>Open the file and navigate to the error location</action>

package/.bmad/bmm/workflows/diagrams/create-wireframe/workflow.yaml

@@ -0,0 +1,26 @@
+name: create-excalidraw-wireframe
+description: "Create website or app wireframes in Excalidraw format"
+author: "BMad"
+
+# Config values
+config_source: "{project-root}/.bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+
+# Workflow components
+installed_path: "{project-root}/.bmad/bmm/workflows/diagrams/create-wireframe"
+shared_path: "{project-root}/.bmad/bmm/workflows/diagrams/_shared"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Core Excalidraw resources (universal knowledge)
+helpers: "{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md"
+json_validation: "{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md"
+
+# Domain-specific resources (technical diagrams)
+templates: "{shared_path}/excalidraw-templates.yaml"
+library: "{shared_path}/excalidraw-library.json"
+
+# Output file (respects user's configured output_folder)
+default_output_file: "{output_folder}/diagrams/wireframe-{timestamp}.excalidraw"
+
+standalone: true

package/.bmad/bmm/workflows/document-project/instructions.md

@@ -196,7 +196,7 @@ Your choice [1/2/3]:
 
 - Mode: {{workflow_mode}}
 - Scan Level: {{scan_level}}
-- Output: {output_folder}/bmm-index.md and related files
+- Output: {output_folder}/index.md and related files
 
 {{#if status_file_found}}
 **Status Updated:**

package/.bmad/bmm/workflows/document-project/workflows/deep-dive-instructions.md

@@ -20,7 +20,7 @@
 
 {{#if has_api_routes}}
 
-### API Routes ({{api_route_count}} endpoints found)
+## API Routes ({{api_route_count}} endpoints found)
 
 {{#each api_route_groups}}
 {{group_index}}. {{group_name}} - {{endpoint_count}} endpoints in `{{path}}`
@@ -29,7 +29,7 @@
 
 {{#if has_feature_modules}}
 
-### Feature Modules ({{feature_count}} features)
+## Feature Modules ({{feature_count}} features)
 
 {{#each feature_modules}}
 {{module_index}}. {{module_name}} - {{file_count}} files in `{{path}}`

package/.bmad/bmm/workflows/generate-project-context/project-context-template.md

@@ -0,0 +1,20 @@
+---
+project_name: '{{project_name}}'
+user_name: '{{user_name}}'
+date: '{{date}}'
+sections_completed: []
+---
+
+# Project Context for AI Agents
+
+_This file contains critical rules and patterns that AI agents must follow when implementing code in this project. Focus on unobvious details that agents might otherwise miss._
+
+---
+
+## Technology Stack & Versions
+
+_Documented after discovery phase_
+
+## Critical Implementation Rules
+
+_Documented after discovery phase_

package/.bmad/bmm/workflows/generate-project-context/steps/step-01-discover.md

@@ -0,0 +1,193 @@
+# Step 1: Context Discovery & Initialization
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+- ✅ ALWAYS treat this as collaborative discovery between technical peers
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- 💬 FOCUS on discovering existing project context and technology stack
+- 🎯 IDENTIFY critical implementation rules that AI agents need
+- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- 📖 Read existing project files to understand current context
+- 💾 Initialize document and update frontmatter
+- 🚫 FORBIDDEN to load next step until discovery is complete
+
+## CONTEXT BOUNDARIES:
+
+- Variables from workflow.md are available in memory
+- Focus on existing project files and architecture decisions
+- Look for patterns, conventions, and unique requirements
+- Prioritize rules that prevent implementation mistakes
+
+## YOUR TASK:
+
+Discover the project's technology stack, existing patterns, and critical implementation rules that AI agents must follow when writing code.
+
+## DISCOVERY SEQUENCE:
+
+### 1. Check for Existing Project Context
+
+First, check if project context already exists:
+
+- Look for file at `{output_folder}/project_context.md`
+- If exists: Read complete file to understand existing rules
+- Present to user: "Found existing project context with {number_of_sections} sections. Would you like to update this or create a new one?"
+
+### 2. Discover Project Technology Stack
+
+Load and analyze project files to identify technologies:
+
+**Architecture Document:**
+
+- Look for `{output_folder}/architecture.md`
+- Extract technology choices with specific versions
+- Note architectural decisions that affect implementation
+
+**Package Files:**
+
+- Check for `package.json`, `requirements.txt`, `Cargo.toml`, etc.
+- Extract exact versions of all dependencies
+- Note development vs production dependencies
+
+**Configuration Files:**
+
+- Look for TypeScript config (`tsconfig.json`)
+- Build tool configs (webpack, vite, next.config.js, etc.)
+- Linting and formatting configs (.eslintrc, .prettierrc, etc.)
+- Testing configurations (jest.config.js, vitest.config.ts, etc.)
+
+### 3. Identify Existing Code Patterns
+
+Search through existing codebase for patterns:
+
+**Naming Conventions:**
+
+- File naming patterns (PascalCase, kebab-case, etc.)
+- Component/function naming conventions
+- Variable naming patterns
+- Test file naming patterns
+
+**Code Organization:**
+
+- How components are structured
+- Where utilities and helpers are placed
+- How services are organized
+- Test organization patterns
+
+**Documentation Patterns:**
+
+- Comment styles and conventions
+- Documentation requirements
+- README and API doc patterns
+
+### 4. Extract Critical Implementation Rules
+
+Look for rules that AI agents might miss:
+
+**Language-Specific Rules:**
+
+- TypeScript strict mode requirements
+- Import/export conventions
+- Async/await vs Promise usage patterns
+- Error handling patterns specific to the language
+
+**Framework-Specific Rules:**
+
+- React hooks usage patterns
+- API route conventions
+- Middleware usage patterns
+- State management patterns
+
+**Testing Rules:**
+
+- Test structure requirements
+- Mock usage conventions
+- Integration vs unit test boundaries
+- Coverage requirements
+
+**Development Workflow Rules:**
+
+- Branch naming conventions
+- Commit message patterns
+- PR review requirements
+- Deployment procedures
+
+### 5. Initialize Project Context Document
+
+Based on discovery, create or update the context document:
+
+#### A. Fresh Document Setup (if no existing context)
+
+Copy template from `{installed_path}/project-context-template.md` to `{output_folder}/project_context.md`
+Initialize frontmatter with:
+
+```yaml
+---
+project_name: '{{project_name}}'
+user_name: '{{user_name}}'
+date: '{{date}}'
+sections_completed: ['technology_stack']
+existing_patterns_found: { { number_of_patterns_discovered } }
+---
+```
+
+#### B. Existing Document Update
+
+Load existing context and prepare for updates
+Set frontmatter `sections_completed` to track what will be updated
+
+### 6. Present Discovery Summary
+
+Report findings to user:
+
+"Welcome {{user_name}}! I've analyzed your project for {{project_name}} to discover the context that AI agents need.
+
+**Technology Stack Discovered:**
+{{list_of_technologies_with_versions}}
+
+**Existing Patterns Found:**
+
+- {{number_of_patterns}} implementation patterns
+- {{number_of_conventions}} coding conventions
+- {{number_of_rules}} critical rules
+
+**Key Areas for Context Rules:**
+
+- {{area_1}} (e.g., TypeScript configuration)
+- {{area_2}} (e.g., Testing patterns)
+- {{area_3}} (e.g., Code organization)
+
+{if_existing_context}
+**Existing Context:** Found {{sections}} sections already defined. We can update or add to these.
+{/if_existing_context}
+
+Ready to create/update your project context. This will help AI agents implement code consistently with your project's standards.
+
+[C] Continue to context generation"
+
+## SUCCESS METRICS:
+
+✅ Existing project context properly detected and handled
+✅ Technology stack accurately identified with versions
+✅ Critical implementation patterns discovered
+✅ Project context document properly initialized
+✅ Discovery findings clearly presented to user
+✅ User ready to proceed with context generation
+
+## FAILURE MODES:
+
+❌ Not checking for existing project context before creating new one
+❌ Missing critical technology versions or configurations
+❌ Overlooking important coding patterns or conventions
+❌ Not initializing frontmatter properly
+❌ Not presenting clear discovery summary to user
+
+## NEXT STEP:
+
+After user selects [C] to continue, load `./step-02-generate.md` to collaboratively generate the specific project context rules.
+
+Remember: Do NOT proceed to step-02 until user explicitly selects [C] from the menu and discovery is confirmed!