@zeyue0329/xiaoma-cli 1.6.4 → 1.7.0

package/docs/reference/agents.md

@@ -1,28 +0,0 @@
----
-title: Agents
-description: Default BMM agents with their skill IDs, menu triggers, and primary workflows
-sidebar:
-  order: 2
----
-
-## Default Agents
-
-This page lists the default BMM (Agile suite) agents that install with XiaoMa Method, along with their skill IDs, menu triggers, and primary workflows. Each agent is invoked as a skill.
-
-## Notes
-
-- Each agent is available as a skill, generated by the installer. The skill ID (e.g., `xiaoma-dev`) is used to invoke the agent.
-- Triggers are the short menu codes (e.g., `CP`) and fuzzy matches shown in each agent menu.
-- QA (Quinn) is the lightweight test automation agent in BMM. The full Test Architect (TEA) lives in its own module.
-
-| Agent                       | Skill ID             | Triggers                           | Primary workflows                                                                                   |
-| --------------------------- | -------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------- |
-| Analyst (Mary)              | `xiaoma-analyst`       | `BP`, `RS`, `CB`, `DP`             | Brainstorm Project, Research, Create Brief, Document Project                                        |
-| Product Manager (John)      | `xiaoma-pm`            | `CP`, `VP`, `EP`, `CE`, `IR`, `CC` | Create/Validate/Edit PRD, Create Epics and Stories, Implementation Readiness, Correct Course        |
-| Architect (Winston)         | `xiaoma-architect`     | `CA`, `IR`                         | Create Architecture, Implementation Readiness                                                       |
-| Scrum Master (Bob)          | `xiaoma-sm`            | `SP`, `CS`, `ER`, `CC`             | Sprint Planning, Create Story, Epic Retrospective, Correct Course                                   |
-| Developer (Amelia)          | `xiaoma-dev`           | `DS`, `CR`                         | Dev Story, Code Review                                                                              |
-| QA Engineer (Quinn)         | `xiaoma-qa`            | `QA`                               | Automate (generate tests for existing features)                                                     |
-| Quick Flow Solo Dev (Barry) | `xiaoma-master`        | `QS`, `QD`, `CR`                   | Quick Spec, Quick Dev, Code Review                                                                  |
-| UX Designer (Sally)         | `xiaoma-ux-designer`   | `CU`                               | Create UX Design                                                                                    |
-| Technical Writer (Paige)    | `xiaoma-tech-writer`   | `DP`, `WD`, `US`, `MG`, `VD`, `EC` | Document Project, Write Document, Update Standards, Mermaid Generate, Validate Doc, Explain Concept |

package/docs/reference/commands.md

@@ -1,145 +0,0 @@
----
-title: Skills
-description: Reference for XiaoMa skills — what they are, how they work, and where to find them.
-sidebar:
-  order: 3
----
-
-Skills are pre-built prompts that load agents, run workflows, or execute tasks inside your IDE. The XiaoMa installer generates them from your installed modules at install time. If you later add, remove, or change modules, re-run the installer to keep skills in sync (see [Troubleshooting](#troubleshooting)).
-
-## Skills vs. Agent Menu Triggers
-
-XiaoMa offers two ways to start work, and they serve different purposes.
-
-| Mechanism | How you invoke it | What happens |
-| --- | --- | --- |
-| **Skill** | Type the skill name (e.g. `xiaoma-help`) in your IDE | Directly loads an agent, runs a workflow, or executes a task |
-| **Agent menu trigger** | Load an agent first, then type a short code (e.g. `DS`) | The agent interprets the code and starts the matching workflow while staying in character |
-
-Agent menu triggers require an active agent session. Use skills when you know which workflow you want. Use triggers when you are already working with an agent and want to switch tasks without leaving the conversation.
-
-## How Skills Are Generated
-
-When you run `npx xiaoma-cli install`, the installer reads the manifests for every selected module and writes one skill per agent, workflow, task, and tool. Each skill is a directory containing a `SKILL.md` file that instructs the AI to load the corresponding source file and follow its instructions.
-
-The installer uses templates for each skill type:
-
-| Skill type | What the generated file does |
-| --- | --- |
-| **Agent launcher** | Loads the agent persona file, activates its menu, and stays in character |
-| **Workflow skill** | Loads the workflow config and follows its steps |
-| **Task skill** | Loads a standalone task file and follows its instructions |
-| **Tool skill** | Loads a standalone tool file and follows its instructions |
-
-:::note[Re-running the installer]
-If you add or remove modules, run the installer again. It regenerates all skill files to match your current module selection.
-:::
-
-## Where Skill Files Live
-
-The installer writes skill files into an IDE-specific directory inside your project. The exact path depends on which IDE you selected during installation.
-
-| IDE / CLI | Skills directory |
-| --- | --- |
-| Claude Code | `.claude/skills/` |
-| Cursor | `.cursor/skills/` |
-| Windsurf | `.windsurf/skills/` |
-| Other IDEs | See the installer output for the target path |
-
-Each skill is a directory containing a `SKILL.md` file. For example, a Claude Code installation looks like:
-
-```text
-.claude/skills/
-├── xiaoma-help/
-│   └── SKILL.md
-├── xiaoma-create-prd/
-│   └── SKILL.md
-├── xiaoma-dev/
-│   └── SKILL.md
-└── ...
-```
-
-The directory name determines the skill name in your IDE. For example, the directory `xiaoma-dev/` registers the skill `xiaoma-dev`.
-
-## How to Discover Your Skills
-
-Type the skill name in your IDE to invoke it. Some platforms require you to enable skills in settings before they appear.
-
-Run `xiaoma-help` for context-aware guidance on your next step.
-
-:::tip[Quick discovery]
-The generated skill directories in your project are the canonical list. Open them in your file explorer to see every skill with its description.
-:::
-
-## Skill Categories
-
-### Agent Skills
-
-Agent skills load a specialized AI persona with a defined role, communication style, and menu of workflows. Once loaded, the agent stays in character and responds to menu triggers.
-
-| Example skill | Agent | Role |
-| --- | --- | --- |
-| `xiaoma-dev` | Amelia (Developer) | Implements stories with strict adherence to specs |
-| `xiaoma-pm` | John (Product Manager) | Creates and validates PRDs |
-| `xiaoma-architect` | Winston (Architect) | Designs system architecture |
-| `xiaoma-sm` | Bob (Scrum Master) | Manages sprints and stories |
-
-See [Agents](./agents.md) for the full list of default agents and their triggers.
-
-### Workflow Skills
-
-Workflow skills run a structured, multi-step process without loading an agent persona first. They load a workflow configuration and follow its steps.
-
-| Example skill | Purpose |
-| --- | --- |
-| `xiaoma-create-prd` | Create a Product Requirements Document |
-| `xiaoma-create-architecture` | Design system architecture |
-| `xiaoma-create-epics-and-stories` | Create epics and stories |
-| `xiaoma-dev-story` | Implement a story |
-| `xiaoma-code-review` | Run a code review |
-| `xiaoma-quick-spec` | Define an ad-hoc change (Quick Flow) |
-
-See [Workflow Map](./workflow-map.md) for the complete workflow reference organized by phase.
-
-### Task and Tool Skills
-
-Tasks and tools are standalone operations that do not require an agent or workflow context.
-
-#### XiaoMa-Help: Your Intelligent Guide
-
-**`xiaoma-help`** is your primary interface for discovering what to do next. It's not just a lookup tool — it's an intelligent assistant that:
-
-- **Inspects your project** to see what's already been done
-- **Understands natural language queries** — ask questions in plain English
-- **Varies by installed modules** — shows options based on what you have
-- **Auto-invokes after workflows** — every workflow ends with clear next steps
-- **Recommends the first required task** — no guessing where to start
-
-**Examples:**
-
-```
-xiaoma-help
-xiaoma-help I have a SaaS idea and know all the features. Where do I start?
-xiaoma-help What are my options for UX design?
-xiaoma-help I'm stuck on the PRD workflow
-```
-
-#### Other Tasks and Tools
-
-| Example skill | Purpose |
-| --- | --- |
-| `xiaoma-shard-doc` | Split a large markdown file into smaller sections |
-| `xiaoma-index-docs` | Index project documentation |
-| `xiaoma-editorial-review-prose` | Review document prose quality |
-
-## Naming Convention
-
-All skills use the `xiaoma-` prefix followed by a descriptive name (e.g., `xiaoma-dev`, `xiaoma-create-prd`, `xiaoma-help`). See [Modules](./modules.md) for available modules.
-
-## Troubleshooting
-
-**Skills not appearing after install.** Some platforms require skills to be explicitly enabled in settings. Check your IDE's documentation or ask your AI assistant how to enable skills. You may also need to restart your IDE or reload the window.
-
-**Expected skills are missing.** The installer only generates skills for modules you selected. Run `npx xiaoma-cli install` again and verify your module selection. Check that the skill files exist in the expected directory.
-
-**Skills from a removed module still appear.** The installer does not delete old skill files automatically. Remove the stale directories from your IDE's skills directory, or delete the entire skills directory and re-run the installer for a clean set.

package/docs/reference/modules.md

@@ -1,76 +0,0 @@
----
-title: Official Modules
-description: Add-on modules for building custom agents, creative intelligence, game development, and testing
-sidebar:
-  order: 4
----
-
-XiaoMa extends through official modules that you select during installation. These add-on modules provide specialized agents, workflows, and tasks for specific domains beyond the built-in core and BMM (Agile suite).
-
-:::tip[Installing Modules]
-Run `npx xiaoma-cli install` and select the modules you want. The installer handles downloading, configuration, and IDE integration automatically.
-:::
-
-## XiaoMa Builder
-
-Create custom agents, workflows, and domain-specific modules with guided assistance. XiaoMa Builder is the meta-module for extending the framework itself.
-
-- **Code:** `bmb`
-- **npm:** [`xiaoma-builder`](https://www.npmjs.com/package/xiaoma-builder)
-- **GitHub:** [xiaoma-code-org/xiaoma-builder](https://github.com/xiaoma-code-org/xiaoma-builder)
-
-**Provides:**
-
-- Agent Builder -- create specialized AI agents with custom expertise and tool access
-- Workflow Builder -- design structured processes with steps and decision points
-- Module Builder -- package agents and workflows into shareable, publishable modules
-- Interactive setup with YAML configuration and npm publishing support
-
-## Creative Intelligence Suite
-
-AI-powered tools for structured creativity, ideation, and innovation during early-stage development. The suite provides multiple agents that facilitate brainstorming, design thinking, and problem-solving using proven frameworks.
-
-- **Code:** `cis`
-- **npm:** [`xiaoma-creative-intelligence-suite`](https://www.npmjs.com/package/xiaoma-creative-intelligence-suite)
-- **GitHub:** [xiaoma-code-org/xiaoma-module-creative-intelligence-suite](https://github.com/xiaoma-code-org/xiaoma-module-creative-intelligence-suite)
-
-**Provides:**
-
-- Innovation Strategist, Design Thinking Coach, and Brainstorming Coach agents
-- Problem Solver and Creative Problem Solver for systematic and lateral thinking
-- Storyteller and Presentation Master for narratives and pitches
-- Ideation frameworks including SCAMPER, Reverse Brainstorming, and problem reframing
-
-## Game Dev Studio
-
-Structured game development workflows adapted for Unity, Unreal, Godot, and custom engines. Supports rapid prototyping through Quick Flow and full-scale production with epic-driven sprints.
-
-- **Code:** `gds`
-- **npm:** [`xiaoma-game-dev-studio`](https://www.npmjs.com/package/xiaoma-game-dev-studio)
-- **GitHub:** [xiaoma-code-org/xiaoma-module-game-dev-studio](https://github.com/xiaoma-code-org/xiaoma-module-game-dev-studio)
-
-**Provides:**
-
-- Game Design Document (GDD) generation workflow
-- Quick Dev mode for rapid prototyping
-- Narrative design support for characters, dialogue, and world-building
-- Coverage for 21+ game types with engine-specific architecture guidance
-
-## Test Architect (TEA)
-
-Enterprise-grade test strategy, automation guidance, and release gate decisions through an expert agent and nine structured workflows. TEA goes well beyond the built-in QA agent with risk-based prioritization and requirements traceability.
-
-- **Code:** `tea`
-- **npm:** [`xiaoma-cli-test-architecture-enterprise`](https://www.npmjs.com/package/xiaoma-cli-test-architecture-enterprise)
-- **GitHub:** [xiaoma-code-org/xiaoma-cli-test-architecture-enterprise](https://github.com/xiaoma-code-org/xiaoma-cli-test-architecture-enterprise)
-
-**Provides:**
-
-- Murat agent (Master Test Architect and Quality Advisor)
-- Workflows for test design, ATDD, automation, test review, and traceability
-- NFR assessment, CI setup, and framework scaffolding
-- P0-P3 prioritization with optional Playwright Utils and MCP integrations
-
-## Community Modules
-
-Community modules and a module marketplace are coming. Check the [XiaoMa GitHub organization](https://github.com/xiaoma-code-org) for updates.

package/docs/reference/testing.md

@@ -1,106 +0,0 @@
----
-title: Testing Options
-description: Comparing the built-in QA agent (Quinn) with the Test Architect (TEA) module for test automation.
-sidebar:
-  order: 5
----
-
-XiaoMa provides two testing paths: a built-in QA agent for fast test generation and an installable Test Architect module for enterprise-grade test strategy.
-
-## Which Should You Use?
-
-| Factor | Quinn (Built-in QA) | TEA Module |
-| --- | --- | --- |
-| **Best for** | Small-medium projects, quick coverage | Large projects, regulated or complex domains |
-| **Setup** | Nothing to install -- included in BMM | Install separately via `npx xiaoma-cli install` |
-| **Approach** | Generate tests fast, iterate later | Plan first, then generate with traceability |
-| **Test types** | API and E2E tests | API, E2E, ATDD, NFR, and more |
-| **Strategy** | Happy path + critical edge cases | Risk-based prioritization (P0-P3) |
-| **Workflow count** | 1 (Automate) | 9 (design, ATDD, automate, review, trace, and others) |
-
-:::tip[Start with Quinn]
-Most projects should start with Quinn. If you later need test strategy, quality gates, or requirements traceability, install TEA alongside it.
-:::
-
-## Built-in QA Agent (Quinn)
-
-Quinn is the built-in QA agent in the BMM (Agile suite) module. It generates working tests quickly using your project's existing test framework -- no configuration or additional installation required.
-
-**Trigger:** `QA` or `xiaoma-qa-generate-e2e-tests`
-
-### What Quinn Does
-
-Quinn runs a single workflow (Automate) that walks through five steps:
-
-1. **Detect test framework** -- scans `package.json` and existing test files for your framework (Jest, Vitest, Playwright, Cypress, or any standard runner). If none exists, analyzes the project stack and suggests one.
-2. **Identify features** -- asks what to test or auto-discovers features in the codebase.
-3. **Generate API tests** -- covers status codes, response structure, happy path, and 1-2 error cases.
-4. **Generate E2E tests** -- covers user workflows with semantic locators and visible-outcome assertions.
-5. **Run and verify** -- executes the generated tests and fixes failures immediately.
-
-Quinn produces a test summary saved to your project's implementation artifacts folder.
-
-### Test Patterns
-
-Generated tests follow a "simple and maintainable" philosophy:
-
-- **Standard framework APIs only** -- no external utilities or custom abstractions
-- **Semantic locators** for UI tests (roles, labels, text rather than CSS selectors)
-- **Independent tests** with no order dependencies
-- **No hardcoded waits or sleeps**
-- **Clear descriptions** that read as feature documentation
-
-:::note[Scope]
-Quinn generates tests only. For code review and story validation, use the Code Review workflow (`CR`) instead.
-:::
-
-### When to Use Quinn
-
-- Quick test coverage for a new or existing feature
-- Beginner-friendly test automation without advanced setup
-- Standard test patterns that any developer can read and maintain
-- Small-medium projects where comprehensive test strategy is unnecessary
-
-## Test Architect (TEA) Module
-
-TEA is a standalone module that provides an expert agent (Murat) and nine structured workflows for enterprise-grade testing. It goes beyond test generation into test strategy, risk-based planning, quality gates, and requirements traceability.
-
-- **Documentation:** [TEA Module Docs](https://xiaoma-code-org.github.io/xiaoma-cli-test-architecture-enterprise/)
-- **Install:** `npx xiaoma-cli install` and select the TEA module
-- **npm:** [`xiaoma-cli-test-architecture-enterprise`](https://www.npmjs.com/package/xiaoma-cli-test-architecture-enterprise)
-
-### What TEA Provides
-
-| Workflow | Purpose |
-| --- | --- |
-| Test Design | Create a comprehensive test strategy tied to requirements |
-| ATDD | Acceptance-test-driven development with stakeholder criteria |
-| Automate | Generate tests with advanced patterns and utilities |
-| Test Review | Validate test quality and coverage against strategy |
-| Traceability | Map tests back to requirements for audit and compliance |
-| NFR Assessment | Evaluate non-functional requirements (performance, security) |
-| CI Setup | Configure test execution in continuous integration pipelines |
-| Framework Scaffolding | Set up test infrastructure and project structure |
-| Release Gate | Make data-driven go/no-go release decisions |
-
-TEA also supports P0-P3 risk-based prioritization and optional integrations with Playwright Utils and MCP tooling.
-
-### When to Use TEA
-
-- Projects that require requirements traceability or compliance documentation
-- Teams that need risk-based test prioritization across many features
-- Enterprise environments with formal quality gates before release
-- Complex domains where test strategy must be planned before tests are written
-- Projects that have outgrown Quinn's single-workflow approach
-
-## How Testing Fits into Workflows
-
-Quinn's Automate workflow appears in Phase 4 (Implementation) of the XiaoMa Method workflow map. A typical sequence:
-
-1. Implement a story with the Dev workflow (`DS`)
-2. Generate tests with Quinn (`QA`) or TEA's Automate workflow
-3. Validate implementation with Code Review (`CR`)
-
-Quinn works directly from source code without loading planning documents (PRD, architecture). TEA workflows can integrate with upstream planning artifacts for traceability.
-
-For more on where testing fits in the overall process, see the [Workflow Map](./workflow-map.md).

package/docs/reference/workflow-map.md

@@ -1,89 +0,0 @@
----
-title: "Workflow Map"
-description: Visual reference for XiaoMa Method workflow phases and outputs
-sidebar:
-  order: 1
----
-
-The XiaoMa Method (BMM) is a module in the XiaoMa Ecosystem, targeted at following the best practices of context engineering and planning. AI agents work best with clear, structured context. The BMM system builds that context progressively across 4 distinct phases - each phase, and multiple workflows optionally within each phase, produce documents that inform the next, so agents always know what to build and why.
-
-The rationale and concepts come from agile methodologies that have been used across the industry with great success as a mental framework.
-
-If at any time you are unsure what to do, the `xiaoma-help` skill will help you stay on track or know what to do next. You can always refer to this for reference also - but `xiaoma-help` is fully interactive and much quicker if you have already installed the XiaoMa Method. Additionally, if you are using different modules that have extended the XiaoMa Method or added other complementary non-extension modules - `xiaoma-help` evolves to know all that is available to give you the best in-the-moment advice.
-
-Final important note: Every workflow below can be run directly with your tool of choice via skill or by loading an agent first and using the entry from the agents menu.
-
-<iframe src="/workflow-map-diagram.html" title="XiaoMa Method Workflow Map Diagram" width="100%" height="100%" style="border-radius: 8px; border: 1px solid #334155; min-height: 900px;"></iframe>
-
-<p style="font-size: 0.8rem; text-align: right; margin-top: -0.5rem; margin-bottom: 1rem;">
-  <a href="/workflow-map-diagram.html" target="_blank" rel="noopener noreferrer">Open diagram in new tab ↗</a>
-</p>
-
-## Phase 1: Analysis (Optional)
-
-Explore the problem space and validate ideas before committing to planning.
-
-| Workflow                        | Purpose                                                                    | Produces                  |
-| ------------------------------- | -------------------------------------------------------------------------- | ------------------------- |
-| `xiaoma-brainstorming`            | Brainstorm Project Ideas with guided facilitation of a brainstorming coach | `brainstorming-report.md` |
-| `xiaoma-domain-research`, `xiaoma-market-research`, `xiaoma-technical-research` | Validate market, technical, or domain assumptions | Research findings |
-| `xiaoma-create-product-brief`     | Capture strategic vision                                                   | `product-brief.md`        |
-
-## Phase 2: Planning
-
-Define what to build and for whom.
-
-| Workflow                    | Purpose                                  | Produces     |
-| --------------------------- | ---------------------------------------- | ------------ |
-| `xiaoma-create-prd`    | Define requirements (FRs/NFRs)           | `PRD.md`     |
-| `xiaoma-create-ux-design`  | Design user experience (when UX matters) | `ux-spec.md` |
-
-## Phase 3: Solutioning
-
-Decide how to build it and break work into stories.
-
-| Workflow                                  | Purpose                                    | Produces                    |
-| ----------------------------------------- | ------------------------------------------ | --------------------------- |
-| `xiaoma-create-architecture`            | Make technical decisions explicit          | `architecture.md` with ADRs |
-| `xiaoma-create-epics-and-stories`       | Break requirements into implementable work | Epic files with stories     |
-| `xiaoma-check-implementation-readiness` | Gate check before implementation           | PASS/CONCERNS/FAIL decision |
-
-## Phase 4: Implementation
-
-Build it, one story at a time. Coming soon, full phase 4 automation!
-
-| Workflow                   | Purpose                                                                  | Produces                         |
-| -------------------------- | ------------------------------------------------------------------------ | -------------------------------- |
-| `xiaoma-sprint-planning` | Initialize tracking (once per project to sequence the dev cycle)         | `sprint-status.yaml`          |
-| `xiaoma-create-story`    | Prepare next story for implementation                                    | `story-[slug].md`             |
-| `xiaoma-dev-story`       | Implement the story                                                      | Working code + tests          |
-| `xiaoma-code-review`     | Validate implementation quality                                          | Approved or changes requested |
-| `xiaoma-correct-course`  | Handle significant mid-sprint changes                                    | Updated plan or re-routing    |
-| `xiaoma-sprint-status`   | Track sprint progress and story status                                   | Sprint status update          |
-| `xiaoma-retrospective`   | Review after epic completion                                             | Lessons learned               |
-
-## Quick Flow (Parallel Track)
-
-Skip phases 1-3 for small, well-understood work.
-
-| Workflow              | Purpose                                    | Produces                                      |
-| --------------------- | ------------------------------------------ | --------------------------------------------- |
-| `xiaoma-quick-spec` | Define an ad-hoc change                    | `tech-spec.md` (story file for small changes) |
-| `xiaoma-quick-dev`  | Implement from spec or direct instructions | Working code + tests                          |
-
-## Context Management
-
-Each document becomes context for the next phase. The PRD tells the architect what constraints matter. The architecture tells the dev agent which patterns to follow. Story files give focused, complete context for implementation. Without this structure, agents make inconsistent decisions.
-
-### Project Context
-
-:::tip[Recommended]
-Create `project-context.md` to ensure AI agents follow your project's rules and preferences. This file works like a constitution for your project — it guides implementation decisions across all workflows. This optional file can be generated at the end of Architecture Creation, or in an existing project it can be generated also to capture whats important to keep aligned with current conventions.
-:::
-
-**How to create it:**
-
-- **Manually** — Create `_xiaoma-output/project-context.md` with your technology stack and implementation rules
-- **Generate it** — Run `xiaoma-generate-project-context` to auto-generate from your architecture or codebase
-
-[**Learn more about project-context.md**](../explanation/project-context.md)

package/docs/roadmap.mdx

@@ -1,136 +0,0 @@
----
-title: Roadmap
-description: What's next for BMad - Features, improvements, and community contributions
----
-
-# The BMad Method: Public Roadmap
-
-The BMad Method, BMad Method Module (BMM), and BMad Builder (BMB) are evolving. Here's what we're working on and what's coming next.
-
-<div class="roadmap-container">
-
-  <h2 class="roadmap-section-title">In Progress</h2>
-
-  <div class="roadmap-future">
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">🧩</span>
-      <h4>Universal Skills Architecture</h4>
-      <p>One skill, any platform. Write once, run everywhere.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">🏗️</span>
-      <h4>BMad Builder v1</h4>
-      <p>Craft production-ready AI agents and workflows with evals, teams, and graceful degradation built in.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">🧠</span>
-      <h4>Project Context System</h4>
-      <p>Your AI actually understands your project. Framework-aware context that evolves with your codebase.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">📦</span>
-      <h4>Centralized Skills</h4>
-      <p>Install once, use everywhere. Share skills across projects without the file clutter.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">🔄</span>
-      <h4>Adaptive Skills</h4>
-      <p>Skills that know your tool. Optimized variants for Claude, Codex, Kimi, and OpenCode, plus many more.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">📝</span>
-      <h4>BMad Team Pros Blog</h4>
-      <p>Guides, articles and insights from the team. Launching soon.</p>
-    </div>
-  </div>
-
-  <h2 class="roadmap-section-title">Getting Started</h2>
-
-  <div class="roadmap-future">
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">🏪</span>
-      <h4>Skill Marketplace</h4>
-      <p>Discover, install, and update community-built skills. One curl command away from superpowers.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">🎨</span>
-      <h4>Workflow Customization</h4>
-      <p>Make it yours. Integrate Jira, Linear, custom outputs your workflow, your rules.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">🚀</span>
-      <h4>Phase 1-3 Optimization</h4>
-      <p>Lightning-fast planning with sub-agent context gathering. YOLO mode meets guided excellence.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">🌐</span>
-      <h4>Enterprise Ready</h4>
-      <p>SSO, audit logs, team workspaces. All the boring stuff that makes companies say yes.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">💎</span>
-      <h4>Community Modules Explosion</h4>
-      <p>Entertainment, security, therapy, roleplay and much more. Expand the BMad Method platform.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">⚡</span>
-      <h4>Dev Loop Automation</h4>
-      <p>Optional autopilot for development. Let AI handle the flow while keeping quality sky-high.</p>
-    </div>
-  </div>
-
-  <h2 class="roadmap-section-title">Community and Team</h2>
-
-  <div class="roadmap-future">
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">🎙️</span>
-      <h4>The BMad Method Podcast</h4>
-      <p>Conversations about AI-native development. Launching March 1, 2026!</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">🎓</span>
-      <h4>The BMad Method Master Class</h4>
-      <p>Go from user to expert. Deep dives into every phase, every workflow, every secret.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">🏗️</span>
-      <h4>The BMad Builder Master Class</h4>
-      <p>Build your own agents. Advanced techniques for when you are ready to create, not just use.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">⚡</span>
-      <h4>BMad Prototype First</h4>
-      <p>Idea to working prototype in one session. Craft your dream app like a work of art.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">🌴</span>
-      <h4>BMad BALM!</h4>
-      <p>Life management for the AI-native. Tasks, habits, goals your AI copilot for everything.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">🖥️</span>
-      <h4>Official UI</h4>
-      <p>A beautiful interface for the entire BMad ecosystem. CLI power, GUI polish.</p>
-    </div>
-    <div class="roadmap-future-card">
-      <span class="roadmap-emoji">🔒</span>
-      <h4>BMad in a Box</h4>
-      <p>Self-hosted, air-gapped, enterprise-grade. Your AI assistant, your infrastructure, your control.</p>
-    </div>
-  </div>
-
-  <div style="text-align: center; margin-top: 3rem; padding: 2rem; background: var(--color-bg-card); border-radius: 12px; border: 1px solid var(--color-border);">
-    <h3 style="margin: 0 0 1rem;">Want to Contribute?</h3>
-    <p style="color: var(--slate-color-400); margin: 0;">
-      This is only a partial list of what's planned. The BMad Open Source team welcomes contributors!{" "}<br />
-      <a href="https://github.com/bmad-code-org/BMAD-METHOD" style="color: var(--color-in-progress);">Join us on GitHub</a> to help shape the future of AI-driven development.
-    </p>
-    <p style="color: var(--slate-color-400); margin: 1.5rem 0 0;">
-      Love what we're building? We appreciate both one-time and monthly{" "}<a href="https://buymeacoffee.com/bmad" style="color: var(--color-in-progress);">support</a>.
-    </p>
-    <p style="color: var(--slate-color-400); margin: 1rem 0 0;">
-      For corporate sponsorship, partnership inquiries, speaking engagements, training, or media enquiries:{" "}
-      <a href="mailto:contact@bmadcode.com" style="color: var(--color-in-progress);">contact@bmadcode.com</a>
-    </p>
-  </div>
-</div>