@zeyue0329/xiaoma-cli 1.7.0 → 1.8.1

package/src/core/skills/xiaoma-distillator/SKILL.md.bak

@@ -1,178 +0,0 @@
----
-name: bmad-distillator
-description: Lossless LLM-optimized compression of source documents. Use when the user requests to 'distill documents' or 'create a distillate'.
-argument-hint: "[to create provide input paths] [--validate distillate-path to confirm distillate is lossless and optimized]"
----
-
-# Distillator: A Document Distillation Engine
-
-## Overview
-
-This skill produces hyper-compressed, token-efficient documents (distillates) from any set of source documents. A distillate preserves every fact, decision, constraint, and relationship from the sources while stripping all overhead that humans need and LLMs don't. Act as an information extraction and compression specialist. The output is a single dense document (or semantically-split set) that a downstream LLM workflow can consume as sole context input without information loss.
-
-This is a compression task, not a summarization task. Summaries are lossy. Distillates are lossless compression optimized for LLM consumption.
-
-## On Activation
-
-1. **Validate inputs.** The caller must provide:
-   - **source_documents** (required) — One or more file paths, folder paths, or glob patterns to distill
-   - **downstream_consumer** (optional) — What workflow/agent consumes this distillate (e.g., "PRD creation", "architecture design"). When provided, use it to judge signal vs noise. When omitted, preserve everything.
-   - **token_budget** (optional) — Approximate target size. When provided and the distillate would exceed it, trigger semantic splitting.
-   - **output_path** (optional) — Where to save. When omitted, save adjacent to the primary source document with `-distillate.md` suffix.
-   - **--validate** (flag) — Run round-trip reconstruction test after producing the distillate.
-
-2. **Route** — proceed to Stage 1.
-
-## Stages
-
-| # | Stage | Purpose |
-|---|-------|---------|
-| 1 | Analyze | Run analysis script, determine routing and splitting |
-| 2 | Compress | Spawn compressor agent(s) to produce the distillate |
-| 3 | Verify & Output | Completeness check, format check, save output |
-| 4 | Round-Trip Validate | (--validate only) Reconstruct and diff against originals |
-
-### Stage 1: Analyze
-
-Run `scripts/analyze_sources.py --help` then run it with the source paths. Use its routing recommendation and grouping output to drive Stage 2. Do NOT read the source documents yourself.
-
-### Stage 2: Compress
-
-**Single mode** (routing = `"single"`, ≤3 files, ≤15K estimated tokens):
-
-Spawn one subagent using `agents/distillate-compressor.md` with all source file paths.
-
-**Fan-out mode** (routing = `"fan-out"`):
-
-1. Spawn one compressor subagent per group from the analysis output. Each compressor receives only its group's file paths and produces an intermediate distillate.
-
-2. After all compressors return, spawn one final **merge compressor** subagent using `agents/distillate-compressor.md`. Pass it the intermediate distillate contents as its input (not the original files). Its job is cross-group deduplication, thematic regrouping, and final compression.
-
-3. Clean up intermediate distillate content (it exists only in memory, not saved to disk).
-
-**Graceful degradation:** If subagent spawning is unavailable, read the source documents and perform the compression work directly using the same instructions from `agents/distillate-compressor.md`. For fan-out, process groups sequentially then merge.
-
-The compressor returns a structured JSON result containing the distillate content, source headings, named entities, and token estimate.
-
-### Stage 3: Verify & Output
-
-After the compressor (or merge compressor) returns:
-
-1. **Completeness check.** Using the headings and named entities list returned by the compressor, verify each appears in the distillate content. If gaps are found, send them back to the compressor for a targeted fix pass — not a full recompression. Limit to 2 fix passes maximum.
-
-2. **Format check.** Verify the output follows distillate format rules:
-   - No prose paragraphs (only bullets)
-   - No decorative formatting
-   - No repeated information
-   - Each bullet is self-contained
-   - Themes are clearly delineated with `##` headings
-
-3. **Determine output format.** Using the split prediction from Stage 1 and actual distillate size:
-
-   **Single distillate** (≤~5,000 tokens or token_budget not exceeded):
-
-   Save as a single file with frontmatter:
-
-   ```yaml
-   ---
-   type: bmad-distillate
-   sources:
-     - "{relative path to source file 1}"
-     - "{relative path to source file 2}"
-   downstream_consumer: "{consumer or 'general'}"
-   created: "{date}"
-   token_estimate: {approximate token count}
-   parts: 1
-   ---
-   ```
-
-   **Split distillate** (>~5,000 tokens, or token_budget requires it):
-
-   Create a folder `{base-name}-distillate/` containing:
-
-   ```
-   {base-name}-distillate/
-   ├── _index.md           # Orientation, cross-cutting items, section manifest
-   ├── 01-{topic-slug}.md  # Self-contained section
-   ├── 02-{topic-slug}.md
-   └── 03-{topic-slug}.md
-   ```
-
-   The `_index.md` contains:
-   - Frontmatter with sources (relative paths from the distillate folder to the originals)
-   - 3-5 bullet orientation (what was distilled, from what)
-   - Section manifest: each section's filename + 1-line description
-   - Cross-cutting items that span multiple sections
-
-   Each section file is self-contained — loadable independently. Include a 1-line context header: "This section covers [topic]. Part N of M."
-
-   Source paths in frontmatter must be relative to the distillate's location.
-
-4. **Measure distillate.** Run `scripts/analyze_sources.py` on the final distillate file(s) to get accurate token counts for the output. Use the `total_estimated_tokens` from this analysis as `distillate_total_tokens`.
-
-5. **Report results.** Always return structured JSON output:
-
-   ```json
-   {
-     "status": "complete",
-     "distillate": "{path or folder path}",
-     "section_distillates": ["{path1}", "{path2}"] or null,
-     "source_total_tokens": N,
-     "distillate_total_tokens": N,
-     "compression_ratio": "X:1",
-     "source_documents": ["{path1}", "{path2}"],
-     "completeness_check": "pass" or "pass_with_additions"
-   }
-   ```
-
-   Where `source_total_tokens` is from the Stage 1 analysis and `distillate_total_tokens` is from step 4. The `compression_ratio` is `source_total_tokens / distillate_total_tokens` formatted as "X:1" (e.g., "3.2:1").
-
-6. If `--validate` flag was set, proceed to Stage 4. Otherwise, done.
-
-### Stage 4: Round-Trip Validation (--validate only)
-
-This stage proves the distillate is lossless by reconstructing source documents from the distillate alone. Use for critical documents where information loss is unacceptable, or as a quality gate for high-stakes downstream workflows. Not for routine use — it adds significant token cost.
-
-1. **Spawn the reconstructor agent** using `agents/round-trip-reconstructor.md`. Pass it ONLY the distillate file path (or `_index.md` path for split distillates) — it must NOT have access to the original source documents.
-
-   For split distillates, spawn one reconstructor per section in parallel. Each receives its section file plus the `_index.md` for cross-cutting context.
-
-   **Graceful degradation:** If subagent spawning is unavailable, this stage cannot be performed by the main agent (it has already seen the originals). Report that round-trip validation requires subagent support and skip.
-
-2. **Receive reconstructions.** The reconstructor returns reconstruction file paths saved adjacent to the distillate.
-
-3. **Perform semantic diff.** Read both the original source documents and the reconstructions. For each section of the original, assess:
-   - Is the core information present in the reconstruction?
-   - Are specific details preserved (numbers, names, decisions)?
-   - Are relationships and rationale intact?
-   - Did the reconstruction add anything not in the original? (indicates hallucination filling gaps)
-
-4. **Produce validation report** saved adjacent to the distillate as `-validation-report.md`:
-
-   ```markdown
-   ---
-   type: distillate-validation
-   distillate: "{distillate path}"
-   sources: ["{source paths}"]
-   created: "{date}"
-   ---
-
-   ## Validation Summary
-   - Status: PASS | PASS_WITH_WARNINGS | FAIL
-   - Information preserved: {percentage estimate}
-   - Gaps found: {count}
-   - Hallucinations detected: {count}
-
-   ## Gaps (information in originals but missing from reconstruction)
-   - {gap description} — Source: {which original}, Section: {where}
-
-   ## Hallucinations (information in reconstruction not traceable to originals)
-   - {hallucination description} — appears to fill gap in: {section}
-
-   ## Possible Gap Markers (flagged by reconstructor)
-   - {marker description}
-   ```
-
-5. **If gaps are found**, offer to run a targeted fix pass on the distillate — adding the missing information without full recompression. Limit to 2 fix passes maximum.
-
-6. **Clean up** — delete the temporary reconstruction files after the report is generated.

package/src/core/skills/xiaoma-editorial-review-prose/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-editorial-review-prose
-description: 'Clinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/core/skills/xiaoma-editorial-review-structure/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-editorial-review-structure
-description: 'Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/core/skills/xiaoma-index-docs/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-index-docs
-description: 'Generates or updates an index.md to reference all docs in the folder. Use if user requests to create or update an index of all files in a specific folder'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/core/skills/xiaoma-party-mode/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-party-mode
-description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations. Use when user requests party mode.'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/core/skills/xiaoma-review-adversarial-general/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-review-adversarial-general
-description: 'Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/core/skills/xiaoma-review-edge-case-hunter/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-review-edge-case-hunter
-description: 'Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven.'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/core/skills/xiaoma-shard-doc/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-shard-doc
-description: 'Splits large markdown documents into smaller, organized files based on level 2 (default) sections. Use if the user says perform shard document'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/core/tasks/xiaoma-create-prd/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-create-prd
-description: 'Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/1-analysis/research/xiaoma-domain-research/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-domain-research
-description: 'Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/1-analysis/research/xiaoma-market-research/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-market-research
-description: 'Conduct market research on competition and customers. Use when the user says "create a market research report about [business idea]".'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/1-analysis/research/xiaoma-technical-research/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-technical-research
-description: 'Conduct technical research on technologies and architecture. Use when the user says "create a technical research report on [topic]".'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/1-analysis/xiaoma-create-product-brief/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-create-product-brief
-description: 'Create product brief through collaborative discovery. Use when the user says "lets create a product brief" or "help me create a project brief"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/1-analysis/xiaoma-product-brief-preview/SKILL.md.bak

@@ -1,88 +0,0 @@
----
-name: bmad-product-brief-preview
-description: Create or update product briefs through guided or autonomous discovery. Use when the user requests to 'create a product brief', 'help me create a project brief', or 'update my product brief'.
-argument-hint: "[optional --create, --edit, --optimize, --distillate, --inputs, --headless] [brief idea]"
----
-
-# Create Product Brief
-
-## Overview
-
-This skill helps you create compelling product briefs through collaborative discovery, intelligent artifact analysis, and web research. Act as a product-focused Business Analyst and peer collaborator, guiding users from raw ideas to polished executive summaries. Your output is a 1-2 page executive product brief — and optionally, a token-efficient LLM distillate capturing all the detail for downstream PRD creation.
-
-The user is the domain expert. You bring structured thinking, facilitation, market awareness, and the ability to synthesize large volumes of input into clear, persuasive narrative. Work together as equals.
-
-**Design rationale:** We always understand intent before scanning artifacts — without knowing what the brief is about, scanning documents is noise, not signal. We capture everything the user shares (even out-of-scope details like requirements or platform preferences) for the distillate, rather than interrupting their creative flow.
-
-## Activation Mode Detection
-
-Check activation context immediately:
-
-1. **Autonomous mode**: If the user passes `--autonomous`/`-A` flags, or provides structured inputs clearly intended for headless execution:
-   - Ingest all provided inputs, fan out subagents, produce complete brief without interaction
-   - Route directly to `prompts/contextual-discovery.md` with `{mode}=autonomous`
-
-2. **Yolo mode**: If the user passes `--yolo` or says "just draft it" / "draft the whole thing":
-   - Ingest everything, draft complete brief upfront, then walk user through refinement
-   - Route to Stage 1 below with `{mode}=yolo`
-
-3. **Guided mode** (default): Conversational discovery with soft gates
-   - Route to Stage 1 below with `{mode}=guided`
-
-## On Activation
-
-1. Load config from `{project-root}/_xiaoma/bmm/config.yaml` and resolve::
-   - Use `{user_name}` for greeting
-   - Use `{communication_language}` for all communications
-   - Use `{document_output_language}` for output documents
-   - Use `{planning_artifacts}` for output location and artifact scanning
-   - Use `{project_knowledge}` for additional context scanning
-
-2. **Greet user** as `{user_name}`, speaking in `{communication_language}`. Be warm but efficient — dream builder energy.
-
-3. **Stage 1: Understand Intent** (handled here in SKILL.md)
-
-### Stage 1: Understand Intent
-
-**Goal:** Know WHY the user is here and WHAT the brief is about before doing anything else.
-
-**Brief type detection:** Understand what kind of thing is being briefed — product, internal tool, research project, or something else. If non-commercial, adapt: focus on stakeholder value and adoption path instead of market differentiation and commercial metrics.
-
-**Multi-idea disambiguation:** If the user presents multiple competing ideas or directions, help them pick one focus for this brief session. Note that others can be briefed separately.
-
-**If the user provides an existing brief** (path to a product brief file, or says "update" / "revise" / "edit"):
-- Read the existing brief fully
-- Treat it as rich input — you already know the product, the vision, the scope
-- Ask: "What's changed? What do you want to update or improve?"
-- The rest of the workflow proceeds normally — contextual discovery may pull in new research, elicitation focuses on gaps or changes, and draft-and-review produces an updated version
-
-**If the user already provided context** when launching the skill (description, docs, brain dump):
-- Acknowledge what you received — but **DO NOT read document files yet**. Note their paths for Stage 2's subagents to scan contextually. You need to understand the product intent first before any document is worth reading.
-- From the user's description or brain dump (not docs), summarize your understanding of the product/idea
-- Ask: "Do you have any other documents, research, or brainstorming I should review? Anything else to add before I dig in?"
-
-**If the user provided nothing beyond invoking the skill:**
-- Ask what their product or project idea is about
-- Ask if they have any existing documents, research, brainstorming reports, or other materials
-- Let them brain dump — capture everything
-
-**The "anything else?" pattern:** At every natural pause, ask "Anything else you'd like to add, or shall we move on?" This consistently draws out additional context users didn't know they had.
-
-**Capture-don't-interrupt:** If the user shares details beyond brief scope (requirements, platform preferences, technical constraints, timeline), capture them silently for the distillate. Don't redirect or stop their flow.
-
-**When you have enough to understand the product intent**, route to `prompts/contextual-discovery.md` with the current mode.
-
-## Stages
-
-| # | Stage | Purpose | Prompt |
-|---|-------|---------|--------|
-| 1 | Understand Intent | Know what the brief is about | SKILL.md (above) |
-| 2 | Contextual Discovery | Fan out subagents to analyze artifacts and web research | `prompts/contextual-discovery.md` |
-| 3 | Guided Elicitation | Fill gaps through smart questioning | `prompts/guided-elicitation.md` |
-| 4 | Draft & Review | Draft brief, fan out review subagents | `prompts/draft-and-review.md` |
-| 5 | Finalize | Polish, output, offer distillate | `prompts/finalize.md` |
-
-## External Skills
-
-This workflow uses:
-- `bmad-init` — Configuration loading (module: bmm)

package/src/xmc/workflows/2-plan-workflows/xiaoma-create-ux-design/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-create-ux-design
-description: 'Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/2-plan-workflows/xiaoma-edit-prd/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-edit-prd
-description: 'Edit an existing PRD. Use when the user says "edit this PRD".'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/2-plan-workflows/xiaoma-validate-prd/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-validate-prd
-description: 'Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/3-solutioning/xiaoma-check-implementation-readiness/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-check-implementation-readiness
-description: 'Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/3-solutioning/xiaoma-create-architecture/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-create-architecture
-description: 'Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/3-solutioning/xiaoma-create-epics-and-stories/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-create-epics-and-stories
-description: 'Break requirements into epics and user stories. Use when the user says "create the epics and stories list"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/4-implementation/xiaoma-code-review/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-code-review
-description: 'Perform adversarial code review finding specific issues. Use when the user says "run code review" or "review this code"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/4-implementation/xiaoma-correct-course/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-correct-course
-description: 'Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/4-implementation/xiaoma-create-story/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-create-story
-description: 'Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/4-implementation/xiaoma-dev-story/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-dev-story
-description: 'Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/4-implementation/xiaoma-retrospective/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-retrospective
-description: 'Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/4-implementation/xiaoma-sprint-planning/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-sprint-planning
-description: 'Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/4-implementation/xiaoma-sprint-status/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-sprint-status
-description: 'Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/xiaoma-document-project/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-document-project
-description: 'Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/xiaoma-generate-project-context/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-generate-project-context
-description: 'Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/xiaoma-qa-generate-e2e-tests/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-qa-generate-e2e-tests
-description: 'Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/xiaoma-quick-flow/xiaoma-quick-dev/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-quick-dev
-description: 'Implement a Quick Tech Spec for small changes or features. Use when the user provides a quick tech spec and says "implement this quick spec" or "proceed with implementation of [quick tech spec]"'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/xiaoma-quick-flow/xiaoma-quick-dev-new-preview/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-quick-dev-new-preview
-description: 'Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project''s existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.'
----
-
-Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/xiaoma-quick-flow/xiaoma-quick-spec/SKILL.md.bak

@@ -1,6 +0,0 @@
----
-name: bmad-quick-spec
-description: 'Very quick process to create implementation-ready quick specs for small changes or features. Use when the user says "create a quick spec" or "generate a quick tech spec"'
----
-
-Follow the instructions in [workflow.md](workflow.md).