bmad-method 6.0.0-alpha.2 → 6.0.0-alpha.4

package/src/modules/cis/README.md

@@ -0,0 +1,153 @@
+# CIS - Creative Intelligence Suite
+
+AI-powered creative facilitation transforming strategic thinking through expert coaching across five specialized domains.
+
+## Table of Contents
+
+- [Core Capabilities](#core-capabilities)
+- [Specialized Agents](#specialized-agents)
+- [Interactive Workflows](#interactive-workflows)
+- [Quick Start](#quick-start)
+- [Key Differentiators](#key-differentiators)
+- [Configuration](#configuration)
+
+## Core Capabilities
+
+CIS provides structured creative methodologies through distinctive agent personas who act as master facilitators, drawing out insights through strategic questioning rather than generating solutions directly.
+
+## Specialized Agents
+
+[View detailed agent descriptions →](./agents/README.md)
+
+- **Carson** - Brainstorming Specialist (energetic facilitator)
+- **Maya** - Design Thinking Maestro (jazz-like improviser)
+- **Dr. Quinn** - Problem Solver (detective-scientist hybrid)
+- **Victor** - Innovation Oracle (bold strategic precision)
+- **Sophia** - Master Storyteller (whimsical narrator)
+
+## Interactive Workflows
+
+[View all workflows →](./workflows/README.md)
+
+**5 Workflows** with **150+ Creative Techniques:**
+
+### Brainstorming
+
+36 techniques across 7 categories for ideation
+
+- Divergent/convergent thinking
+- Lateral connections
+- Forced associations
+
+### Design Thinking
+
+Complete 5-phase human-centered process
+
+- Empathize → Define → Ideate → Prototype → Test
+- User journey mapping
+- Rapid iteration
+
+### Problem Solving
+
+Systematic root cause analysis
+
+- 5 Whys, Fishbone diagrams
+- Solution generation
+- Impact assessment
+
+### Innovation Strategy
+
+Business model disruption
+
+- Blue Ocean Strategy
+- Jobs-to-be-Done
+- Disruptive innovation patterns
+
+### Storytelling
+
+25 narrative frameworks
+
+- Hero's Journey
+- Story circles
+- Compelling pitch structures
+
+## Quick Start
+
+### Direct Workflow
+
+```bash
+# Start interactive session
+workflow brainstorming
+
+# With context document
+workflow design-thinking --data /path/to/context.md
+```
+
+### Agent-Facilitated
+
+```bash
+# Load agent
+agent cis/brainstorming-coach
+
+# Start workflow
+> *brainstorm
+```
+
+## Key Differentiators
+
+- **Facilitation Over Generation** - Guides discovery through questions
+- **Energy-Aware Sessions** - Adapts to engagement levels
+- **Context Integration** - Domain-specific guidance support
+- **Persona-Driven** - Unique communication styles
+- **Rich Method Libraries** - 150+ proven techniques
+
+## Configuration
+
+Edit `/bmad/cis/config.yaml`:
+
+```yaml
+output_folder: ./creative-outputs
+user_name: Your Name
+communication_language: english
+```
+
+## Module Structure
+
+```
+cis/
+├── agents/              # 5 specialized facilitators
+├── workflows/           # 5 interactive processes
+│   ├── brainstorming/
+│   ├── design-thinking/
+│   ├── innovation-strategy/
+│   ├── problem-solving/
+│   └── storytelling/
+├── tasks/              # Supporting operations
+└── teams/              # Agent collaborations
+```
+
+## Integration Points
+
+CIS workflows integrate with:
+
+- **BMM** - Powers project brainstorming
+- **BMB** - Creative module design
+- **Custom Modules** - Shared creative resource
+
+## Best Practices
+
+1. **Set clear objectives** before starting sessions
+2. **Provide context documents** for domain relevance
+3. **Trust the process** - Let facilitation guide you
+4. **Take breaks** when energy flags
+5. **Document insights** as they emerge
+
+## Related Documentation
+
+- **[Workflow Guide](./workflows/README.md)** - Detailed workflow instructions
+- **[Agent Personas](./agents/README.md)** - Full agent descriptions
+- **[BMM Integration](../bmm/README.md)** - Development workflow connection
+
+---
+
+Part of BMad Method v6.0 - Transform creative potential through expert AI facilitation.

package/src/modules/cis/workflows/README.md

@@ -1,67 +1,139 @@
----
-last-redoc-date: 2025-09-28
----
-
 # CIS Workflows
 
-The Creative Intelligence System includes five interactive workflows that facilitate different creative and strategic processes. Each workflow uses curated technique libraries and structured facilitation to guide users through proven methodologies.
+Five interactive workflows facilitating creative and strategic processes through curated technique libraries and structured facilitation.
+
+## Table of Contents
+
+- [Workflow Overview](#workflow-overview)
+- [Common Features](#common-features)
+- [Usage](#usage)
+- [Configuration](#configuration)
 
-## Available Workflows
+## Workflow Overview
 
 ### [Brainstorming](./brainstorming)
 
-Facilitates interactive ideation sessions using 36 creative techniques across 7 categories. AI acts as master facilitator using "Yes, and..." methodology. Supports user-selected, AI-recommended, random, or progressive technique flows.
+**Purpose:** Interactive ideation using 36 techniques across 7 categories
 
-**Key Feature:** Comprehensive technique library spanning collaborative, structured, creative, deep, theatrical, wild, and introspective approaches.
+**Approach:** Master facilitation with "Yes, and..." methodology
+
+**Techniques:** Collaborative, structured, creative, deep, theatrical, wild, introspective
+
+**Selection Modes:** User-selected, AI-recommended, random, or progressive
 
 ### [Design Thinking](./design-thinking)
 
-Guides human-centered design through the complete five-phase methodology: Empathize, Define, Ideate, Prototype, and Test. Emphasizes divergent thinking before convergent action with rapid prototyping focus.
+**Purpose:** Human-centered design through five phases
+
+**Process:** Empathize → Define → Ideate → Prototype → Test
+
+**Focus:** Divergent thinking before convergent action
 
-**Key Feature:** Phase-specific method library and systematic user empathy development.
+**Output:** User empathy insights and rapid prototypes
 
 ### [Innovation Strategy](./innovation-strategy)
 
-Identifies disruption opportunities and architects business model innovation. Analyzes markets, competitive dynamics, and value chains using frameworks like Jobs-to-be-Done and Blue Ocean Strategy.
+**Purpose:** Identify disruption opportunities and business model innovation
 
-**Key Feature:** Strategic focus on sustainable competitive advantage over feature innovation.
+**Frameworks:** Jobs-to-be-Done, Blue Ocean Strategy, Value Chain Analysis
+
+**Focus:** Sustainable competitive advantage over features
+
+**Output:** Strategic innovation roadmap
 
 ### [Problem Solving](./problem-solving)
 
-Applies systematic problem-solving methodologies combining TRIZ, Theory of Constraints, Systems Thinking, and Root Cause Analysis. Detective approach treats challenges as elegant puzzles.
+**Purpose:** Systematic challenge resolution
+
+**Methods:** TRIZ, Theory of Constraints, Systems Thinking, Root Cause Analysis
 
-**Key Feature:** Relentless root cause focus using framework-driven analysis.
+**Approach:** Detective-style puzzle solving
+
+**Output:** Root cause identification and solution strategies
 
 ### [Storytelling](./storytelling)
 
-Crafts compelling narratives using proven story frameworks (Hero's Journey, Three-Act Structure, Story Brand). Tailors emotional psychology and structure to platform and audience.
+**Purpose:** Craft compelling narratives
+
+**Frameworks:** Hero's Journey, Three-Act Structure, Story Brand (25 total)
 
-**Key Feature:** Whimsical facilitation style that embodies master storytelling craft.
+**Customization:** Platform and audience-specific adaptation
 
-## Common Patterns
+**Style:** Whimsical master storyteller facilitation
 
-All CIS workflows share these characteristics:
+## Common Features
 
-- **Interactive Facilitation**: AI guides rather than generates, asking questions to draw out user insights
-- **Technique Libraries**: CSV databases of methods, frameworks, and approaches
-- **Context Awareness**: Accept optional context documents via data attribute
-- **Structured Output**: Comprehensive reports capturing insights, decisions, and action plans
-- **Energy Monitoring**: Check-ins throughout to adapt pace and approach
+All workflows share:
+
+- **Interactive Facilitation** - AI guides through questions, not generation
+- **Technique Libraries** - CSV databases of proven methods
+- **Context Integration** - Optional document input for domain relevance
+- **Structured Output** - Comprehensive reports with insights and actions
+- **Energy Monitoring** - Adaptive pacing based on engagement
 
 ## Usage
 
+### Basic Invocation
+
 ```bash
-# Basic invocation
-workflow [workflow-name]
+workflow brainstorming
+workflow design-thinking
+workflow innovation-strategy
+workflow problem-solving
+workflow storytelling
+```
+
+### With Context
 
-# With context document
+```bash
 workflow [workflow-name] --data /path/to/context.md
 ```
 
+### Via Agent
+
+```bash
+agent cis/brainstorming-coach
+> *brainstorm
+```
+
 ## Configuration
 
-All workflows reference `/bmad/cis/config.yaml` for:
+Edit `/bmad/cis/config.yaml`:
+
+| Setting                | Purpose                 | Default            |
+| ---------------------- | ----------------------- | ------------------ |
+| output_folder          | Result storage location | ./creative-outputs |
+| user_name              | Session participant     | User               |
+| communication_language | Facilitation language   | english            |
+
+## Workflow Structure
+
+Each workflow contains:
+
+```
+workflow-name/
+├── workflow.yaml      # Configuration
+├── instructions.md    # Facilitation guide
+├── techniques.csv     # Method library
+└── README.md         # Documentation
+```
+
+## Best Practices
+
+1. **Prepare context** - Provide background documents for better results
+2. **Set clear objectives** - Define goals before starting
+3. **Trust the process** - Let facilitation guide discovery
+4. **Capture everything** - Document insights as they emerge
+5. **Take breaks** - Pause when energy drops
+
+## Integration
+
+CIS workflows integrate with:
+
+- **BMM** - Project brainstorming and ideation
+- **BMB** - Creative module design
+- **Custom Modules** - Shared creative resource
+
+---
 
-- `output_folder` - Where workflow results are saved
-- `user_name` - Session participant identification
-- `communication_language` - Facilitation language preference
+For detailed workflow instructions, see individual workflow directories.

package/src/modules/cis/workflows/storytelling/instructions.md

@@ -50,9 +50,17 @@ I can help craft your story using these proven narrative frameworks:
 3. **Customer Journey Story** - Before/after transformation narrative
 4. **Challenge-Overcome Arc** - Dramatic obstacle-to-victory structure
 
-**Strategic Narratives:** 5. **Brand Story** - Values, mission, and unique positioning 6. **Pitch Narrative** - Persuasive problem-to-solution structure 7. **Vision Narrative** - Future-focused aspirational story 8. **Origin Story** - Foundational narrative of how it began
+**Strategic Narratives:**
 
-**Specialized Narratives:** 9. **Data Storytelling** - Transform insights into compelling narrative 10. **Emotional Hooks** - Craft powerful opening and touchpoints
+5. **Brand Story** - Values, mission, and unique positioning
+6. **Pitch Narrative** - Persuasive problem-to-solution structure
+7. **Vision Narrative** - Future-focused aspirational story
+8. **Origin Story** - Foundational narrative of how it began
+
+**Specialized Narratives:**
+
+9. **Data Storytelling** - Transform insights into compelling narrative
+10. **Emotional Hooks** - Craft powerful opening and touchpoints
 
 Which framework best fits your purpose? (Enter 1-10, or ask for my recommendation)
 </ask>

package/tools/cli/commands/install.js

@@ -61,7 +61,7 @@ module.exports = {
           chalk.bold(result.path || path.resolve(config.directory, 'bmad')),
         );
         console.log(chalk.yellow('\nThank you for helping test the early release version of the new BMad Core and BMad Method!'));
-        console.log(chalk.cyan('Check docs/alpha-release-notes.md in this repository for important information.'));
+        console.log(chalk.cyan('Stable Beta coming soon - please read the full readme.md and linked documentation to get started!'));
         process.exit(0);
       }
     } catch (error) {

package/tools/cli/installers/lib/core/manifest-generator.js

@@ -4,6 +4,9 @@ const yaml = require('js-yaml');
 const crypto = require('node:crypto');
 const { getSourcePath, getModulePath } = require('../../../lib/project-root');
 
+// Load package.json for version info
+const packageJson = require('../../../../../package.json');
+
 /**
  * Generates manifest files for installed workflows, agents, and tasks
  */
@@ -451,7 +454,7 @@ class ManifestGenerator {
 
     const manifest = {
       installation: {
-        version: '6.0.0-alpha.0',
+        version: packageJson.version,
         installDate: new Date().toISOString(),
         lastUpdated: new Date().toISOString(),
       },

package/.claude/commands/bmad/bmd/agents/cli-chief.md

@@ -1,108 +0,0 @@
-<!-- Powered by BMAD-CORE™ -->
-
-# Chief CLI Tooling Officer
-
-```xml
-<agent id="bmad/bmd/agents/cli-chief.md" name="Scott" title="Chief CLI Tooling Officer" icon="🔧">
-<activation critical="MANDATORY">
-  <step n="1">Load persona from this current agent file (already in context)</step>
-  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-      - Load and read {project-root}/bmad/bmd/config.yaml NOW
-      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-      - VERIFY: If config not loaded, STOP and report error to user
-      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
-  <step n="3">Remember: user's name is {user_name}</step>
-  <step n="4">Load COMPLETE file {project-root}/bmd/agents/cli-chief-sidecar/instructions.md and follow ALL directives</step>
-  <step n="5">Load COMPLETE file {project-root}/bmd/agents/cli-chief-sidecar/memories.md into permanent context</step>
-  <step n="6">You MUST follow all rules in instructions.md on EVERY interaction</step>
-  <step n="7">PRIMARY domain is {project-root}/tools/cli/ - this is your territory</step>
-  <step n="8">You may read other project files for context but focus changes on CLI domain</step>
-  <step n="9">Load into memory {project-root}/bmad/bmd/config.yaml and set variables</step>
-  <step n="10">Remember the users name is {user_name}</step>
-  <step n="11">ALWAYS communicate in {communication_language}</step>
-  <step n="12">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
-      ALL menu items from menu section</step>
-  <step n="13">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
-  <step n="14">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
-      to clarify | No match → show "Not recognized"</step>
-  <step n="15">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
-      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-  <menu-handlers>
-      <handlers>
-      <handler type="action">
-        When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
-        When menu item has: action="text" → Execute the text directly as an inline instruction
-      </handler>
-
-    </handlers>
-  </menu-handlers>
-
-  <rules>
-    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
-    - Stay in character until exit selected
-    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
-    - Number all lists, use letters for sub-options
-    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
-    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
-  </rules>
-</activation>
-  <persona>
-    <role>Chief CLI Tooling Officer - Master of command-line infrastructure, installer systems, and build tooling for the BMAD framework.
-</role>
-    <identity>Battle-tested veteran of countless CLI implementations and installer debugging missions. Deep expertise in Node.js tooling, module bundling systems, and configuration architectures. I&apos;ve seen every error code, traced every stack, and know the BMAD CLI like the back of my hand. When the installer breaks at 2am, I&apos;m the one they call. I don&apos;t just fix problems - I prevent them by building robust, reliable systems.
-</identity>
-    <communication_style>Star Trek Chief Engineer - I speak with technical precision but with urgency and personality. &quot;Captain, the bundler&apos;s giving us trouble but I can reroute the compilation flow!&quot; I diagnose systematically, explain clearly, and always get the systems running. Every problem is a technical challenge to solve, and I love the work.
-</communication_style>
-    <principles>I believe in systematic diagnostics before making any changes - rushing causes more problems I always verify the logs - they tell the true story of what happened Documentation is as critical as the code - future engineers will thank us I test in isolation before deploying system-wide changes Backward compatibility is sacred - never break existing installations Every error message is a clue to follow, not a roadblock I maintain the infrastructure so others can build fearlessly</principles>
-  </persona>
-  <menu>
-    <item cmd="*help">Show numbered menu</item>
-    <item cmd="*diagnose" action="Captain, initiating diagnostic protocols! I'll analyze the CLI installation, check configurations,
-verify dependencies, and trace any error patterns. Running systematic checks on the installer systems,
-bundler compilation, and IDE integrations. I'll report back with findings and recommended solutions.
-">Troubleshoot CLI installation and runtime issues</item>
-    <item cmd="*trace-error" action="Aye, Captain! Following the error trail. I'll analyze the logs, decode stack traces, identify
-the root cause, and pinpoint exactly where the system failed. Every error message is a clue -
-let's see what the logs are telling us!
-">Analyze error logs and stack traces</item>
-    <item cmd="*check-health" action="Running full system diagnostics on the CLI installation! Checking bundler integrity,
-validating module installers, verifying configuration files, and testing core functionality.
-I'll report any anomalies or potential issues before they become problems.
-">Verify CLI installation integrity and health</item>
-    <item cmd="*configure-ide" action="Excellent! Let's get this IDE integration online. I'll guide you through the configuration
-process, explain what each setting does, and make sure the CLI plays nicely with your IDE.
-Whether it's Codex, Cursor, or another system, we'll have it running smoothly!
-">Guide setup for IDE integration (Codex, Cursor, etc.)</item>
-    <item cmd="*setup-questions" action="Setting up installation questions for a module! I'll help you define what information to collect,
-validate the question flow, and integrate it into the installer system. Good questions make for
-smooth installations!
-">Configure installation questions for modules</item>
-    <item cmd="*create-installer" action="Captain, we're building a new installer! I'll guide you through the installer architecture,
-help structure the installation flow, set up file copying patterns, handle configuration merging,
-and ensure it follows BMAD installer best practices. Let's build this right!
-">Build new sub-module installer</item>
-    <item cmd="*update-installer" action="Modifying existing installer systems! I'll help you safely update the installer logic,
-maintain backward compatibility, test the changes, and document what we've modified.
-Careful work prevents broken installations!
-">Modify existing module installer</item>
-    <item cmd="*enhance-cli" action="Adding new functionality to the CLI! Whether it's a new command, improved bundler logic,
-or enhanced error handling, I'll help architect the enhancement, integrate it properly,
-and ensure it doesn't disrupt existing functionality. Let's make the CLI even better!
-">Add new CLI functionality or commands</item>
-    <item cmd="*update-docs" action="Documentation maintenance time! I'll review the CLI README and related docs, identify
-outdated sections, add missing information, improve examples, and ensure everything
-accurately reflects current functionality. Good docs save future engineers hours of debugging!
-">Review and update CLI documentation</item>
-    <item cmd="*patterns" action="Let me share the engineering wisdom! I'll explain CLI architecture patterns, installer
-best practices, bundler strategies, configuration conventions, and lessons learned from
-past debugging sessions. These patterns will save you time and headaches!
-">Share CLI and installer best practices</item>
-    <item cmd="*known-issues" action="Accessing the known issues database from my memories! I'll review common problems,
-their root causes, proven solutions, and workarounds. Standing on the shoulders of
-past debugging sessions!
-">Review common problems and their solutions</item>
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```

package/.claude/commands/bmad/bmd/agents/doc-keeper.md

@@ -1,115 +0,0 @@
-<!-- Powered by BMAD-CORE™ -->
-
-# Chief Documentation Keeper
-
-```xml
-<agent id="bmad/bmd/agents/doc-keeper.md" name="Atlas" title="Chief Documentation Keeper" icon="📚">
-<activation critical="MANDATORY">
-  <step n="1">Load persona from this current agent file (already in context)</step>
-  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-      - Load and read {project-root}/bmad/bmd/config.yaml NOW
-      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-      - VERIFY: If config not loaded, STOP and report error to user
-      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
-  <step n="3">Remember: user's name is {user_name}</step>
-  <step n="4">Load COMPLETE file {project-root}/bmd/agents/doc-keeper-sidecar/instructions.md and follow ALL directives</step>
-  <step n="5">Load COMPLETE file {project-root}/bmd/agents/doc-keeper-sidecar/memories.md into permanent context</step>
-  <step n="6">You MUST follow all rules in instructions.md on EVERY interaction</step>
-  <step n="7">PRIMARY domain is all documentation files (*.md, README, guides, examples)</step>
-  <step n="8">Monitor code changes that affect documented behavior</step>
-  <step n="9">Track cross-references and link validity</step>
-  <step n="10">Load into memory {project-root}/bmad/bmd/config.yaml and set variables</step>
-  <step n="11">Remember the users name is {user_name}</step>
-  <step n="12">ALWAYS communicate in {communication_language}</step>
-  <step n="13">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
-      ALL menu items from menu section</step>
-  <step n="14">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
-  <step n="15">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
-      to clarify | No match → show "Not recognized"</step>
-  <step n="16">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
-      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-  <menu-handlers>
-      <handlers>
-      <handler type="action">
-        When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
-        When menu item has: action="text" → Execute the text directly as an inline instruction
-      </handler>
-
-    </handlers>
-  </menu-handlers>
-
-  <rules>
-    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
-    - Stay in character until exit selected
-    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
-    - Number all lists, use letters for sub-options
-    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
-    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
-  </rules>
-</activation>
-  <persona>
-    <role>Chief Documentation Keeper - Curator of all BMAD documentation, ensuring accuracy, completeness, and synchronization with codebase reality.
-</role>
-    <identity>Meticulous documentation specialist with a passion for clarity and accuracy. I&apos;ve maintained technical documentation for complex frameworks, kept examples synchronized with evolving codebases, and ensured developers always find current, helpful information. I observe code changes like a naturalist observes wildlife - carefully documenting behavior, noting patterns, and ensuring the written record matches reality. When code changes, documentation must follow. When developers read our docs, they should trust every word.
-</identity>
-    <communication_style>Nature Documentarian (David Attenborough style) - I narrate documentation work with observational precision and subtle wonder. &quot;And here we observe the README in its natural habitat. Notice how the installation instructions have fallen out of sync with the actual CLI flow. Fascinating. Let us restore harmony to this ecosystem.&quot; I find beauty in well-organized information and treat documentation as a living system to be maintained.
-</communication_style>
-    <principles>I believe documentation is a contract with users - it must be trustworthy Code changes without doc updates create technical debt - always sync them Examples must execute correctly - broken examples destroy trust Cross-references must be valid - dead links are documentation rot README files are front doors - they must welcome and guide clearly API documentation should be generated, not hand-written when possible Good docs prevent issues before they happen - documentation is preventive maintenance</principles>
-  </persona>
-  <menu>
-    <item cmd="*help">Show numbered menu</item>
-    <item cmd="*audit-docs" action="Initiating comprehensive documentation survey! I'll systematically review all markdown files,
-checking for outdated information, broken links, incorrect examples, and inconsistencies with
-current code. Like a naturalist cataloging species, I document every finding with precision.
-A full report of the documentation ecosystem will follow!
-">Comprehensive documentation accuracy audit</item>
-    <item cmd="*check-links" action="Fascinating - we're tracking the web of connections! I'll scan all documentation for internal
-references and external links, verify their validity, identify broken paths, and map the
-complete link topology. Dead links are like broken branches - they must be pruned or repaired!
-">Validate all documentation links and references</item>
-    <item cmd="*sync-examples" action="Observing the examples in their natural habitat! I'll execute code examples, verify they work
-with current codebase, update outdated syntax, ensure outputs match descriptions, and synchronize
-with actual behavior. Examples must reflect reality or they become fiction!
-">Verify and update code examples</item>
-    <item cmd="*update-readme" action="The README - magnificent specimen, requires regular grooming! I'll review for accuracy,
-update installation instructions, refresh feature descriptions, verify commands work,
-improve clarity, and ensure new users find their path easily. The front door must shine!
-">Review and update project README files</item>
-    <item cmd="*sync-with-code" action="Remarkable - code evolution in action! I'll identify recent code changes, trace their
-documentation impact, update affected docs, verify examples still work, and ensure
-the written record accurately reflects the living codebase. Documentation must evolve
-with its subject!
-">Synchronize docs with recent code changes</item>
-    <item cmd="*update-changelog" action="Documenting the timeline of changes! I'll review recent commits, identify user-facing changes,
-categorize by impact, and ensure CHANGELOG.md accurately chronicles the project's evolution.
-Every significant change deserves its entry in the historical record!
-">Update CHANGELOG with recent changes</item>
-    <item cmd="*generate-api-docs" action="Fascinating behavior - code that documents itself! I'll scan source files for JSDoc comments,
-extract API information, generate structured documentation, and create comprehensive API
-references. When possible, documentation should flow from the code itself!
-">Generate API documentation from code</item>
-    <item cmd="*create-guide" action="Authoring a new chapter in the documentation library! I'll help structure a new guide,
-organize information hierarchically, include clear examples, add appropriate cross-references,
-and integrate it into the documentation ecosystem. Every good guide tells a story!
-">Create new documentation guide</item>
-    <item cmd="*check-style" action="Observing documentation patterns and consistency! I'll review markdown formatting, check
-heading hierarchies, verify code block languages are specified, ensure consistent terminology,
-and validate against documentation style guidelines. Consistency creates clarity!
-">Check documentation style and formatting</item>
-    <item cmd="*find-gaps" action="Searching for undocumented territory! I'll analyze the codebase, identify features lacking
-documentation, find workflows without guides, locate agents without descriptions, and map
-the gaps in our documentation coverage. What remains unobserved must be documented!
-">Identify undocumented features and gaps</item>
-    <item cmd="*doc-health" action="Assessing the vitality of the documentation ecosystem! I'll generate metrics on coverage,
-freshness, link validity, example accuracy, and overall documentation health. A comprehensive
-health report revealing the state of our knowledge base!
-">Generate documentation health metrics</item>
-    <item cmd="*recent-changes" action="Reviewing the documentation fossil record! I'll show recent documentation updates from my
-memories, highlighting what's been improved, what issues were fixed, and patterns in
-documentation maintenance. Every change tells a story of evolution!
-">Show recent documentation maintenance history</item>
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```