@zeyue0329/xiaoma-cli 1.6.5 → 1.8.0

package/src/xmc/workflows/1-analysis/xiaoma-product-brief-preview/prompts/draft-and-review.md

@@ -0,0 +1,86 @@
+**Language:** Use `{communication_language}` for all output.
+**Output Language:** Use `{document_output_language}` for documents.
+**Output Location:** `{planning_artifacts}`
+
+# Stage 4: Draft & Review
+
+**Goal:** Produce the executive product brief and run it through multiple review lenses to catch blind spots before the user sees the final version.
+
+## Step 1: Draft the Executive Brief
+
+Use `../resources/brief-template.md` as a guide — adapt structure to fit the product's story.
+
+**Writing principles:**
+- **Executive audience** — persuasive, clear, concise. 1-2 pages.
+- **Lead with the problem** — make the reader feel the pain before presenting the solution
+- **Concrete over abstract** — specific examples, real scenarios, measurable outcomes
+- **Confident voice** — this is a pitch, not a hedge
+- Write in `{document_output_language}`
+
+**Create the output document at:** `{planning_artifacts}/product-brief-{project_name}.md`
+
+Include YAML frontmatter:
+```yaml
+---
+title: "Product Brief: {project_name}"
+status: "draft"
+created: "{timestamp}"
+updated: "{timestamp}"
+inputs: [list of input files used]
+---
+```
+
+## Step 2: Fan Out Review Subagents
+
+Before showing the draft to the user, run it through multiple review lenses in parallel.
+
+**Launch in parallel:**
+
+1. **Skeptic Reviewer** (`../agents/skeptic-reviewer.md`) — "What's missing? What assumptions are untested? What could go wrong? Where is the brief vague or hand-wavy?"
+
+2. **Opportunity Reviewer** (`../agents/opportunity-reviewer.md`) — "What adjacent value propositions are being missed? What market angles or partnerships could strengthen this? What's underemphasized?"
+
+3. **Contextual Reviewer** — You (the main agent) pick the most useful third lens based on THIS specific product. Choose the lens that addresses the SINGLE BIGGEST RISK that the skeptic and opportunity reviewers won't naturally catch. Examples:
+   - For healthtech: "Regulatory and compliance risk reviewer"
+   - For devtools: "Developer experience and adoption friction critic"
+   - For marketplace: "Network effects and chicken-and-egg problem analyst"
+   - For enterprise: "Procurement and organizational change management reviewer"
+   - **When domain is unclear, default to:** "Go-to-market and launch risk reviewer" — examines distribution, pricing, and first-customer acquisition. Almost always valuable, frequently missed.
+   Describe the lens, run the review yourself inline.
+
+### Graceful Degradation
+
+If subagents are unavailable:
+- Perform all three review passes yourself, sequentially
+- Apply each lens deliberately — don't blend them into one generic review
+- The quality of review matters more than the parallelism
+
+## Step 3: Integrate Review Insights
+
+After all reviews complete:
+
+1. **Triage findings** — group by theme, remove duplicates
+2. **Apply non-controversial improvements** directly to the draft (obvious gaps, unclear language, missing specifics)
+3. **Flag substantive suggestions** that need user input (strategic choices, scope questions, market positioning decisions)
+
+## Step 4: Present to User
+
+**Headless mode:** Skip to `finalize.md` — no user interaction. Save the improved draft directly.
+
+**Yolo and Guided modes:**
+
+Present the draft brief to the user. Then share the reviewer insights:
+
+"Here's your product brief draft. Before we finalize, my review panel surfaced some things worth considering:
+
+**[Grouped reviewer findings — only the substantive ones that need user input]**
+
+What do you think? Any changes you'd like to make?"
+
+Present reviewer findings with brief rationale, then offer: "Want me to dig into any of these, or are you ready to make your revisions?"
+
+**Iterate** as long as the user wants to refine. Use the "anything else, or are we happy with this?" soft gate.
+
+## Stage Complete
+
+This stage is complete when: (a) the draft has been reviewed by all three lenses and improvements integrated, AND either (autonomous) save and route directly, or (guided/yolo) the user is satisfied. Route to `finalize.md`.

package/src/xmc/workflows/1-analysis/xiaoma-product-brief-preview/prompts/finalize.md

@@ -0,0 +1,75 @@
+**Language:** Use `{communication_language}` for all output.
+**Output Language:** Use `{document_output_language}` for documents.
+**Output Location:** `{planning_artifacts}`
+
+# Stage 5: Finalize
+
+**Goal:** Save the polished brief, offer the LLM distillate, and point the user forward.
+
+## Step 1: Polish and Save
+
+Update the product brief document at `{planning_artifacts}/product-brief-{project_name}.md`:
+- Update frontmatter `status` to `"complete"`
+- Update `updated` timestamp
+- Ensure formatting is clean and consistent
+- Confirm the document reads well as a standalone 1-2 page executive summary
+
+## Step 2: Offer the Distillate
+
+Throughout the discovery process, you likely captured detail that doesn't belong in a 1-2 page executive summary but is valuable for downstream work — requirements hints, platform preferences, rejected ideas, technical constraints, detailed user scenarios, competitive deep-dives, etc.
+
+**Ask the user:**
+"Your product brief is complete. During our conversation, I captured additional detail that goes beyond the executive summary — things like [mention 2-3 specific examples of overflow you captured]. Would you like me to create a detail pack for PRD creation? It distills all that extra context into a concise, structured format optimized for the next phase."
+
+**If yes, create the distillate** at `{planning_artifacts}/product-brief-{project_name}-distillate.md`:
+
+```yaml
+---
+title: "Product Brief Distillate: {project_name}"
+type: llm-distillate
+source: "product-brief-{project_name}.md"
+created: "{timestamp}"
+purpose: "Token-efficient context for downstream PRD creation"
+---
+```
+
+**Distillate content principles:**
+- Dense bullet points, not prose
+- Each bullet carries enough context to be understood standalone (don't assume the reader has the full brief loaded)
+- Group by theme, not by when it was mentioned
+- Include:
+  - **Rejected ideas** — so downstream workflows don't re-propose them, with brief rationale
+  - **Requirements hints** — anything the user mentioned that sounds like a requirement
+  - **Technical context** — platforms, integrations, constraints, preferences
+  - **Detailed user scenarios** — richer than what fits in the exec summary
+  - **Competitive intelligence** — specifics from web research worth preserving
+  - **Open questions** — things surfaced but not resolved during discovery
+  - **Scope signals** — what the user indicated is in/out/maybe for MVP
+- Token-conscious: be concise, but give enough context per bullet so an LLM reading this later understands WHY each point matters
+
+**Headless mode:** Always create the distillate automatically — unless the session was too brief to capture meaningful overflow (in that case, note this in the completion output instead of creating an empty file).
+
+## Step 3: Present Completion
+
+"Your product brief for {project_name} is complete!
+
+**Executive Brief:** `{planning_artifacts}/product-brief-{project_name}.md`
+[If distillate created:] **Detail Pack:** `{planning_artifacts}/product-brief-{project_name}-distillate.md`
+
+**Recommended next step:** Use the product brief (and detail pack) as input for PRD creation — tell your assistant 'create a PRD' and point it to these files."
+[If distillate created:] "The detail pack contains all the overflow context (requirements hints, rejected ideas, technical constraints) specifically structured for the PRD workflow to consume."
+
+**Headless mode:** Output the file paths as structured JSON and exit:
+```json
+{
+  "status": "complete",
+  "brief": "{planning_artifacts}/product-brief-{project_name}.md",
+  "distillate": "{path or null}",
+  "confidence": "high|medium|low",
+  "open_questions": ["any unresolved items"]
+}
+```
+
+## Stage Complete
+
+This is the terminal stage. After delivering the completion message and file paths, the workflow is done. If the user requests further revisions, loop back to `draft-and-review.md`. Otherwise, exit.

package/src/xmc/workflows/1-analysis/xiaoma-product-brief-preview/prompts/guided-elicitation.md

@@ -0,0 +1,70 @@
+**Language:** Use `{communication_language}` for all output.
+**Output Language:** Use `{document_output_language}` for documents.
+
+# Stage 3: Guided Elicitation
+
+**Goal:** Fill the gaps in what you know. By now you have the user's brain dump, artifact analysis, and web research. This stage is about smart, targeted questioning — not rote section-by-section interrogation.
+
+**Skip this stage entirely in Yolo and Autonomous modes** — go directly to `draft-and-review.md`.
+
+## Approach
+
+You are NOT walking through a rigid questionnaire. You're having a conversation that covers the substance of a great product brief. The topics below are your mental checklist, not a script. Adapt to:
+- What you already know (don't re-ask what's been covered)
+- What the user is excited about (follow their energy)
+- What's genuinely unclear (focus questions where they matter)
+
+## Topics to Cover (flexibly, conversationally)
+
+### Vision & Problem
+- What core problem does this solve? For whom?
+- How do people solve this today? What's frustrating about current approaches?
+- What would success look like for the people this helps?
+- What's the insight or angle that makes this approach different?
+
+### Users & Value
+- Who experiences this problem most acutely?
+- Are there different user types with different needs?
+- What's the "aha moment" — when does a user realize this is what they needed?
+- How does this fit into their existing workflow or life?
+
+### Market & Differentiation
+- What competitive or alternative solutions exist? (Leverage web research findings)
+- What's the unfair advantage or defensible moat?
+- Why is now the right time for this?
+
+### Success & Scope
+- How will you know this is working? What metrics matter?
+- What's the minimum viable version that creates real value?
+- What's explicitly NOT in scope for the first version?
+- If this is wildly successful, what does it become in 2-3 years?
+
+## The Flow
+
+For each topic area where you have gaps:
+
+1. **Lead with what you know** — "Based on your input and my research, it sounds like [X]. Is that right?"
+2. **Ask the gap question** — targeted, specific, not generic
+3. **Reflect and confirm** — paraphrase what you heard
+4. **"Anything else on this, or shall we move on?"** — the soft gate
+
+If the user is giving you detail beyond brief scope (requirements, architecture, platform details, timelines), **capture it silently** for the distillate. Acknowledge it briefly ("Good detail, I'll capture that") but don't derail the conversation.
+
+## When to Move On
+
+When you have enough substance to draft a compelling 1-2 page executive brief covering:
+- Clear problem and who it affects
+- Proposed solution and what makes it different
+- Target users (at least primary)
+- Some sense of success criteria or business objectives
+- MVP-level scope thinking
+
+You don't need perfection — you need enough to draft well. Missing details can be surfaced during the review stage.
+
+If the user is providing complete, confident answers and you have solid coverage across all four topic areas after fewer than 3-4 exchanges, proactively offer to draft early.
+
+**Transition:** "I think I have a solid picture. Ready for me to draft the brief, or is there anything else you'd like to add?"
+
+## Stage Complete
+
+This stage is complete when sufficient substance exists to draft a compelling brief and the user confirms readiness. Route to `draft-and-review.md`.

package/src/xmc/workflows/1-analysis/xiaoma-product-brief-preview/resources/brief-template.md

@@ -0,0 +1,60 @@
+# Product Brief Template
+
+This is a flexible guide for the executive product brief — adapt it to serve the product's story. Merge sections, add new ones, reorder as needed. The product determines the structure, not the template.
+
+## Sensible Default Structure
+
+```markdown
+# Product Brief: {Product Name}
+
+## Executive Summary
+
+[2-3 paragraph narrative: What is this? What problem does it solve? Why does it matter? Why now?
+This should be compelling enough to stand alone — if someone reads only this section, they should understand the vision.]
+
+## The Problem
+
+[What pain exists? Who feels it? How are they coping today? What's the cost of the status quo?
+Be specific — real scenarios, real frustrations, real consequences.]
+
+## The Solution
+
+[What are we building? How does it solve the problem?
+Focus on the experience and outcome, not the implementation.]
+
+## What Makes This Different
+
+[Key differentiators. Why this approach vs alternatives? What's the unfair advantage?
+Be honest — if the moat is execution speed, say so. Don't fabricate technical moats.]
+
+## Who This Serves
+
+[Primary users — vivid but brief. Who are they, what do they need, what does success look like for them?
+Secondary users if relevant.]
+
+## Success Criteria
+
+[How do we know this is working? What metrics matter?
+Mix of user success signals and business objectives. Be measurable.]
+
+## Scope
+
+[What's in for the first version? What's explicitly out?
+Keep this tight — it's a boundary document, not a feature list.]
+
+## Vision
+
+[Where does this go if it succeeds? What does it become in 2-3 years?
+Inspiring but grounded.]
+```
+
+## Adaptation Guidelines
+
+- **For B2B products:** Consider adding a "Buyer vs User" section if they're different people
+- **For platforms/marketplaces:** Consider a "Network Effects" or "Ecosystem" section
+- **For technical products:** May need a brief "Technical Approach" section (keep it high-level)
+- **For regulated industries:** Consider a "Compliance & Regulatory" section
+- **If scope is well-defined:** Merge "Scope" and "Vision" into "Roadmap Thinking"
+- **If the problem is well-known:** Shorten "The Problem" and expand "What Makes This Different"
+
+The brief should be 1-2 pages. If it's longer, you're putting in too much detail — that's what the distillate is for.

package/src/xmc/workflows/1-analysis/xiaoma-product-brief-preview/xiaoma-manifest.json

@@ -0,0 +1,17 @@
+{
+  "module-code": "xmc",
+  "replaces-skill": "xiaoma-create-product-brief",
+  "capabilities": [
+    {
+      "name": "create-brief",
+      "menu-code": "CB",
+      "description": "Produces executive product brief and optional LLM distillate for PRD input.",
+      "supports-headless": true,
+      "phase-name": "1-analysis",
+      "after": ["brainstorming, perform-research"],
+      "before": ["create-prd"],
+      "is-required": true,
+      "output-location": "{planning_artifacts}"
+    }
+  ]
+}

package/src/xmc/workflows/1-analysis/xiaoma-product-brief-preview/xiaoma-skill-manifest.yaml

@@ -0,0 +1 @@
+type: skill

package/src/xmc/workflows/2-plan-workflows/create-prd/steps-v/step-v-01-discovery.md

@@ -4,8 +4,6 @@ description: 'Document Discovery & Confirmation - Handle fresh context validatio
 
 # File references (ONLY variables used in this step)
 nextStepFile: './step-v-02-format-detection.md'
-advancedElicitationTask: '{project-root}/_xiaoma/core/workflows/advanced-elicitation/workflow.md'
-partyModeWorkflow: '{project-root}/_xiaoma/core/workflows/party-mode/workflow.md'
 prdPurpose: '../data/prd-purpose.md'
 ---
 
@@ -195,8 +193,8 @@ Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Conti
 
 #### Menu Handling Logic:
 
-- IF A: Read fully and follow: {advancedElicitationTask}, and when finished redisplay the menu
-- IF P: Read fully and follow: {partyModeWorkflow}, and when finished redisplay the menu
+- IF A: Invoke the `xiaoma-advanced-elicitation` skill, and when finished redisplay the menu
+- IF P: Invoke the `xiaoma-party-mode` skill, and when finished redisplay the menu
 - IF C: Read fully and follow: {nextStepFile} to begin format detection
 - IF user provides additional document: Load it, update report, redisplay summary
 - IF Any other: help user, then redisplay menu

package/src/xmc/workflows/2-plan-workflows/create-prd/steps-v/step-v-10-smart-validation.md

@@ -6,7 +6,6 @@ description: 'SMART Requirements Validation - Validate Functional Requirements m
 nextStepFile: './step-v-11-holistic-quality-validation.md'
 prdFile: '{prd_file_path}'
 validationReportPath: '{validation_report_path}'
-advancedElicitationTask: '{project-root}/_xiaoma/core/workflows/advanced-elicitation/workflow.md'
 ---
 
 # Step 10: SMART Requirements Validation
@@ -24,6 +23,7 @@ Validate Functional Requirements meet SMART quality criteria (Specific, Measurab
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 

package/src/xmc/workflows/2-plan-workflows/create-prd/steps-v/step-v-11-holistic-quality-validation.md

@@ -6,7 +6,6 @@ description: 'Holistic Quality Assessment - Assess PRD as cohesive, compelling d
 nextStepFile: './step-v-12-completeness-validation.md'
 prdFile: '{prd_file_path}'
 validationReportPath: '{validation_report_path}'
-advancedElicitationTask: '{project-root}/_xiaoma/core/workflows/advanced-elicitation/workflow.md'
 ---
 
 # Step 11: Holistic Quality Assessment
@@ -24,6 +23,7 @@ Assess the PRD as a cohesive, compelling document - evaluating document flow, du
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 
@@ -66,8 +66,8 @@ Assess the PRD as a cohesive, compelling document - evaluating document flow, du
 
 "Perform holistic quality assessment on this PRD using multi-perspective evaluation:
 
-**Read fully and follow the Advanced Elicitation workflow:**
-{advancedElicitationTask}
+**Advanced Elicitation workflow:**
+Invoke the `xiaoma-advanced-elicitation` skill
 
 **Evaluate the PRD from these perspectives:**
 

package/src/xmc/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md

@@ -22,6 +22,7 @@ Finalize validation report, summarize all findings from steps 1-12, present summ
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 
@@ -181,7 +182,7 @@ Display:
 - **IF E (Use Edit Workflow):**
   - Explain: "The Edit workflow (steps-e/) can use this validation report to systematically address issues. Edit mode will guide you through discovering what to edit, reviewing the PRD, and applying targeted improvements."
   - Offer: "Would you like to launch Edit mode now? It will help you fix validation findings systematically."
-  - If yes: Read fully and follow: steps-e/step-e-01-discovery.md
+  - If yes: Read fully and follow: `./steps-e/step-e-01-discovery.md`
   - If no: Return to menu
 
 - **IF F (Fix Simpler Items):**

package/src/xmc/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md

@@ -1,6 +1,7 @@
 ---
 name: validate-prd
 description: 'Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation"'
+standalone: false
 main_config: '{project-root}/_xiaoma/xmc/config.yaml'
 validateWorkflow: './steps-v/step-v-01-discovery.md'
 ---
@@ -55,6 +56,7 @@ Load and read full config from {main_config} and resolve:
 - `date` as system-generated current datetime
 
 ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
+✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`.
 
 ### 2. Route to Validate Workflow
 

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

@@ -0,0 +1,6 @@
+---
+name: xiaoma-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.

package/src/xmc/workflows/2-plan-workflows/{create-ux-design → xiaoma-create-ux-design}/steps/step-01-init.md

@@ -44,7 +44,7 @@ First, check if the output document already exists:
 
 If the document exists and has frontmatter with `stepsCompleted`:
 
-- **STOP here** and load `{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-ux-design/steps/step-01b-continue.md` immediately
+- **STOP here** and load `./step-01b-continue.md` immediately
 - Do not proceed with any initialization tasks
 - Let step-01b handle the continuation logic
 
@@ -58,7 +58,7 @@ Discover and load context documents using smart discovery. Documents can be in t
 - {planning_artifacts}/**
 - {output_folder}/**
 - {product_knowledge}/**
-- docs/**
+- {project-root}/docs/**
 
 Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
 
@@ -80,7 +80,7 @@ Try to discover the following:
 
 #### B. Create Initial Document
 
-Copy the template from `{installed_path}/ux-design-template.md` to `{planning_artifacts}/ux-design-specification.md`
+Copy the template from `../ux-design-template.md` to `{planning_artifacts}/ux-design-specification.md`
 Initialize frontmatter in the template.
 
 #### C. Complete Initialization and Report
@@ -110,7 +110,7 @@ Do you have any other documents you'd like me to include, or shall we continue t
 
 ## NEXT STEP:
 
-After user selects [C] to continue, ensure the file `{planning_artifacts}/ux-design-specification.md` has been created and saved, and then load `{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md` to begin the UX discovery phase.
+After user selects [C] to continue, ensure the file `{planning_artifacts}/ux-design-specification.md` has been created and saved, and then load `./step-02-discovery.md` to begin the UX discovery phase.
 
 Remember: Do NOT proceed to step-02 until output file has been updated and user explicitly selects [C] to continue!
 

package/src/xmc/workflows/2-plan-workflows/{create-ux-design → xiaoma-create-ux-design}/steps/step-01b-continue.md

@@ -72,9 +72,9 @@ Does this look right, or do you want to make any adjustments before we proceed?"
 
 Based on `lastStep` value, determine which step to load next:
 
-- If `lastStep = 1` → Load `{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md`
-- If `lastStep = 2` → Load `{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md`
-- If `lastStep = 3` → Load `{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md`
+- If `lastStep = 1` → Load `./step-02-discovery.md`
+- If `lastStep = 2` → Load `./step-03-core-experience.md`
+- If `lastStep = 3` → Load `./step-04-emotional-response.md`
 - Continue this pattern for all steps
 - If `lastStep` indicates final step → Workflow already complete
 
@@ -108,7 +108,7 @@ After presenting current progress, ask:
 If `lastStep` indicates the final step is completed:
 "Great news! It looks like we've already completed the UX design workflow for {{project_name}}.
 
-The final UX design specification is ready at {output_folder}/ux-design-specification.md with all sections completed through step {finalStepNumber}.
+The final UX design specification is ready at {planning_artifacts}/ux-design-specification.md with all sections completed through step {finalStepNumber}.
 
 The complete UX design includes visual foundations, user flows, and design specifications ready for implementation.
 

package/src/xmc/workflows/2-plan-workflows/{create-ux-design → xiaoma-create-ux-design}/steps/step-02-discovery.md

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Read fully and follow: {project-root}/_xiaoma/core/workflows/advanced-elicitation/workflow.md
-- When 'P' selected: Read fully and follow: {project-root}/_xiaoma/core/workflows/party-mode/workflow.md
+- When 'A' selected: Invoke the `xiaoma-advanced-elicitation` skill
+- When 'P' selected: Invoke the `xiaoma-party-mode` skill
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -155,11 +155,11 @@ Show the generated project understanding content and present choices:
 
 - Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: `stepsCompleted: [1, 2]`
-- Load `{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md`
+- Load `./step-03-core-experience.md`
 
 ## APPEND TO DOCUMENT:
 
-When user selects 'C', append the content directly to the document. Only after the content is saved to document, read fully and follow: `{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md`.
+When user selects 'C', append the content directly to the document. Only after the content is saved to document, read fully and follow: `./step-03-core-experience.md`.
 
 ## SUCCESS METRICS:
 

package/src/xmc/workflows/2-plan-workflows/{create-ux-design → xiaoma-create-ux-design}/steps/step-03-core-experience.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on defining the core user experience and platform
 - 🎯 COLLABORATIVE discovery, not assumption-based design
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -30,8 +31,8 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Read fully and follow: {project-root}/_xiaoma/core/workflows/advanced-elicitation/workflow.md
-- When 'P' selected: Read fully and follow: {project-root}/_xiaoma/core/workflows/party-mode/workflow.md
+- When 'A' selected: Invoke the `xiaoma-advanced-elicitation` skill
+- When 'P' selected: Invoke the `xiaoma-party-mode` skill
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -161,7 +162,7 @@ Show the generated core experience content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Read fully and follow: {project-root}/_xiaoma/core/workflows/advanced-elicitation/workflow.md with the current core experience content
+- Invoke the `xiaoma-advanced-elicitation` skill with the current core experience content
 - Process the enhanced experience insights that come back
 - Ask user: "Accept these improvements to the core experience definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -169,7 +170,7 @@ Show the generated core experience content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Read fully and follow: {project-root}/_xiaoma/core/workflows/party-mode/workflow.md with the current core experience definition
+- Invoke the `xiaoma-party-mode` skill with the current core experience definition
 - Process the collaborative experience improvements that come back
 - Ask user: "Accept these changes to the core experience definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -179,7 +180,7 @@ Show the generated core experience content and present choices:
 
 - Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: append step to end of stepsCompleted array
-- Load `{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md`
+- Load `./step-04-emotional-response.md`
 
 ## APPEND TO DOCUMENT:
 
@@ -211,6 +212,6 @@ When user selects 'C', append the content directly to the document using the str
 
 ## NEXT STEP:
 
-After user selects 'C' and content is saved to document, load `{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md` to define desired emotional responses.
+After user selects 'C' and content is saved to document, load `./step-04-emotional-response.md` to define desired emotional responses.
 
 Remember: Do NOT proceed to step-04 until user explicitly selects 'C' from the A/P/C menu and content is saved!

package/src/xmc/workflows/2-plan-workflows/{create-ux-design → xiaoma-create-ux-design}/steps/step-04-emotional-response.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on defining desired emotional responses and user feelings
 - 🎯 COLLABORATIVE discovery, not assumption-based design
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -30,8 +31,8 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Read fully and follow: {project-root}/_xiaoma/core/workflows/advanced-elicitation/workflow.md
-- When 'P' selected: Read fully and follow: {project-root}/_xiaoma/core/workflows/party-mode/workflow.md
+- When 'A' selected: Invoke the `xiaoma-advanced-elicitation` skill
+- When 'P' selected: Invoke the `xiaoma-party-mode` skill
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -164,7 +165,7 @@ Show the generated emotional response content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Read fully and follow: {project-root}/_xiaoma/core/workflows/advanced-elicitation/workflow.md with the current emotional response content
+- Invoke the `xiaoma-advanced-elicitation` skill with the current emotional response content
 - Process the enhanced emotional insights that come back
 - Ask user: "Accept these improvements to the emotional response definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -172,7 +173,7 @@ Show the generated emotional response content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Read fully and follow: {project-root}/_xiaoma/core/workflows/party-mode/workflow.md with the current emotional response definition
+- Invoke the `xiaoma-party-mode` skill with the current emotional response definition
 - Process the collaborative emotional insights that come back
 - Ask user: "Accept these changes to the emotional response definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -182,7 +183,7 @@ Show the generated emotional response content and present choices:
 
 - Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: append step to end of stepsCompleted array
-- Load `{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md`
+- Load `./step-05-inspiration.md`
 
 ## APPEND TO DOCUMENT:
 
@@ -214,6 +215,6 @@ When user selects 'C', append the content directly to the document using the str
 
 ## NEXT STEP:
 
-After user selects 'C' and content is saved to document, load `{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md` to analyze UX patterns from inspiring products.
+After user selects 'C' and content is saved to document, load `./step-05-inspiration.md` to analyze UX patterns from inspiring products.
 
 Remember: Do NOT proceed to step-05 until user explicitly selects 'C' from the A/P/C menu and content is saved!