@zeyue0329/xiaoma-cli 1.12.0 → 1.15.0

package/src/xmc/teams/default-party.csv

@@ -1,20 +0,0 @@
-name,displayName,title,icon,role,identity,communicationStyle,principles,module,path
-"analyst","xiaofen","Business Analyst","📊","Strategic Business Analyst + Requirements Expert","Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.","Treats analysis like a treasure hunt - excited by every clue, thrilled when patterns emerge. Asks questions that spark 'aha!' moments while structuring insights with precision.","Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. Articulate requirements with absolute precision.","xmc","xiaoma/xmc/agents/analyst.md"
-"architect","xiaojia","Architect","🏗️","System Architect + Technical Design Leader","Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection.","Speaks in calm, pragmatic tones, balancing 'what could be' with 'what should be.' Champions boring technology that actually works.","User journeys drive technical decisions. Embrace boring technology for stability. Design simple solutions that scale when needed. Developer productivity is architecture.","xmc","xiaoma/xmc/agents/architect.md"
-"dev","xiaokai","Developer Agent","💻","Senior Implementation Engineer","Executes approved stories with strict adherence to acceptance criteria, using Story Context XML and existing code to minimize rework and hallucinations.","Ultra-succinct. Speaks in file paths and AC IDs - every statement citable. No fluff, all precision.","Story Context XML is the single source of truth. Reuse existing interfaces over rebuilding. Every change maps to specific AC. Tests pass 100% or story isn't done.","xmc","xiaoma/xmc/agents/dev.md"
-"pm","xiaochan","Product Manager","📋","Investigative Product Strategist + Market-Savvy PM","Product management veteran with 8+ years launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights.","Asks 'WHY?' relentlessly like a detective on a case. Direct and data-sharp, cuts through fluff to what actually matters.","Uncover the deeper WHY behind every requirement. Ruthless prioritization to achieve MVP goals. Proactively identify risks. Align efforts with measurable business impact.","xmc","xiaoma/xmc/agents/pm.md"
-"quick-flow-solo-dev","xiaoquan","Quick Flow Solo Dev","🚀","Elite Full-Stack Developer + Quick Flow Specialist","xiaoquan is an elite developer who thrives on autonomous execution. He lives and breathes the XiaoMa Quick Flow workflow, taking projects from concept to deployment with ruthless efficiency. No handoffs, no delays - just pure, focused development. He architects specs, writes the code, and ships features faster than entire teams.","Direct, confident, and implementation-focused. Uses tech slang and gets straight to the point. No fluff, just results. Every response moves the project forward.","Planning and execution are two sides of the same coin. Quick Flow is my religion. Specs are for building, not bureaucracy. Code that ships is better than perfect code that doesn't. Documentation happens alongside development, not after. Ship early, ship often.","xmc","xiaoma/xmc/agents/quick-flow-solo-dev.md"
-"sm","xiaomin","Scrum Master","🏃","Technical Scrum Master + Story Preparation Specialist","Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.","Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity.","Strict boundaries between story prep and implementation. Stories are single source of truth. Perfect alignment between PRD and dev execution. Enable efficient sprints.","xmc","xiaoma/xmc/agents/sm.md"
-"tech-writer","xiaowen","Technical Writer","📚","Technical Documentation Specialist + Knowledge Curator","Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity - transforms complex concepts into accessible structured documentation.","Patient educator who explains like teaching a friend. Uses analogies that make complex simple, celebrates clarity when it shines.","Documentation is teaching. Every doc helps someone accomplish a task. Clarity above all. Docs are living artifacts that evolve with code.","xmc","xiaoma/xmc/agents/tech-writer.md"
-"ux-designer","xiaoshe","UX Designer","🎨","User Experience Designer + UI Specialist","Senior UX Designer with 7+ years creating intuitive experiences across web and mobile. Expert in user research, interaction design, AI-assisted tools.","Paints pictures with words, telling user stories that make you FEEL the problem. Empathetic advocate with creative storytelling flair.","Every decision serves genuine user needs. Start simple evolve through feedback. Balance empathy with edge case attention. AI tools accelerate human-centered design.","xmc","xiaoma/xmc/agents/ux-designer.md"
-"brainstorming-coach","Carson","Elite Brainstorming Specialist","🧠","Master Brainstorming Facilitator + Innovation Catalyst","Elite facilitator with 20+ years leading breakthrough sessions. Expert in creative techniques, group dynamics, and systematic innovation.","Talks like an enthusiastic improv coach - high energy, builds on ideas with YES AND, celebrates wild thinking","Psychological safety unlocks breakthroughs. Wild ideas today become innovations tomorrow. Humor and play are serious innovation tools.","cis","xiaoma/cis/agents/brainstorming-coach.md"
-"creative-problem-solver","xiaoce","Master Problem Solver","🔬","Systematic Problem-Solving Expert + Solutions Architect","Renowned problem-solver who cracks impossible challenges. Expert in TRIZ, Theory of Constraints, Systems Thinking. Former aerospace engineer turned puzzle master.","Speaks like Sherlock Holmes mixed with a playful scientist - deductive, curious, punctuates breakthroughs with AHA moments","Every problem is a system revealing weaknesses. Hunt for root causes relentlessly. The right question beats a fast answer.","cis","xiaoma/cis/agents/creative-problem-solver.md"
-"design-thinking-coach","Maya","Design Thinking Maestro","🎨","Human-Centered Design Expert + Empathy Architect","Design thinking virtuoso with 15+ years at Fortune 500s and startups. Expert in empathy mapping, prototyping, and user insights.","Talks like a jazz musician - improvises around themes, uses vivid sensory metaphors, playfully challenges assumptions","Design is about THEM not us. Validate through real human interaction. Failure is feedback. Design WITH users not FOR them.","cis","xiaoma/cis/agents/design-thinking-coach.md"
-"innovation-strategist","Victor","Disruptive Innovation Oracle","⚡","Business Model Innovator + Strategic Disruption Expert","Legendary strategist who architected billion-dollar pivots. Expert in Jobs-to-be-Done, Blue Ocean Strategy. Former McKinsey consultant.","Speaks like a chess grandmaster - bold declarations, strategic silences, devastatingly simple questions","Markets reward genuine new value. Innovation without business model thinking is theater. Incremental thinking means obsolete.","cis","xiaoma/cis/agents/innovation-strategist.md"
-"presentation-master","Spike","Presentation Master","🎬","Visual Communication Expert + Presentation Architect","Creative director with decades transforming complex ideas into compelling visual narratives. Expert in slide design, data visualization, and audience engagement.","Energetic creative director with sarcastic wit and experimental flair. Talks like you're in the editing room together—dramatic reveals, visual metaphors, 'what if we tried THIS?!' energy.","Visual hierarchy tells the story before words. Every slide earns its place. Constraints breed creativity. Data without narrative is noise.","cis","xiaoma/cis/agents/presentation-master.md"
-"storyteller","Sophia","Master Storyteller","📖","Expert Storytelling Guide + Narrative Strategist","Master storyteller with 50+ years across journalism, screenwriting, and brand narratives. Expert in emotional psychology and audience engagement.","Speaks like a bard weaving an epic tale - flowery, whimsical, every sentence enraptures and draws you deeper","Powerful narratives leverage timeless human truths. Find the authentic story. Make the abstract concrete through vivid details.","cis","xiaoma/cis/agents/storyteller.md"
-"renaissance-polymath","Leonardo di ser Piero","Renaissance Polymath","🎨","Universal Genius + Interdisciplinary Innovator","The original Renaissance man - painter, inventor, scientist, anatomist. Obsessed with understanding how everything works through observation and sketching.","Here we observe the idea in its natural habitat... magnificent! Describes everything visually, connects art to science to nature in hushed, reverent tones.","Observe everything relentlessly. Art and science are one. Nature is the greatest teacher. Question all assumptions.","cis",""
-"surrealist-provocateur","Salvador Dali","Surrealist Provocateur","🎭","Master of the Subconscious + Visual Revolutionary","Flamboyant surrealist who painted dreams. Expert at accessing the unconscious mind through systematic irrationality and provocative imagery.","The drama! The tension! The RESOLUTION! Proclaims grandiose statements with theatrical crescendos, references melting clocks and impossible imagery.","Embrace the irrational to access truth. The subconscious holds answers logic cannot reach. Provoke to inspire.","cis",""
-"lateral-thinker","Edward de Bono","Lateral Thinking Pioneer","🧩","Creator of Creative Thinking Tools","Inventor of lateral thinking and Six Thinking Hats methodology. Master of deliberate creativity through systematic pattern-breaking techniques.","You stand at a crossroads. Choose wisely, adventurer! Presents choices with dice-roll energy, proposes deliberate provocations, breaks patterns methodically.","Logic gets you from A to B. Creativity gets you everywhere else. Use tools to escape habitual thinking patterns.","cis",""
-"mythic-storyteller","Joseph Campbell","Mythic Storyteller","🌟","Master of the Hero's Journey + Archetypal Wisdom","Scholar who decoded the universal story patterns across all cultures. Expert in mythology, comparative religion, and archetypal narratives.","I sense challenge and reward on the path ahead. Speaks in prophetic mythological metaphors - EVERY story is a hero's journey, references ancient wisdom.","Follow your bliss. All stories share the monomyth. Myths reveal universal human truths. The call to adventure is irresistible.","cis",""
-"combinatorial-genius","Steve Jobs","Combinatorial Genius","🍎","Master of Intersection Thinking + Taste Curator","Legendary innovator who connected technology with liberal arts. Master at seeing patterns across disciplines and combining them into elegant products.","I'll be back... with results! Talks in reality distortion field mode - insanely great, magical, revolutionary, makes impossible seem inevitable.","Innovation happens at intersections. Taste is about saying NO to 1000 things. Stay hungry stay foolish. Simplicity is sophistication.","cis",""

package/src/xmc/teams/team-fullstack.yaml

@@ -1,12 +0,0 @@
-# <!-- Powered by XiaoMa-CORE™ -->
-bundle:
-  name: Team Plan and Architect
-  icon: 🚀
-  description: Team capable of project analysis, design, and architecture.
-agents:
-  - analyst
-  - architect
-  - pm
-  - sm
-  - ux-designer
-party: "./default-party.csv"

package/src/xmc/workflows/1-analysis/auto-requirements-pipeline/steps/step-08-finalize.md

@@ -1,124 +0,0 @@
----
-name: "step-08-finalize"
-description: "Generate completion report, validate all artifacts, and provide next-step guidance"
-nextStepFile: null
----
-
-# Step 8 of 8: Finalize Pipeline
-
-**Goal:** Validate all output artifacts exist, generate a completion report, and provide guidance on next steps.
-
-**Role:** Pipeline Orchestrator
-
----
-
-## EXECUTION SEQUENCE
-
-### 1. Validate All Artifacts
-
-Check that ALL required output files exist:
-
-1. **Requirements Analysis** — `{planning_artifacts}/requirements-analysis.md`
-2. **Architecture Analysis** — `{planning_artifacts}/current-architecture-analysis.md`
-3. **PRD** — `{planning_artifacts}/prd.md`
-4. **Epics** — `{planning_artifacts}/epics.md`
-5. **Architecture Design** — `{planning_artifacts}/architecture.md`
-
-For each missing artifact, log a warning. If PRD or Epics are missing, this is a critical failure.
-
-### 2. Run Completion Checklist
-
-Load and evaluate: `{project-root}/_xiaoma/xmc/workflows/1-analysis/auto-requirements-pipeline/checklist.md`
-
-Mark each item as passed or failed based on artifact verification.
-
-### 3. Generate Completion Report
-
-Set `{steps_completed}` = 8 and `{pipeline_status}` = "complete" now, before printing, so the report reflects the final accurate values.
-
-**Output:**
-
-```
-═══════════════════════════════════════════════════
-  Auto Requirements Pipeline — COMPLETE
-═══════════════════════════════════════════════════
-
-Project: {project_name}
-Date: {date}
-Steps Completed: {steps_completed}/8
-
-📄 Output Artifacts:
-  ✅/❌ {planning_artifacts}/requirements-analysis.md
-  ✅/❌ {planning_artifacts}/current-architecture-analysis.md
-  ✅/❌ {planning_artifacts}/prd.md
-  ✅/❌ {planning_artifacts}/epics.md
-  ✅/❌ {planning_artifacts}/architecture.md
-
-Pipeline Status: {pipeline_status}
-
-═══════════════════════════════════════════════════
-```
-
-### 4. Generate Machine-Readable Status File
-
-Write machine-readable status to: `{planning_artifacts}/pipeline-status.json`
-
-```json
-{
-  "pipeline": "auto-requirements-pipeline",
-  "date": "{date}",
-  "project": "{project_name}",
-  "status": "complete",
-  "steps_completed": 8,
-  "artifacts": {
-    "requirements_analysis": "{planning_artifacts}/requirements-analysis.md",
-    "architecture_analysis": "{planning_artifacts}/current-architecture-analysis.md",
-    "prd": "{planning_artifacts}/prd.md",
-    "epics": "{planning_artifacts}/epics.md",
-    "architecture": "{planning_artifacts}/architecture.md"
-  },
-  "iterations": {
-    "analysis": {analysis_iteration},
-    "architecture": {architecture_iteration},
-    "validation": {validation_iteration}
-  }
-}
-```
-
-This enables downstream tools (including the Auto Story Pipeline) to check pipeline status programmatically.
-
-### 5. Provide Next Steps
-
-**Output:**
-
-```
-🔜 Recommended Next Steps:
-
-1. Review generated artifacts in {planning_artifacts}/
-2. Run Sprint Planning (SP) to organize stories into sprints
-3. Run Auto Story Pipeline to begin implementation
-
-Available commands:
-  - SP (Sprint Planning) — Organize epics/stories into sprints
-  - ASP (Auto Story Pipeline) — Automated story development lifecycle
-```
-
-### 6. Pipeline Complete
-
-**Pipeline execution is COMPLETE. HALT.**
-
----
-
-## SUCCESS METRICS
-
-- All 5 output artifacts verified
-- Machine-readable `pipeline-status.json` generated
-- Completion report generated
-- Next steps provided
-- Pipeline status set to "complete"
-
-## FAILURE MODES
-
-- Missing critical artifacts (PRD, Epics)
-- Not providing completion report
-- Not suggesting next steps

package/src/xmc/workflows/1-analysis/auto-requirements-pipeline/workflow.md

@@ -1,107 +0,0 @@
----
-name: auto-requirements-pipeline
-description: "Automated end-to-end requirements analysis pipeline: requirements analysis → architecture analysis → PRD creation → PRD validation → epic+story creation → architecture design → finalize. Use when the user says 'auto requirements', 'run requirements pipeline', or 'AR'"
----
-
-# Auto Requirements Pipeline Workflow
-
-**Goal:** Execute the complete automated requirements analysis lifecycle — from requirements document (req.md) through analysis, PRD creation, validation, epic/story breakdown, architecture design, and delivery readiness — as a single continuous pipeline with zero user intervention.
-
-**Your Role:** Pipeline Orchestrator. You switch expert roles at each phase:
-
-- **Analyst (xiaofen)** — Requirements analysis and deep research
-- **Architect (xiaojia)** — Architecture analysis and design
-- **PM (xiaochan)** — PRD creation, validation, and epic/story breakdown
-
-- Communicate all responses in {communication_language} and generate all documents in {document_output_language}
-- Execute ALL steps in exact order; do NOT skip steps
-- Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution until the pipeline is COMPLETE or a HALT condition is triggered
-- Each step file loads fresh to combat "lost in the middle" context degradation
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **step-file architecture** for focused execution across a long-running pipeline:
-
-- Each step loads fresh to prevent context loss in long sessions
-- State persists via variables passed between steps
-- Sequential progression through pipeline phases with conditional branching
-- Role switching at each phase boundary
-
-### State Variables
-
-- `{req_file_path}` — Path to the requirements document (default: `{planning_artifacts}/req.md`)
-- `{pipeline_status}` — Current pipeline phase for tracking
-- `{steps_completed}` — Count of steps completed in this pipeline run
-- `{validation_iteration}` — PRD validation loop counter (used in step-05, max 3)
-- `{max_validation_iterations}` — PRD validation retry limit (set in step-05, default 3; higher than analysis/architecture limits because PRD validation delegates to the full 14-step validate-prd workflow)
-- `{analysis_iteration}` — Requirements analysis quality-retry counter (used in step-02, max 2 retries)
-- `{architecture_iteration}` — Architecture analysis quality-retry counter (used in step-03, max 2 retries)
-
-### Output Artifacts
-
-All outputs are written to `{planning_artifacts}/`:
-
-- `requirements-analysis.md` — Deep requirements analysis report
-- `current-architecture-analysis.md` — Existing codebase architecture analysis
-- `prd.md` — Product Requirements Document
-- `epics.md` — Epic and story breakdown
-- `architecture.md` — Technical architecture design
-- `pipeline-status.json` — Machine-readable pipeline completion status
-
-### Architecture Document Types (Important Distinction)
-
-This pipeline produces TWO different architecture documents:
-
-1. **current-architecture-analysis.md** (Step 3 output)
-   - Analysis of the EXISTING codebase
-   - Generated by Architect (xiaojia) analyzing current system patterns
-   - Used as context for designing new features that integrate cleanly
-   - Describes what IS
-
-2. **architecture.md** (Step 7 output)
-   - Technical design for NEW features/requirements
-   - Generated by Architect (xiaojia) designing the solution
-   - References current architecture analysis as context
-   - Describes what SHOULD BE
-
-When step-07 runs, it may find a stale `architecture.md` from a prior pipeline run — in that case, the step explicitly overwrites it (see step-07 section 3).
-
----
-
-## INITIALIZATION
-
-### Configuration Loading
-
-Load config from `{project-root}/_xiaoma/xmc/config.yaml` and resolve:
-
-- `project_name`, `user_name`
-- `communication_language`, `document_output_language`
-- `user_skill_level`
-- `planning_artifacts`, `implementation_artifacts`
-- `date` as system-generated current datetime
-
-### Paths
-
-- `installed_path` = `{project-root}/_xiaoma/xmc/workflows/1-analysis/auto-requirements-pipeline`
-- `validation` = `{installed_path}/checklist.md`
-
-### Related Workflows
-
-These existing workflows contain the detailed logic that pipeline steps delegate to:
-
-- `create_prd_workflow` = `{project-root}/_xiaoma/core/tasks/xiaoma-create-prd/workflow.md` *(Note: uses `core/tasks/` path — `xiaoma-create-prd` originates in the core module, not the xmc module. All other related workflows use `_xiaoma/xmc/workflows/`.)*
-- `validate_prd_workflow` = `{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/xiaoma-validate-prd/workflow.md`
-- `create_epics_workflow` = `{project-root}/_xiaoma/xmc/workflows/3-solutioning/xiaoma-create-epics-and-stories/workflow.md`
-- `create_architecture_workflow` = `{project-root}/_xiaoma/xmc/workflows/3-solutioning/xiaoma-create-architecture/workflow.md`
-
-### Context
-
-- `project_context` = `**/project-context.md` (load if exists)
-
----
-
-## EXECUTION
-
-Read fully and follow: `{project-root}/_xiaoma/xmc/workflows/1-analysis/auto-requirements-pipeline/steps/step-01-init-and-validate.md` to begin the pipeline.

package/src/xmc/workflows/1-analysis/auto-requirements-pipeline/xiaoma-skill-manifest.yaml

@@ -1,3 +0,0 @@
-canonicalId: xiaoma-auto-requirements-pipeline
-type: workflow
-description: "Automated requirements analysis pipeline: analyze → PRD → validate → epics → architecture → ready. Use when the user says 'auto requirements', 'run requirements pipeline', or 'AR'"

package/src/xmc/workflows/1-analysis/research/market-steps/step-01-init.md

@@ -1,182 +0,0 @@
-# Market Research Step 1: Market Research Initialization
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate research content in init step
-- ✅ ALWAYS confirm understanding of user's research goals
-- 📋 YOU ARE A MARKET RESEARCH FACILITATOR, not content generator
-- 💬 FOCUS on clarifying scope and approach
-- 🔍 NO WEB RESEARCH in init - that's for later steps
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Confirm research understanding before proceeding
-- ⚠️ Present [C] continue option after scope clarification
-- 💾 Write initial scope document immediately
-- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
-- 🚫 FORBIDDEN to load next step until C is selected
-
-## CONTEXT BOUNDARIES:
-
-- Current document and frontmatter from main workflow discovery are available
-- Research type = "market" is already set
-- **Research topic = "{{research_topic}}"** - discovered from initial discussion
-- **Research goals = "{{research_goals}}"** - captured from initial discussion
-- Focus on market research scope clarification
-- Web search capabilities are enabled for later steps
-
-## YOUR TASK:
-
-Initialize market research by confirming understanding of {{research_topic}} and establishing clear research scope.
-
-## MARKET RESEARCH INITIALIZATION:
-
-### 1. Confirm Research Understanding
-
-**INITIALIZE - DO NOT RESEARCH YET**
-
-Start with research confirmation:
-"I understand you want to conduct **market research** for **{{research_topic}}** with these goals: {{research_goals}}
-
-**My Understanding of Your Research Needs:**
-
-- **Research Topic**: {{research_topic}}
-- **Research Goals**: {{research_goals}}
-- **Research Type**: Market Research
-- **Approach**: Comprehensive market analysis with source verification
-
-**Market Research Areas We'll Cover:**
-
-- Market size, growth dynamics, and trends
-- Customer insights and behavior analysis
-- Competitive landscape and positioning
-- Strategic recommendations and implementation guidance
-
-**Does this accurately capture what you're looking for?**"
-
-### 2. Refine Research Scope
-
-Gather any clarifications needed:
-
-#### Scope Clarification Questions:
-
-- "Are there specific customer segments or aspects of {{research_topic}} we should prioritize?"
-- "Should we focus on specific geographic regions or global market?"
-- "Is this for market entry, expansion, product development, or other business purpose?"
-- "Any competitors or market segments you specifically want us to analyze?"
-
-### 3. Document Initial Scope
-
-**WRITE IMMEDIATELY TO DOCUMENT**
-
-Write initial research scope to document:
-
-```markdown
-# Market Research: {{research_topic}}
-
-## Research Initialization
-
-### Research Understanding Confirmed
-
-**Topic**: {{research_topic}}
-**Goals**: {{research_goals}}
-**Research Type**: Market Research
-**Date**: {{date}}
-
-### Research Scope
-
-**Market Analysis Focus Areas:**
-
-- Market size, growth projections, and dynamics
-- Customer segments, behavior patterns, and insights
-- Competitive landscape and positioning analysis
-- Strategic recommendations and implementation guidance
-
-**Research Methodology:**
-
-- Current web data with source verification
-- Multiple independent sources for critical claims
-- Confidence level assessment for uncertain data
-- Comprehensive coverage with no critical gaps
-
-### Next Steps
-
-**Research Workflow:**
-
-1. ✅ Initialization and scope setting (current step)
-2. Customer Insights and Behavior Analysis
-3. Competitive Landscape Analysis
-4. Strategic Synthesis and Recommendations
-
-**Research Status**: Scope confirmed, ready to proceed with detailed market analysis
-```
-
-### 4. Present Confirmation and Continue Option
-
-Show initial scope document and present continue option:
-"I've documented our understanding and initial scope for **{{research_topic}}** market research.
-
-**What I've established:**
-
-- Research topic and goals confirmed
-- Market analysis focus areas defined
-- Research methodology verification
-- Clear workflow progression
-
-**Document Status:** Initial scope written to research file for your review
-
-**Ready to begin detailed market research?**
-[C] Continue - Confirm scope and proceed to customer insights analysis
-[Modify] Suggest changes to research scope before proceeding
-
-### 5. Handle User Response
-
-#### If 'C' (Continue):
-
-- Update frontmatter: `stepsCompleted: [1]`
-- Add confirmation note to document: "Scope confirmed by user on {{date}}"
-- Load: `{project-root}/_xiaoma/xmc/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md`
-
-#### If 'Modify':
-
-- Gather user changes to scope
-- Update document with modifications
-- Re-present updated scope for confirmation
-
-## SUCCESS METRICS:
-
-✅ Research topic and goals accurately understood
-✅ Market research scope clearly defined
-✅ Initial scope document written immediately
-✅ User opportunity to review and modify scope
-✅ [C] continue option presented and handled correctly
-✅ Document properly updated with scope confirmation
-
-## FAILURE MODES:
-
-❌ Not confirming understanding of research topic and goals
-❌ Generating research content instead of just scope clarification
-❌ Not writing initial scope document to file
-❌ Not providing opportunity for user to modify scope
-❌ Proceeding to next step without user confirmation
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-
-## INITIALIZATION PRINCIPLES:
-
-This step ensures:
-
-- Clear mutual understanding of research objectives
-- Well-defined research scope and approach
-- Immediate documentation for user review
-- User control over research direction before detailed work begins
-
-## NEXT STEP:
-
-After user confirmation and scope finalization, load `{project-root}/_xiaoma/xmc/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md` to begin detailed market research with customer insights analysis.
-
-Remember: Init steps confirm understanding and scope, not generate research content!