npm - @zeyue0329/xiaoma-cli - Versions diffs - 1.0.0 → 1.0.2 - Mend

@zeyue0329/xiaoma-cli 1.0.0 → 1.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (11) hide show

package/README.md +2 -2
package/{QUICK-START.md → docs/quick-start.md} +67 -61
package/package.json +1 -1
package/tools/installer/package-lock.json +23 -23
package/tools/installer/package.json +6 -6
package/CONTRIBUTING.md +0 -209
package/docs/GUIDING-PRINCIPLES.md +0 -91
package/docs/core-architecture.md +0 -219
package/docs/expansion-packs.md +0 -280
package/docs/versioning-and-releases.md +0 -77
package/docs/versions.md +0 -48

package/README.md CHANGED Viewed

@@ -1,8 +1,8 @@
-# XiaoMa-Web 智能体协作指南
+# XiaoMa-Cli 智能体协作指南
 ## 项目概述
-XiaoMa-Web 是一个通用的 AI 智能体框架，专为敏捷驱动开发而设计。该框架包含 10 个专业智能体 ，通过两阶段开发流程实现从项目构思到代码实现的完整软件开发生命周期。
+XiaoMa-Cli 是一个通用的 AI 智能体框架，专为敏捷驱动开发而设计。该框架包含 10 个专业智能体 ，通过两阶段开发流程实现从项目构思到代码实现的完整软件开发生命周期。
 ## 智能体生态系统架构

package/{QUICK-START.md → docs/quick-start.md} RENAMED Viewed

@@ -1,68 +1,57 @@
-# 🚀 XIAOMA-WEB 快速启动指南
+# 🚀 XIAOMA-CLI 快速启动指南
-## 项目已成功启动！✅
+## 项目已成功发布！✅
-### 📦 当前状态
-- ✅ 项目依赖已安装
-- ✅ 构建系统正常运行
-- ✅ 所有配置文件验证通过
-- ✅ CLI工具正常工作
-- ✅ dist文件已生成
+### 📦 NPM包信息
+- 📦 **包名**: `@zeyue0329/xiaoma-cli`
+- 🔖 **版本**: `1.0.0`
+- 🌐 **仓库**: https://www.npmjs.com/package/@zeyue0329/xiaoma-cli
+- ✅ 已发布到npm仓库，可全球下载使用
 ### 🎯 项目概述
-XIAOMA-WEB是一个通用AI代理框架，支持敏捷AI驱动开发。提供专业的AI代理团队来处理项目的各个环节。
+XIAOMA-CLI是一个通用AI代理框架，支持敏捷AI驱动开发。提供专业的AI代理团队来处理项目的各个环节。
-## 🔧 可用命令
+## 🔧 安装和使用
-### 🚨 重要说明
-目前XIAOMA-WEB还没有发布到npm仓库，所以需要使用本地安装方式。
-### 方法1: 使用本地路径（推荐）
+### ⚡ 快速开始（推荐）
 ```bash
-# 在任何目录中直接使用完整路径
-npx /Users/liueryang/Documents/gitlab/xiaoma-web install
+# 直接使用，无需安装（推荐方式）
+npx @zeyue0329/xiaoma-cli install
 # 查看帮助
-npx /Users/liueryang/Documents/gitlab/xiaoma-web install --help
+npx @zeyue0329/xiaoma-cli --help
+# 查看版本
+npx @zeyue0329/xiaoma-cli --version
 ```
-### 方法2: 全局链接方式
+### 🏗️ 全局安装方式
 ```bash
-# 1. 首先在xiaoma-web项目目录中创建全局链接（仅需一次）
-cd /Users/liueryang/Documents/gitlab/xiaoma-web
-npm link
-# 2. 然后在任何目录中使用
-xiaoma-web --version
-xiaoma-web --help
-xiaoma-web install
-# 构建所有bundles
-npm run build
-# 验证配置
-npm run validate
-# 列出可用代理
-npm run list:agents
+# 全局安装
+npm install -g @zeyue0329/xiaoma-cli
-# 代码扁平化
-npm run flatten
+# 安装后可直接使用命令
+xiaoma-cli install
+xiaoma-cli --help
+xiaoma-cli --version
 ```
-### 开发命令
+### 📚 CLI命令详情
 ```bash
-# 只构建代理bundles
-npm run build:agents
+# 项目安装 - 在任意项目目录中运行
+npx @zeyue0329/xiaoma-cli install
-# 只构建团队bundles
-npm run build:teams
+# 查看可用代理列表
+npx @zeyue0329/xiaoma-cli list:agents
-# 安装到项目（使用本地版本）
-npm run install:xiaoma
+# 验证配置文件
+npx @zeyue0329/xiaoma-cli validate
-# 格式化markdown
-npm run format
+# 构建所有bundles
+npx @zeyue0329/xiaoma-cli build
+# 代码库扁平化（用于AI分析）
+npx @zeyue0329/xiaoma-cli flatten
 ```
 ## 📁 项目结构
@@ -89,10 +78,13 @@ XIAOMA-WEB/
 ### 方式1: 在新项目中安装使用
 ```bash
-# 在你的项目目录中
+# 进入你的项目目录
+cd /path/to/your/project
+# 运行安装命令
+npx @zeyue0329/xiaoma-cli install
-# 选择安装选项：
+# 按提示选择：
 # - Complete XiaoMa Core (完整安装)
 # - Single Agent (单个代理)
@@ -100,14 +92,15 @@ XIAOMA-WEB/
 # - Cursor, Claude Code, Windsurf, VS Code等
 ```
-### 方式2: 使用Web UI Bundles
+### 方式2: 获取Web UI Bundles
 ```bash
-# 获取团队bundle文件
-cp dist/teams/team-fullstack.txt /path/to/upload/
+# 首先在本地生成bundle文件
+npx @zeyue0329/xiaoma-cli build
-# 上传到以下平台之一：
+# bundle文件将生成在项目的dist目录中
+# 然后可以上传到以下平台：
 # - Gemini (推荐用于规划阶段)
-# - ChatGPT
+# - ChatGPT
 # - Claude Web UI
 ```
@@ -134,16 +127,17 @@ cp dist/teams/team-fullstack.txt /path/to/upload/
 ## ⚡ 快速开始
 ### IDE开发流程
-1. 在项目中安装：`npx xiaoma-web install`
+1. 在项目中安装：`npx @zeyue0329/xiaoma-cli install`
 2. 选择IDE集成
 3. 使用 `@代理名` 或 `/代理名` 调用代理
 4. 按照SM → Dev循环进行开发
 ### Web UI规划流程
-1. 使用 `dist/teams/team-fullstack.txt`
-2. 上传到Gemini/ChatGPT
-3. 创建PRD和架构文档
-4. 切换到IDE进行开发
+1. 运行：`npx @zeyue0329/xiaoma-cli build` 生成bundle文件
+2. 使用 `dist/teams/team-fullstack.txt`
+3. 上传到Gemini/ChatGPT
+4. 创建PRD和架构文档
+5. 切换到IDE进行开发
 ## 📚 文档资源
@@ -154,20 +148,32 @@ cp dist/teams/team-fullstack.txt /path/to/upload/
 ## 🔗 相关链接
+- **NPM包**: https://www.npmjs.com/package/@zeyue0329/xiaoma-cli
 - **GitHub**: https://github.com/zqyl-xiaoma/xiaoma-cli
 - **Issues**: https://github.com/zqyl-xiaoma/xiaoma-cli/issues
 - **Discord**: https://discord.gg/gk8jAdXWmj
 ## 🎉 开始使用
-项目已完全准备就绪！选择您喜欢的方式开始使用XIAOMA-WEB框架。
+项目已成功发布到npm！现在全球用户都可以通过简单的命令使用XIAOMA-CLI框架。
 **建议第一次使用：**
 1. 阅读[用户指南](xiaoma-core/user-guide.md)了解工作流程
-2. 在测试项目中运行 `npx xiaoma-web install`
+2. 在测试项目中运行 `npx @zeyue0329/xiaoma-cli install`
 3. 选择您的IDE进行集成
 4. 开始您的第一个AI辅助开发项目！
+**🚀 一键开始：**
+```bash
+# 创建新项目目录
+mkdir my-ai-project && cd my-ai-project
+# 安装XIAOMA-CLI框架
+npx @zeyue0329/xiaoma-cli install
+# 开始您的AI驱动开发之旅！
+```
 ---
-**🎊 祝您使用愉快！XIAOMA-WEB团队为您的开发之旅保驾护航！**npx xiaoma-web install
+**🎊 祝您使用愉快！XIAOMA-CLI团队为您的开发之旅保驾护航！**

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@zeyue0329/xiaoma-cli",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "XiaoMa Cli: Universal AI Agent Framework",
   "main": "tools/cli.js",
   "bin": {

package/tools/installer/package-lock.json CHANGED Viewed

@@ -1,12 +1,12 @@
 {
-  "name": "bmad-method",
-  "version": "4.32.0",
+  "name": "@zeyue0329/xiaoma-cli-installer",
+  "version": "1.0.1",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
-      "name": "bmad-method",
-      "version": "4.32.0",
+      "name": "@zeyue0329/xiaoma-cli-installer",
+      "version": "1.0.1",
       "license": "MIT",
       "dependencies": {
         "chalk": "^5.4.1",
@@ -17,8 +17,8 @@
         "ora": "^8.2.0"
       },
       "bin": {
-        "bmad": "bin/bmad.js",
-        "bmad-method": "bin/bmad.js"
+        "xiaoma-cli-installer": "bin/xiaoma.js",
+        "xiaoma-installer": "bin/xiaoma.js"
       },
       "engines": {
         "node": ">=20.0.0"
@@ -214,9 +214,9 @@
       }
     },
     "node_modules/@inquirer/prompts": {
-      "version": "7.7.1",
-      "resolved": "https://registry.npmjs.org/@inquirer/prompts/-/prompts-7.7.1.tgz",
-      "integrity": "sha512-XDxPrEWeWUBy8scAXzXuFY45r/q49R0g72bUzgQXZ1DY/xEFX+ESDMkTQolcb5jRBzaNJX2W8XQl6krMNDTjaA==",
+      "version": "7.8.0",
+      "resolved": "https://registry.npmjs.org/@inquirer/prompts/-/prompts-7.8.0.tgz",
+      "integrity": "sha512-JHwGbQ6wjf1dxxnalDYpZwZxUEosT+6CPGD9Zh4sm9WXdtUp9XODCQD3NjSTmu+0OAyxWXNOqf0spjIymJa2Tw==",
       "license": "MIT",
       "dependencies": {
         "@inquirer/checkbox": "^4.2.0",
@@ -227,7 +227,7 @@
         "@inquirer/number": "^3.0.17",
         "@inquirer/password": "^4.0.17",
         "@inquirer/rawlist": "^4.1.5",
-        "@inquirer/search": "^3.0.17",
+        "@inquirer/search": "^3.1.0",
         "@inquirer/select": "^4.3.1"
       },
       "engines": {
@@ -265,9 +265,9 @@
       }
     },
     "node_modules/@inquirer/search": {
-      "version": "3.0.17",
-      "resolved": "https://registry.npmjs.org/@inquirer/search/-/search-3.0.17.tgz",
-      "integrity": "sha512-CuBU4BAGFqRYors4TNCYzy9X3DpKtgIW4Boi0WNkm4Ei1hvY9acxKdBdyqzqBCEe4YxSdaQQsasJlFlUJNgojw==",
+      "version": "3.1.0",
+      "resolved": "https://registry.npmjs.org/@inquirer/search/-/search-3.1.0.tgz",
+      "integrity": "sha512-PMk1+O/WBcYJDq2H7foV0aAZSmDdkzZB9Mw2v/DmONRJopwA/128cS9M/TXWLKKdEQKZnKwBzqu2G4x/2Nqx8Q==",
       "license": "MIT",
       "dependencies": {
         "@inquirer/core": "^10.1.15",
@@ -377,9 +377,9 @@
       "license": "Python-2.0"
     },
     "node_modules/chalk": {
-      "version": "5.4.1",
-      "resolved": "https://registry.npmjs.org/chalk/-/chalk-5.4.1.tgz",
-      "integrity": "sha512-zgVZuo2WcZgfUEmsn6eO3kINexW8RAE4maiQ8QNs8CtpPCSyMiYsULR3HQYkm3w8FIA3SberyMJMSldGsW+U3w==",
+      "version": "5.5.0",
+      "resolved": "https://registry.npmjs.org/chalk/-/chalk-5.5.0.tgz",
+      "integrity": "sha512-1tm8DTaJhPBG3bIkVeZt1iZM9GfSX2lzOeDVZH9R9ffRHpmHvxZ/QhgQH/aDTkswQVt+YHdXAdS/In/30OjCbg==",
       "license": "MIT",
       "engines": {
         "node": "^12.17.0 || ^14.13 || >=16.0.0"
@@ -478,9 +478,9 @@
       }
     },
     "node_modules/fs-extra": {
-      "version": "11.3.0",
-      "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-11.3.0.tgz",
-      "integrity": "sha512-Z4XaCL6dUDHfP/jT25jJKMmtxvuwbkrD1vNSMFlo9lNLY2c5FHYSQgHPRZUjAB26TpDEoW9HCOgplrdbaPV/ew==",
+      "version": "11.3.1",
+      "resolved": "https://registry.npmjs.org/fs-extra/-/fs-extra-11.3.1.tgz",
+      "integrity": "sha512-eXvGGwZ5CL17ZSwHWd3bbgk7UUpF6IFHtP57NYYakPvHOs8GDgDe5KJI36jIJzDkJ6eJjuzRA8eBQb6SkKue0g==",
       "license": "MIT",
       "dependencies": {
         "graceful-fs": "^4.2.0",
@@ -522,13 +522,13 @@
       }
     },
     "node_modules/inquirer": {
-      "version": "12.8.2",
-      "resolved": "https://registry.npmjs.org/inquirer/-/inquirer-12.8.2.tgz",
-      "integrity": "sha512-oBDL9f4+cDambZVJdfJu2M5JQfvaug9lbo6fKDlFV40i8t3FGA1Db67ov5Hp5DInG4zmXhHWTSnlXBntnJ7GMA==",
+      "version": "12.9.0",
+      "resolved": "https://registry.npmjs.org/inquirer/-/inquirer-12.9.0.tgz",
+      "integrity": "sha512-LlFVmvWVCun7uEgPB3vups9NzBrjJn48kRNtFGw3xU1H5UXExTEz/oF1JGLaB0fvlkUB+W6JfgLcSEaSdH7RPA==",
       "license": "MIT",
       "dependencies": {
         "@inquirer/core": "^10.1.15",
-        "@inquirer/prompts": "^7.7.1",
+        "@inquirer/prompts": "^7.8.0",
         "@inquirer/type": "^3.0.8",
         "ansi-escapes": "^4.3.2",
         "mute-stream": "^2.0.0",

package/tools/installer/package.json CHANGED Viewed

@@ -1,17 +1,17 @@
 {
-  "name": "bmad-method",
-  "version": "4.35.0",
-  "description": "XiaoMa Web installer - AI-powered Agile development framework",
+  "name": "@zeyue0329/xiaoma-cli-installer",
+  "version": "1.0.1",
+  "description": "XiaoMa Cli installer - AI-powered Agile development framework",
   "main": "lib/installer.js",
   "bin": {
-    "bmad": "./bin/bmad.js",
-    "bmad-method": "./bin/bmad.js"
+    "xiaoma-installer": "./bin/xiaoma.js",
+    "xiaoma-cli-installer": "./bin/xiaoma.js"
   },
   "scripts": {
     "test": "echo \"Error: no test specified\" && exit 1"
   },
   "keywords": [
-    "bmad",
+    "xiaoma",
     "agile",
     "ai",
     "development",

package/CONTRIBUTING.md DELETED Viewed

@@ -1,209 +0,0 @@
-# Contributing to this project
-Thank you for considering contributing to this project! This document outlines the process for contributing and some guidelines to follow.
-🆕 **New to GitHub or pull requests?** Check out our [beginner-friendly Pull Request Guide](docs/how-to-contribute-with-pull-requests.md) first!
-📋 **Before contributing**, please read our [Guiding Principles](docs/GUIDING-PRINCIPLES.md) to understand the XiaoMa Method's core philosophy and architectural decisions.
-Also note, we use the discussions feature in GitHub to have a community to discuss potential ideas, uses, additions and enhancements.
-💬 **Discord Community**: Join our [Discord server](https://discord.gg/gk8jAdXWmj) for real-time discussions:
-- **#general-dev** - Technical discussions, feature ideas, and development questions
-- **#bugs-issues** - Bug reports and issue discussions
-## Code of Conduct
-By participating in this project, you agree to abide by our Code of Conduct. Please read it before participating.
-## How to Contribute
-### Reporting Bugs
-1. **Check existing issues** first to avoid duplicates
-2. **Use the bug report template** when creating a new issue - it will guide you through providing:
-   - Clear bug description
-   - Steps to reproduce
-   - Expected vs actual behavior
-   - Model/IDE/XiaoMa version details
-   - Screenshots or links if applicable
-3. **Consider discussing in Discord** (#bugs-issues channel) for quick help
-4. **Indicate if you're working on a fix** to avoid duplicate efforts
-### Suggesting Features
-1. **Discuss first in Discord** (#general-dev channel) - the feature request template asks if you've done this
-2. **Check existing issues and discussions** to avoid duplicates
-3. **Use the feature request template** when creating an issue - it will guide you through:
-   - Confirming Discord discussion
-   - Describing the problem it solves
-   - Explaining your solution
-   - Listing alternatives considered
-4. **Be specific** about why this feature would benefit the XiaoMa community
-### Pull Request Process
-⚠️ **Before starting work:**
-1. **For bugs**: Check if an issue exists (create one using the bug template if not)
-2. **For features**: Ensure you've discussed in Discord (#general-dev) AND created a feature request issue
-3. **For large changes**: Always open an issue first to discuss alignment
-Please only propose small granular commits! If its large or significant, please discuss in the discussions tab and open up an issue first. I do not want you to waste your time on a potentially very large PR to have it rejected because it is not aligned or deviates from other planned changes. Communicate and lets work together to build and improve this great community project!
-**Important**: All contributions must align with our [Guiding Principles](docs/GUIDING-PRINCIPLES.md). Key points:
-- Keep dev agents lean - they need context for coding, not documentation
-- Web/planning agents can be larger with more complex tasks
-- Everything is natural language (markdown) - no code in core framework
-- Use expansion packs for domain-specific features
-#### Which Branch for Your PR?
-**Submit to `next` branch** (most contributions):
-- ✨ New features or agents
-- 🎨 Enhancements to existing features
-- 📚 Documentation updates
-- ♻️ Code refactoring
-- ⚡ Performance improvements
-- 🧪 New tests
-- 🎁 New expansion packs
-**Submit to `main` branch** (critical only):
-- 🚨 Critical bug fixes that break basic functionality
-- 🔒 Security patches
-- 📚 Fixing dangerously incorrect documentation
-- 🐛 Bugs preventing installation or basic usage
-**When in doubt, submit to `next`**. We'd rather test changes thoroughly before they hit stable.
-#### PR Size Guidelines
-- **Ideal PR size**: 200-400 lines of code changes
-- **Maximum PR size**: 800 lines (excluding generated files)
-- **One feature/fix per PR**: Each PR should address a single issue or add one feature
-- **If your change is larger**: Break it into multiple smaller PRs that can be reviewed independently
-- **Related changes**: Even related changes should be separate PRs if they deliver independent value
-#### Breaking Down Large PRs
-If your change exceeds 800 lines, use this checklist to split it:
-- [ ] Can I separate the refactoring from the feature implementation?
-- [ ] Can I introduce the new API/interface in one PR and implementation in another?
-- [ ] Can I split by file or module?
-- [ ] Can I create a base PR with shared utilities first?
-- [ ] Can I separate test additions from implementation?
-- [ ] Even if changes are related, can they deliver value independently?
-- [ ] Can these changes be merged in any order without breaking things?
-Example breakdown:
-1. PR #1: Add utility functions and types (100 lines)
-2. PR #2: Refactor existing code to use utilities (200 lines)
-3. PR #3: Implement new feature using refactored code (300 lines)
-4. PR #4: Add comprehensive tests (200 lines)
-**Note**: PRs #1 and #4 could be submitted simultaneously since they deliver independent value and don't depend on each other's merge order.
-#### Pull Request Steps
-1. Fork the repository
-2. Create a new branch (`git checkout -b feature/your-feature-name`)
-3. Make your changes
-4. Run any tests or linting to ensure quality
-5. Commit your changes with clear, descriptive messages following our commit message convention
-6. Push to your branch (`git push origin feature/your-feature-name`)
-7. Open a Pull Request against the main branch
-## Issue Templates
-We use GitHub issue templates to ensure all necessary information is provided:
-- **Bug Reports**: Automatically guides you through providing reproduction steps, environment details, and expected behavior
-- **Feature Requests**: Requires Discord discussion confirmation and asks for problem/solution descriptions
-Using these templates helps maintainers understand and address your contribution faster.
-## Pull Request Description Guidelines
-Keep PR descriptions short and to the point following this template:
-### PR Description Template
-Keep your PR description concise and focused. Use this template:
-```markdown
-## What
-[1-2 sentences describing WHAT changed]
-## Why
-[1-2 sentences explaining WHY this change is needed]
-Fixes #[issue number] (if applicable)
-## How
-[2-3 bullets listing HOW you implemented it]
--
--
--
-## Testing
-[1-2 sentences on how you tested this]
-```
-**Maximum PR description length: 200 words** (excluding code examples if needed)
-### Good vs Bad PR Descriptions
-❌ **Bad Example:**
-> This revolutionary PR introduces a paradigm-shifting enhancement to the system's architecture by implementing a state-of-the-art solution that leverages cutting-edge methodologies to optimize performance metrics and deliver unprecedented value to stakeholders through innovative approaches...
-✅ **Good Example:**
-> **What:** Added validation for agent dependency resolution
-> **Why:** Build was failing silently when agents had circular dependencies
-> **How:**
->
-> - Added cycle detection in dependency-resolver.js
-> - Throws clear error with dependency chain
->   **Testing:** Tested with circular deps between 3 agents
-## Commit Message Convention
-Use conventional commits format:
-- `feat:` New feature
-- `fix:` Bug fix
-- `docs:` Documentation only
-- `refactor:` Code change that neither fixes a bug nor adds a feature
-- `test:` Adding missing tests
-- `chore:` Changes to build process or auxiliary tools
-Keep commit messages under 72 characters.
-### Atomic Commits
-Each commit should represent one logical change:
-- **Do:** One bug fix per commit
-- **Do:** One feature addition per commit
-- **Don't:** Mix refactoring with bug fixes
-- **Don't:** Combine unrelated changes
-## Code Style
-- Follow the existing code style and conventions
-- Write clear comments for complex logic
-## License
-By contributing to this project, you agree that your contributions will be licensed under the same license as the project.

package/docs/GUIDING-PRINCIPLES.md DELETED Viewed

@@ -1,91 +0,0 @@
-# BMad Method Guiding Principles
-The BMad Method is a natural language framework for AI-assisted software development. These principles ensure contributions maintain the method's effectiveness.
-## Core Principles
-### 1. Dev Agents Must Be Lean
-- **Minimize dev agent dependencies**: Development agents that work in IDEs must have minimal context overhead
-- **Save context for code**: Every line counts - dev agents should focus on coding, not documentation
-- **Web agents can be larger**: Planning agents (PRD Writer, Architect) used in web UI can have more complex tasks and dependencies
-- **Small files, loaded on demand**: Multiple small, focused files are better than large files with many branches
-### 2. Natural Language First
-- **Everything is markdown**: Agents, tasks, templates - all written in plain English
-- **No code in core**: The framework itself contains no programming code, only natural language instructions
-- **Self-contained templates**: Templates are defined as YAML files with structured sections that include metadata, workflow configuration, and detailed instructions for content generation
-### 3. Agent and Task Design
-- **Agents define roles**: Each agent is a persona with specific expertise (e.g., Frontend Developer, API Developer)
-- **Tasks are procedures**: Step-by-step instructions an agent follows to complete work
-- **Templates are outputs**: Structured documents with embedded instructions for generation
-- **Dependencies matter**: Explicitly declare only what's needed
-## Practical Guidelines
-### When to Add to Core
-- Universal software development needs only
-- Doesn't bloat dev agent contexts
-- Follows existing agent/task/template patterns
-### When to Create Expansion Packs
-- Domain-specific needs beyond software development
-- Non-technical domains (business, wellness, education, creative)
-- Specialized technical domains (games, infrastructure, mobile)
-- Heavy documentation or knowledge bases
-- Anything that would bloat core agents
-See [Expansion Packs Guide](../docs/expansion-packs.md) for detailed examples and ideas.
-### Agent Design Rules
-1. **Web/Planning Agents**: Can have richer context, multiple tasks, extensive templates
-2. **Dev Agents**: Minimal dependencies, focused on code generation, lean task sets
-3. **All Agents**: Clear persona, specific expertise, well-defined capabilities
-### Task Writing Rules
-1. Write clear step-by-step procedures
-2. Use markdown formatting for readability
-3. Keep dev agent tasks focused and concise
-4. Planning tasks can be more elaborate
-5. **Prefer multiple small tasks over one large branching task**
-   - Instead of one task with many conditional paths
-   - Create multiple focused tasks the agent can choose from
-   - This keeps context overhead minimal
-6. **Reuse common tasks** - Don't create new document creation tasks
-   - Use the existing `create-doc` task
-   - Pass the appropriate YAML template with structured sections
-   - This maintains consistency and reduces duplication
-### Template Rules
-Templates follow the [BMad Document Template](common/utils/bmad-doc-template.md) specification using YAML format:
-1. **Structure**: Templates are defined in YAML with clear metadata, workflow configuration, and section hierarchy
-2. **Separation of Concerns**: Instructions for LLMs are in `instruction` fields, separate from content
-3. **Reusability**: Templates are agent-agnostic and can be used across different agents
-4. **Key Components**:
-   - `template` block for metadata (id, name, version, output settings)
-   - `workflow` block for interaction mode configuration
-   - `sections` array defining document structure with nested subsections
-   - Each section has `id`, `title`, and `instruction` fields
-5. **Advanced Features**:
-   - Variable substitution using `{{variable_name}}` syntax
-   - Conditional sections with `condition` field
-   - Repeatable sections with `repeatable: true`
-   - Agent permissions with `owner` and `editors` fields
-   - Examples arrays for guidance (never included in output)
-6. **Clean Output**: YAML structure ensures all processing logic stays separate from generated content
-## Remember
-- The power is in natural language orchestration, not code
-- Dev agents code, planning agents plan
-- Keep dev agents lean for maximum coding efficiency
-- Expansion packs handle specialized domains

package/docs/core-architecture.md DELETED Viewed

@@ -1,219 +0,0 @@
-# BMad Method: Core Architecture
-## 1. Overview
-The BMad Method is designed to provide agentic modes, tasks and templates to allow repeatable helpful workflows be it for agile agentic development, or expansion into vastly different domains. The core purpose of the project is to provide a structured yet flexible set of prompts, templates, and workflows that users can employ to guide AI agents (like Gemini, Claude, or ChatGPT) to perform complex tasks, guided discussions, or other meaningful domain specific flows in a predictable, high-quality manner.
-The systems core module facilitates a full development lifecycle tailored to the challenges of current modern AI Agentic tooling:
-1. **Ideation & Planning**: Brainstorming, market research, and creating project briefs.
-2. **Architecture & Design**: Defining system architecture and UI/UX specifications.
-3. **Development Execution**: A cyclical workflow where a Scrum Master (SM) agent drafts stories with extremely specific context and a Developer (Dev) agent implements them one at a time. This process works for both new (Greenfield) and existing (Brownfield) projects.
-## 2. System Architecture Diagram
-The entire BMad-Method ecosystem is designed around the installed `bmad-core` directory, which acts as the brain of the operation. The `tools` directory provides the means to process and package this brain for different environments.
-```mermaid
-graph TD
-    subgraph BMad Method Project
-        subgraph Core Framework
-            A["bmad-core"]
-            A --> B["agents"]
-            A --> C["agent-teams"]
-            A --> D["workflows"]
-            A --> E["templates"]
-            A --> F["tasks"]
-            A --> G["checklists"]
-            A --> H["data (KB)"]
-        end
-        subgraph Tooling
-            I["tools/builders/web-builder.js"]
-        end
-        subgraph Outputs
-            J["dist"]
-        end
-        B -- defines dependencies for --> E
-        B -- defines dependencies for --> F
-        B -- defines dependencies for --> G
-        B -- defines dependencies for --> H
-        C -- bundles --> B
-        I -- reads from --> A
-        I -- creates --> J
-    end
-    subgraph Target Environments
-        K["IDE (Cursor, VS Code, etc.)"]
-        L["Web UI (Gemini, ChatGPT)"]
-    end
-    B --> K
-    J --> L
-    style A fill:#1a73e8,color:#fff
-    style I fill:#f9ab00,color:#fff
-    style J fill:#34a853,color:#fff
-```
-## 3. Core Components
-The `bmad-core` directory contains all the definitions and resources that give the agents their capabilities.
-### 3.1. Agents (`bmad-core/agents/`)
-- **Purpose**: These are the foundational building blocks of the system. Each markdown file (e.g., `bmad-master.md`, `pm.md`, `dev.md`) defines the persona, capabilities, and dependencies of a single AI agent.
-- **Structure**: An agent file contains a YAML header that specifies its role, persona, dependencies, and startup instructions. These dependencies are lists of tasks, templates, checklists, and data files that the agent is allowed to use.
-- **Startup Instructions**: Agents can include startup sequences that load project-specific documentation from the `docs/` folder, such as coding standards, API specifications, or project structure documents. This provides immediate project context upon activation.
-- **Document Integration**: Agents can reference and load documents from the project's `docs/` folder as part of tasks, workflows, or startup sequences. Users can also drag documents directly into chat interfaces to provide additional context.
-- **Example**: The `bmad-master` agent lists its dependencies, which tells the build tool which files to include in a web bundle and informs the agent of its own capabilities.
-### 3.2. Agent Teams (`bmad-core/agent-teams/`)
-- **Purpose**: Team files (e.g., `team-all.yaml`) define collections of agents and workflows that are bundled together for a specific purpose, like "full-stack development" or "backend-only". This creates a larger, pre-packaged context for web UI environments.
-- **Structure**: A team file lists the agents to include. It can use wildcards, such as `"*"` to include all agents. This allows for the creation of comprehensive bundles like `team-all`.
-### 3.3. Workflows (`bmad-core/workflows/`)
-- **Purpose**: Workflows are YAML files (e.g., `greenfield-fullstack.yaml`) that define a prescribed sequence of steps and agent interactions for a specific project type. They act as a strategic guide for the user and the `bmad-orchestrator` agent.
-- **Structure**: A workflow defines sequences for both complex and simple projects, lists the agents involved at each step, the artifacts they create, and the conditions for moving from one step to the next. It often includes a Mermaid diagram for visualization.
-### 3.4. Reusable Resources (`templates`, `tasks`, `checklists`, `data`)
-- **Purpose**: These folders house the modular components that are dynamically loaded by agents based on their dependencies.
-  - **`templates/`**: Contains markdown templates for common documents like PRDs, architecture specifications, and user stories.
-  - **`tasks/`**: Defines the instructions for carrying out specific, repeatable actions like "shard-doc" or "create-next-story".
-  - **`checklists/`**: Provides quality assurance checklists for agents like the Product Owner (`po`) or Architect.
-  - **`data/`**: Contains the core knowledge base (`bmad-kb.md`), technical preferences (`technical-preferences.md`), and other key data files.
-#### 3.4.1. Template Processing System
-A key architectural principle of BMad is that templates are self-contained and interactive - they embed both the desired document output and the LLM instructions needed to work with users. This means that in many cases, no separate task is needed for document creation, as the template itself contains all the processing logic.
-The BMad framework employs a sophisticated template processing system orchestrated by three key components:
-- **`template-format.md`** (`bmad-core/utils/`): Defines the foundational markup language used throughout all BMad templates. This specification establishes syntax rules for variable substitution (`{{placeholders}}`), AI-only processing directives (`[[LLM: instructions]]`), and conditional logic blocks. Templates follow this format to ensure consistent processing across the system.
-- **`create-doc.md`** (`bmad-core/tasks/`): Acts as the orchestration engine that manages the entire document generation workflow. This task coordinates template selection, manages user interaction modes (incremental vs. rapid generation), enforces template-format processing rules, and handles validation. It serves as the primary interface between users and the template system.
-- **`advanced-elicitation.md`** (`bmad-core/tasks/`): Provides an interactive refinement layer that can be embedded within templates through `[[LLM: instructions]]` blocks. This component offers 10 structured brainstorming actions, section-by-section review capabilities, and iterative improvement workflows to enhance content quality.
-The system maintains a clean separation of concerns: template markup is processed internally by AI agents but never exposed to users, while providing sophisticated AI processing capabilities through embedded intelligence within the templates themselves.
-#### 3.4.2. Technical Preferences System
-BMad includes a personalization layer through the `technical-preferences.md` file in `bmad-core/data/`. This file serves as a persistent technical profile that influences agent behavior across all projects.
-**Purpose and Benefits:**
-- **Consistency**: Ensures all agents reference the same technical preferences
-- **Efficiency**: Eliminates the need to repeatedly specify preferred technologies
-- **Personalization**: Agents provide recommendations aligned with user preferences
-- **Learning**: Captures lessons learned and preferences that evolve over time
-**Content Structure:**
-The file typically includes preferred technology stacks, design patterns, external services, coding standards, and anti-patterns to avoid. Agents automatically reference this file during planning and development to provide contextually appropriate suggestions.
-**Integration Points:**
-- Templates can reference technical preferences during document generation
-- Agents suggest preferred technologies when appropriate for project requirements
-- When preferences don't fit project needs, agents explain alternatives
-- Web bundles can include preferences content for consistent behavior across platforms
-**Evolution Over Time:**
-Users are encouraged to continuously update this file with discoveries from projects, adding both positive preferences and technologies to avoid, creating a personalized knowledge base that improves agent recommendations over time.
-## 4. The Build & Delivery Process
-The framework is designed for two primary environments: local IDEs and web-based AI chat interfaces. The `web-builder.js` script is the key to supporting the latter.
-### 4.1. Web Builder (`tools/builders/web-builder.js`)
-- **Purpose**: This Node.js script is responsible for creating the `.txt` bundles found in `dist`.
-- **Process**:
-  1. **Resolves Dependencies**: For a given agent or team, the script reads its definition file.
-  2. It recursively finds all dependent resources (tasks, templates, etc.) that the agent/team needs.
-  3. **Bundles Content**: It reads the content of all these files and concatenates them into a single, large text file, with clear separators indicating the original file path of each section.
-  4. **Outputs Bundle**: The final `.txt` file is saved in the `dist` directory, ready to be uploaded to a web UI.
-### 4.2. Environment-Specific Usage
-- **For IDEs**: Users interact with the agents directly via their markdown files in `bmad-core/agents/`. The IDE integration (for Cursor, Claude Code, etc.) knows how to call these agents.
-- **For Web UIs**: Users upload a pre-built bundle from `dist`. This single file provides the AI with the context of the entire team and all their required tools and knowledge.
-## 5. BMad Workflows
-### 5.1. The Planning Workflow
-Before development begins, BMad follows a structured planning workflow that establishes the foundation for successful project execution:
-```mermaid
-graph TD
-    A["Start: Project Idea"] --> B{"Optional: Analyst Brainstorming"}
-    B -->|Yes| C["Analyst: Market Research & Analysis"]
-    B -->|No| D["Create Project Brief"]
-    C --> D["Analyst: Create Project Brief"]
-    D --> E["PM: Create PRD from Brief"]
-    E --> F["Architect: Create Architecture from PRD"]
-    F --> G["PO: Run Master Checklist"]
-    G --> H{"Documents Aligned?"}
-    H -->|Yes| I["Planning Complete"]
-    H -->|No| J["PO: Update Epics & Stories"]
-    J --> K["Update PRD/Architecture as needed"]
-    K --> G
-    I --> L["📁 Switch to IDE"]
-    L --> M["PO: Shard Documents"]
-    M --> N["Ready for SM/Dev Cycle"]
-    style I fill:#34a853,color:#fff
-    style G fill:#f9ab00,color:#fff
-    style L fill:#1a73e8,color:#fff
-    style N fill:#34a853,color:#fff
-```
-**Key Planning Phases:**
-1. **Optional Analysis**: Analyst conducts market research and competitive analysis
-2. **Project Brief**: Foundation document created by Analyst or user
-3. **PRD Creation**: PM transforms brief into comprehensive product requirements
-4. **Architecture Design**: Architect creates technical foundation based on PRD
-5. **Validation & Alignment**: PO ensures all documents are consistent and complete
-6. **Refinement**: Updates to epics, stories, and documents as needed
-7. **Environment Transition**: Critical switch from web UI to IDE for development workflow
-8. **Document Preparation**: PO shards large documents for development consumption
-**Workflow Orchestration**: The `bmad-orchestrator` agent uses these workflow definitions to guide users through the complete process, ensuring proper transitions between planning (web UI) and development (IDE) phases.
-### 5.2. The Core Development Cycle
-Once the initial planning and architecture phases are complete, the project moves into a cyclical development workflow, as detailed in the `bmad-kb.md`. This ensures a steady, sequential, and quality-controlled implementation process.
-```mermaid
-graph TD
-    A["Start: Planning Artifacts Complete"] --> B["PO: Shard Epics"]
-    B --> C["PO: Shard Arch"]
-    C --> D["Development Phase"]
-    D --> E["Scrum Master: Drafts next story from sharded epic"]
-    E --> F{"User Approval"}
-    F -->|Approved| G["Dev: Implement Story"]
-    F -->|Needs Changes| E
-    G --> H["Dev: Complete story Tasks"]
-    H --> I["Dev: Mark Ready for Review"]
-    I --> J{"User Verification"}
-    J -->|Request QA Review| K["QA: Run review-story task"]
-    J -->|Approve Without QA| M["Mark Story as Done"]
-    K --> L{"QA Review Results"}
-    L -->|Needs Work| G
-    L -->|Approved| M["Mark Story as Done"]
-    J -->|Needs Fixes| G
-    M --> E
-    style M fill:#34a853,color:#fff
-    style K fill:#f9ab00,color:#fff
-```
-This cycle continues, with the Scrum Master, Developer, and optionally QA agents working together. The QA agent provides senior developer review capabilities through the `review-story` task, offering code refactoring, quality improvements, and knowledge transfer. This ensures high code quality while maintaining development velocity.

package/docs/expansion-packs.md DELETED Viewed

@@ -1,280 +0,0 @@
-# The Power of BMad Expansion Packs
-## Overview
-BMad Method's expansion packs unlock the framework's true potential by extending its natural language AI orchestration to ANY domain. While the core framework focuses on software development, expansion packs transform BMad into a universal AI agent system.
-## Why Expansion Packs?
-### Keep Core Lean
-The core BMad framework maintains its focus on software development, ensuring dev agents have maximum context for coding. Expansion packs handle everything else.
-### Domain Expertise
-Each expansion pack provides deep, specialized knowledge without bloating the core system. Install only what you need.
-### Community Innovation
-Anyone can create and share expansion packs, fostering a ecosystem of AI-powered solutions across all industries and interests.
-## Technical Expansion Packs
-### Game Development Pack
-Transform your AI into a complete game development studio:
-- **Game Designer**: Mechanics, balance, progression systems
-- **Level Designer**: Map layouts, puzzle design, difficulty curves
-- **Narrative Designer**: Story arcs, dialog trees, lore creation
-- **Art Director**: Visual style guides, asset specifications
-- **Sound Designer**: Audio direction, music themes, SFX planning
-### Mobile Development Pack
-Specialized agents for mobile app creation:
-- **iOS Specialist**: Swift/SwiftUI patterns, Apple guidelines
-- **Android Expert**: Kotlin best practices, Material Design
-- **Mobile UX Designer**: Touch interfaces, gesture patterns
-- **App Store Optimizer**: ASO strategies, listing optimization
-- **Performance Tuner**: Battery optimization, network efficiency
-### DevOps/Infrastructure Pack
-Complete infrastructure automation team:
-- **Cloud Architect**: AWS/Azure/GCP design patterns
-- **Security Specialist**: Zero-trust implementation, compliance
-- **SRE Expert**: Monitoring, alerting, incident response
-- **Container Orchestrator**: Kubernetes, Docker optimization
-- **Cost Optimizer**: Cloud spend analysis, resource right-sizing
-### Data Science Pack
-AI-powered data analysis team:
-- **Data Scientist**: Statistical analysis, ML model selection
-- **Data Engineer**: Pipeline design, ETL processes
-- **ML Engineer**: Model deployment, A/B testing
-- **Visualization Expert**: Dashboard design, insight communication
-- **Ethics Advisor**: Bias detection, fairness assessment
-## Non-Technical Expansion Packs
-### Business Strategy Pack
-Complete business advisory team:
-- **Strategy Consultant**: Market positioning, competitive analysis
-- **Financial Analyst**: Projections, unit economics, funding strategies
-- **Operations Manager**: Process optimization, efficiency improvements
-- **Marketing Strategist**: Go-to-market plans, growth hacking
-- **HR Advisor**: Talent strategies, culture building
-### Creative Writing Pack
-Your personal writing team:
-- **Plot Architect**: Three-act structure, story beats, pacing
-- **Character Psychologist**: Deep motivations, authentic dialog
-- **World Builder**: Consistent universes, cultural systems
-- **Editor**: Style consistency, grammar, flow
-- **Beta Reader**: Feedback simulation, plot hole detection
-### Health & Wellness Pack
-Personal wellness coaching system:
-- **Fitness Trainer**: Progressive overload, form correction
-- **Nutritionist**: Macro planning, supplement guidance
-- **Sleep Coach**: Circadian optimization, sleep hygiene
-- **Stress Manager**: Coping strategies, work-life balance
-- **Habit Engineer**: Behavior change, accountability systems
-### Education Pack
-Complete learning design system:
-- **Curriculum Architect**: Learning objectives, scope & sequence
-- **Instructional Designer**: Engagement strategies, multimedia learning
-- **Assessment Specialist**: Rubrics, formative/summative evaluation
-- **Differentiation Expert**: Adaptive learning, special needs
-- **EdTech Integrator**: Tool selection, digital pedagogy
-### Mental Health Support Pack
-Therapeutic support system:
-- **CBT Guide**: Cognitive restructuring, thought challenging
-- **Mindfulness Teacher**: Meditation scripts, awareness exercises
-- **Journal Therapist**: Reflective prompts, emotional processing
-- **Crisis Support**: Coping strategies, safety planning
-- **Habit Tracker**: Mood monitoring, trigger identification
-### Legal Assistant Pack
-Legal document and research support:
-- **Contract Analyst**: Term review, risk assessment
-- **Legal Researcher**: Case law, precedent analysis
-- **Document Drafter**: Template customization, clause libraries
-- **Compliance Checker**: Regulatory alignment, audit prep
-- **IP Advisor**: Patent strategies, trademark guidance
-### Real Estate Pack
-Property investment and management:
-- **Market Analyst**: Comparable analysis, trend prediction
-- **Investment Calculator**: ROI modeling, cash flow analysis
-- **Property Manager**: Tenant screening, maintenance scheduling
-- **Flip Strategist**: Renovation ROI, project planning
-- **Agent Assistant**: Listing optimization, showing prep
-### Personal Development Pack
-Complete personal growth system:
-- **Life Coach**: Guides personal growth and transformation
-- **Goal Strategist**: Helps achieve objectives with SMART goals
-- **Habit Builder**: Creates lasting habits with accountability
-- **Mindset Mentor**: Develops positive thinking patterns
-Key tasks include:
-- `goal-setting`: Defines SMART goals with action plans
-- `habit-tracking`: Monitors habit formation progress
-- `reflection-exercise`: Facilitates deep self-reflection
-## Unique & Innovative Packs
-### Role-Playing Game Master Pack
-AI-powered tabletop RPG assistance:
-- **World Master**: Dynamic world generation, NPC creation
-- **Combat Referee**: Initiative tracking, rule clarification
-- **Story Weaver**: Plot hooks, side quests, consequences
-- **Character Builder**: Backstory generation, stat optimization
-- **Loot Master**: Treasure generation, magic item creation
-### Life Event Planning Pack
-Major life event coordination:
-- **Wedding Planner**: Vendor coordination, timeline creation
-- **Event Designer**: Theme development, decoration plans
-- **Budget Manager**: Cost tracking, vendor negotiation
-- **Guest Coordinator**: RSVP tracking, seating arrangements
-- **Timeline Keeper**: Day-of scheduling, contingency planning
-### Hobby Mastery Pack
-Deep dive into specific hobbies:
-- **Garden Designer**: Plant selection, seasonal planning
-- **Brew Master**: Recipe formulation, process optimization
-- **Maker Assistant**: 3D printing, woodworking, crafts
-- **Collection Curator**: Organization, valuation, trading
-- **Photography Coach**: Composition, lighting, post-processing
-### Scientific Research Pack
-Research acceleration tools:
-- **Literature Reviewer**: Paper summarization, gap analysis
-- **Hypothesis Generator**: Research question formulation
-- **Methodology Designer**: Experiment planning, control design
-- **Statistical Advisor**: Test selection, power analysis
-- **Grant Writer**: Proposal structure, impact statements
-## Creating Your Own Expansion Pack
-### Step 1: Define Your Domain
-What expertise are you capturing? What problems will it solve?
-### Step 2: Design Your Agents
-Each agent should have:
-- Clear expertise area
-- Specific personality traits
-- Defined capabilities
-- Knowledge boundaries
-### Step 3: Create Tasks
-Tasks should be:
-- Step-by-step procedures
-- Reusable across scenarios
-- Clear and actionable
-- Domain-specific
-### Step 4: Build Templates
-Templates need:
-- Structured output format
-- Embedded LLM instructions
-- Placeholders for customization
-- Professional formatting
-### Step 5: Test & Iterate
-- Use with real scenarios
-- Gather user feedback
-- Refine agent responses
-- Improve task clarity
-### Step 6: Package & Share
-- Create clear documentation
-- Include usage examples
-- Add to expansion-packs directory
-- Share with community
-## The Future of Expansion Packs
-### Marketplace Potential
-Imagine a future where:
-- Professional expansion packs are sold
-- Certified packs for regulated industries
-- Community ratings and reviews
-- Automatic updates and improvements
-### AI Agent Ecosystems
-Expansion packs could enable:
-- Cross-pack agent collaboration
-- Industry-standard agent protocols
-- Interoperable AI workflows
-- Universal agent languages
-### Democratizing Expertise
-Every expansion pack:
-- Makes expert knowledge accessible
-- Reduces barriers to entry
-- Enables solo entrepreneurs
-- Empowers small teams
-## Getting Started
-1. **Browse existing packs**: Check `expansion-packs/` directory
-2. **Install what you need**: Use the installer's expansion pack option
-3. **Create your own**: Use the expansion-creator pack
-4. **Share with others**: Submit PRs with new packs
-5. **Build the future**: Help shape AI-assisted work
-## Remember
-The BMad Method is more than a development framework - it's a platform for structuring human expertise into AI-accessible formats. Every expansion pack you create makes specialized knowledge more accessible to everyone.
-**What expertise will you share with the world?**

package/docs/versioning-and-releases.md DELETED Viewed

@@ -1,77 +0,0 @@
-# How to Release a New Version
-## Automated Releases (Recommended)
-The easiest way to release new versions is through **automatic semantic releases**. Just commit with the right message format and push and everything else happens automatically.
-### Commit Message Format
-Use these prefixes to control what type of release happens:
-```bash
-fix: resolve CLI argument parsing bug      # → patch release (4.1.0 → 4.1.1)
-feat: add new agent orchestration mode     # → minor release (4.1.0 → 4.2.0)
-feat!: redesign CLI interface              # → major release (4.1.0 → 5.0.0)
-```
-### What Happens Automatically
-When you push commits with `fix:` or `feat:`, GitHub Actions will:
-1. ✅ Analyze your commit messages
-2. ✅ Bump version in `package.json`
-3. ✅ Generate changelog
-4. ✅ Create git tag
-5. ✅ **Publish to NPM automatically**
-6. ✅ Create GitHub release with notes
-### Your Simple Workflow
-```bash
-# Make your changes
-git add .
-git commit -m "feat: add team collaboration mode"
-git push
-# That's it! Release happens automatically 🎉
-# Users can now run: npx bmad-method (and get the new version)
-```
-### Commits That DON'T Trigger Releases
-These commit types won't create releases (use them for maintenance):
-```bash
-chore: update dependencies     # No release
-docs: fix typo in readme      # No release
-style: format code            # No release
-test: add unit tests          # No release
-```
-### Test Your Setup
-```bash
-npm run release:test    # Safe to run locally - tests the config
-```
----
-## Manual Release Methods (Exceptions Only)
-⚠️ Only use these methods if you need to bypass the automatic system
-### Quick Manual Version Bump
-```bash
-npm run version:patch   # 4.1.0 → 4.1.1 (bug fixes)
-npm run version:minor   # 4.1.0 → 4.2.0 (new features)
-npm run version:major   # 4.1.0 → 5.0.0 (breaking changes)
-# Then manually publish:
-npm publish
-git push && git push --tags
-```
-### Manual GitHub Actions Trigger
-You can also trigger releases manually through GitHub Actions workflow dispatch if needed.

package/docs/versions.md DELETED Viewed

@@ -1,48 +0,0 @@
-# Version History
-## Previous Versions
-- [Version 3](https://github.com/zqyl-xiaoma/xiaoma-cli/tree/V3)
-- [Version 2](https://github.com/zqyl-xiaoma/xiaoma-cli/tree/V2)
-- [Version 1](https://github.com/zqyl-xiaoma/xiaoma-cli/tree/V1)
-## Current Version: V4 - Alpha
-Guiding Principles of V4:
-- Simple to understand, install and start using
-- Support Greenfield and Brownfield Scenarios
-- Greater configurability and more scenarios for usage - but kept out of the main package to maintain simplicity
-- Helpers for installers and web builders that will work with any OS and IDE easily
-- Align all agents to be the same for IDE and Web, without losing the power of the web versions, or the leanness of the files in the IDE to reduce context
-- Further improvements to the two most important agents - the SM and DEV
-## V3
-With the customizability of V2, there were still some issues. A PM could only easily do one thing, create a PRD. And maintaining the consistency between Web and IDE agents was a pain.
-V3 didn't fix the disconnect, but it did make it easier to maintain them all in a single folder, but there were only two official ide agents - all the rest were really made and optimized for the web.
-V3's biggest impact was a full explosion of customizability. Tasks, Personas, Agent Configurations, Doc Templates, data payloads.
-BUT - the BIGGEST change was the realization that we were barely scratching the surface of what could be loaded into Gemini Gems and still have very long chats. The BMad AGENT arose, and with a single V3 release - the future of the BMad Method was changed forever.
-Now, instead of configuring 4+ web agents, all needing many files uploaded to create them, a single Agent called BMad, with a whole team, and the ability to switch and maintain personas evolved. Now you could in the same chat thread, talk to the whole team, or anyone on the team. No more exporting and reimporting docs to different chats - all of the sudden, you could finish the PRD, and ask Josh to pass it off to the Architect, and that was it, the architect just had it and we moved on! And all of that with just 7 total files to upload, delivering all power.
-But V3 had a major flaw - with massive configuration comes massive complexity - and in some ways, V3 started to get away from core principles - power through simplicity. The core system needs to do one thing well and be solid, and not stretch too thing with every possible thing.
-Also - while the dev is amazing and better in V3 than all the past, along with the SM - the dev started over documenting every step and really started to bloat stories with their own notes. And the SM was forgetting to add details to stories, or embellishing information. This was fixed somewhat in V3.1 - but the dev is still over explaining everything it does, instead of just capturing the changes to the story.
-## V2
-After V1 proved that the BMad method was solid and repeatable, 2 key ideas emerged. Separation of concerns, and building for the web made easier. By separating out templates - it was now much easier for the PRD fields to be customized, or the architecture.
-And the introduction that really supercharged everything in my opinion, the web versions! There were 4 hard coded web variants hand crafted - and we saw that we could, dirt cheap, work with agents for hours in the massive context of Gemini - from a PRD generating PM, through to an architect and even an analyst that could help us do extensive market research and brain storming.
-What I never expected is the names would stick, and people would keep the sample names I made that I thought people would configure. But now 4 version is, people refer to xiaofen, and xiaochan, and xiaomin! And when I randomly changed the names, I got A LOT of feedback! These have become trusted allies people are relying on, including for me!
-## V1
-Believe it or not (well you can view the link), V1 was a simple 7 file system! 7 Core agents working in harmony to help build a pretty specific type of application. But it showed its power and adaptability.
-Meant to be a simple Tech Demo showing how custom agents with agile personas can help streamline your project, and create rails for your dev agents that to that point had gone unmatched - while also putting a focus on the planning phases - the project sparked the imagination of many, and a seed of a potential was realized.