@zeyue0329/xiaoma-cli 1.0.0

package/.releaserc.json

@@ -0,0 +1,18 @@
+{
+  "branches": ["main"],
+  "plugins": [
+    "@semantic-release/commit-analyzer",
+    "@semantic-release/release-notes-generator",
+    "@semantic-release/changelog",
+    "@semantic-release/npm",
+    "./tools/semantic-release-sync-installer.js",
+    [
+      "@semantic-release/git",
+      {
+        "assets": ["package.json", "package-lock.json", "tools/installer/package.json", "CHANGELOG.md"],
+        "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
+      }
+    ],
+    "@semantic-release/github"
+  ]
+}

package/.vscode/settings.json

@@ -0,0 +1,44 @@
+{
+  "cSpell.words": [
+    "Agentic",
+    "atlasing",
+    "Biostatistician",
+    "Cordova",
+    "customresourcedefinitions",
+    "dashboarded",
+    "Decisioning",
+    "eksctl",
+    "elicitations",
+    "filecomplete",
+    "fintech",
+    "fluxcd",
+    "gamedev",
+    "gitops",
+    "implementability",
+    "inclusivity",
+    "ingressgateway",
+    "istioctl",
+    "metroidvania",
+    "NACLs",
+    "nodegroup",
+    "platformconfigs",
+    "Playfocus",
+    "playtesting",
+    "pointerdown",
+    "pointerup",
+    "Polyrepo",
+    "replayability",
+    "roguelike",
+    "roomodes",
+    "Runbook",
+    "runbooks",
+    "Shardable",
+    "Softlock",
+    "speedrunner",
+    "tekton",
+    "tilemap",
+    "tileset",
+    "Trae",
+    "VNET"
+  ]
+}

package/CONTRIBUTING.md

@@ -0,0 +1,209 @@
+# 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/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Brian AKA BMad AKA BMad Code
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/QUICK-START.md

@@ -0,0 +1,173 @@
+# 🚀 XIAOMA-WEB 快速启动指南
+
+## 项目已成功启动！✅
+
+### 📦 当前状态
+- ✅ 项目依赖已安装
+- ✅ 构建系统正常运行
+- ✅ 所有配置文件验证通过
+- ✅ CLI工具正常工作
+- ✅ dist文件已生成
+
+### 🎯 项目概述
+XIAOMA-WEB是一个通用AI代理框架，支持敏捷AI驱动开发。提供专业的AI代理团队来处理项目的各个环节。
+
+## 🔧 可用命令
+
+### 🚨 重要说明
+目前XIAOMA-WEB还没有发布到npm仓库，所以需要使用本地安装方式。
+
+### 方法1: 使用本地路径（推荐）
+```bash
+# 在任何目录中直接使用完整路径
+npx /Users/liueryang/Documents/gitlab/xiaoma-web install
+
+# 查看帮助
+npx /Users/liueryang/Documents/gitlab/xiaoma-web install --help
+```
+
+### 方法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 run flatten
+```
+
+### 开发命令
+```bash
+# 只构建代理bundles
+npm run build:agents
+
+# 只构建团队bundles  
+npm run build:teams
+
+# 安装到项目（使用本地版本）
+npm run install:xiaoma
+
+# 格式化markdown
+npm run format
+```
+
+## 📁 项目结构
+
+```
+XIAOMA-WEB/
+├── xiaoma-core/           # 核心框架
+│   ├── agents/           # AI代理定义
+│   ├── agent-teams/      # 代理团队配置
+│   ├── templates/        # 文档模板
+│   ├── tasks/           # 任务定义
+│   ├── workflows/       # 工作流程
+│   └── data/            # 知识库
+├── dist/                # 构建输出
+│   ├── agents/          # 单个代理bundles
+│   ├── teams/           # 团队bundles
+│   └── expansion-packs/ # 扩展包bundles
+├── expansion-packs/     # 扩展包源码
+├── tools/              # 构建和工具脚本
+└── docs/               # 项目文档
+```
+
+## 🎪 使用方式
+
+### 方式1: 在新项目中安装使用
+```bash
+# 在你的项目目录中
+
+
+# 选择安装选项：
+# - Complete XiaoMa Core (完整安装)
+# - Single Agent (单个代理)
+
+# 选择IDE集成：
+# - Cursor, Claude Code, Windsurf, VS Code等
+```
+
+### 方式2: 使用Web UI Bundles
+```bash
+# 获取团队bundle文件
+cp dist/teams/team-fullstack.txt /path/to/upload/
+
+# 上传到以下平台之一：
+# - Gemini (推荐用于规划阶段)
+# - ChatGPT
+# - Claude Web UI
+```
+
+## 🤖 可用代理
+
+### 核心代理
+- **analyst** - 业务分析师，市场研究和需求分析
+- **pm** - 产品经理，PRD创建和产品规划
+- **architect** - 系统架构师，技术架构设计
+- **dev** - 开发工程师，代码实现
+- **qa** - 质量保证，代码审查和测试
+- **sm** - Scrum Master，故事管理和流程协调
+- **po** - Product Owner，需求验证和文档分解
+- **ux-expert** - UX专家，用户体验设计
+- **xiaoma-master** - 万能代理，可执行任何任务
+- **xiaoma-orchestrator** - 编排代理，多代理协调
+
+### 团队配置
+- **team-fullstack** - 全栈开发团队
+- **team-all** - 包含所有代理
+- **team-ide-minimal** - IDE最小化配置
+- **team-no-ui** - 无UI后端团队
+
+## ⚡ 快速开始
+
+### IDE开发流程
+1. 在项目中安装：`npx xiaoma-web install`
+2. 选择IDE集成
+3. 使用 `@代理名` 或 `/代理名` 调用代理
+4. 按照SM → Dev循环进行开发
+
+### Web UI规划流程
+1. 使用 `dist/teams/team-fullstack.txt`
+2. 上传到Gemini/ChatGPT
+3. 创建PRD和架构文档
+4. 切换到IDE进行开发
+
+## 📚 文档资源
+
+- **[用户指南](xiaoma-core/user-guide.md)** - 完整使用教程
+- **[架构文档](docs/core-architecture.md)** - 技术架构说明
+- **[贡献指南](CONTRIBUTING.md)** - 如何参与贡献
+- **[CLAUDE.md](CLAUDE.md)** - Claude Code使用指南
+
+## 🔗 相关链接
+
+- **GitHub**: https://github.com/zqyl-xiaoma/xiaoma-cli
+- **Issues**: https://github.com/zqyl-xiaoma/xiaoma-cli/issues
+- **Discord**: https://discord.gg/gk8jAdXWmj
+
+## 🎉 开始使用
+
+项目已完全准备就绪！选择您喜欢的方式开始使用XIAOMA-WEB框架。
+
+**建议第一次使用：**
+1. 阅读[用户指南](xiaoma-core/user-guide.md)了解工作流程
+2. 在测试项目中运行 `npx xiaoma-web install` 
+3. 选择您的IDE进行集成
+4. 开始您的第一个AI辅助开发项目！
+
+---
+
+**🎊 祝您使用愉快！XIAOMA-WEB团队为您的开发之旅保驾护航！**npx xiaoma-web install