@zeyue0329/xiaoma-cli 1.0.49 → 1.0.66

package/src/xmc/workflows/5-full-pipeline/auto-full-pipeline/steps/step-01-init-and-validate.md

@@ -0,0 +1,152 @@
+---
+name: "step-01-init-and-validate"
+description: "Validate unified environment prerequisites, initialize master pipeline state variables, and prepare for end-to-end execution"
+nextStepFile: "./step-02-run-requirements-pipeline.md"
+---
+
+# Step 1 of 5: Initialize and Validate Environment
+
+**Goal:** Verify all prerequisites for the full requirements-to-delivery pipeline are met, initialize master pipeline state variables, and confirm that both sub-pipelines are accessible.
+
+**Role:** Master Pipeline Orchestrator
+
+---
+
+## EXECUTION SEQUENCE
+
+### 1. Load Configuration
+
+Read 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`
+- `max_fix_iterations` (default: 5 if not set)
+- `date` as system-generated current datetime
+
+**HALT if config not found:** "XiaoMa config not found at `{project-root}/_xiaoma/xmc/config.yaml`. Run `npx @zeyue0329/xiaoma-cli install` first."
+
+### 2. Validate Prerequisites
+
+Check that the following required artifacts and workflows exist:
+
+1. **Requirements Document** — `{planning_artifacts}/req.md` must exist
+   - If missing: HALT — "No requirements document found at `{planning_artifacts}/req.md`. Create a requirements document before running the full pipeline."
+
+2. **Auto Requirements Pipeline** — `{project-root}/_xiaoma/xmc/workflows/1-analysis/auto-requirements-pipeline/workflow.md` must be readable
+   - If missing: HALT — "Auto Requirements Pipeline workflow not found. Verify XiaoMa installation is complete."
+
+3. **Sprint Planning Workflow** — `{project-root}/_xiaoma/xmc/workflows/4-implementation/xiaoma-sprint-planning/workflow.md` must be readable
+   - If missing: HALT — "Sprint Planning workflow not found. Verify XiaoMa installation is complete."
+
+4. **Auto Story Pipeline Batch** — `{project-root}/_xiaoma/xmc/workflows/4-implementation/auto-story-pipeline-batch/workflow.md` must be readable
+   - If missing: HALT — "Auto Story Pipeline Batch workflow not found. Verify XiaoMa installation is complete."
+
+5. **Source Directory** — `src/` directory should exist (warning only if missing)
+   - If missing: Output WARNING — "No `src/` directory found. Architecture analysis may be limited."
+
+### 3. Check Existing Artifacts
+
+Scan for pre-existing output artifacts from prior runs:
+
+- `{planning_artifacts}/requirements-analysis.md`
+- `{planning_artifacts}/current-architecture-analysis.md`
+- `{planning_artifacts}/prd.md`
+- `{planning_artifacts}/epics.md`
+- `{planning_artifacts}/architecture.md`
+- `{planning_artifacts}/pipeline-status.json`
+- `{implementation_artifacts}/sprint-status.yaml`
+
+If any exist, log INFO — "Pre-existing artifact found: {filename}. Will be overwritten during pipeline execution."
+
+### 4. Detect Resume Mode
+
+Check if a prior pipeline run left completed phases that can be skipped:
+
+**Resume Conditions:**
+
+1. **Phase 1 resumable** — ALL of these exist: `{planning_artifacts}/prd.md`, `{planning_artifacts}/epics.md`, `{planning_artifacts}/architecture.md`, AND `{planning_artifacts}/pipeline-status.json` contains `"status": "complete"`
+2. **Phase 2 resumable** — Phase 1 resumable AND `{implementation_artifacts}/sprint-status.yaml` exists with valid YAML containing at least one story entry
+
+**Resume Logic:**
+
+- If Phase 1 AND Phase 2 are resumable:
+  - Set `{phase_1_status}` = "success (resumed)", `{phase_2_status}` = "success (resumed)"
+  - Set `{resume_from_step}` = 4 (skip to Step-04 Story Development)
+  - Output: "🔄 Resume mode detected — Phase 1 and Phase 2 artifacts found from prior run. Skipping to Phase 3 (Story Development)."
+- If Phase 1 only is resumable:
+  - Set `{phase_1_status}` = "success (resumed)"
+  - Set `{resume_from_step}` = 3 (skip to Step-03 Sprint Planning Bridge)
+  - Output: "🔄 Resume mode detected — Phase 1 artifacts found from prior run. Skipping to Phase 2 (Sprint Planning Bridge)."
+- Otherwise:
+  - Set `{resume_from_step}` = 2 (normal — start from Step-02)
+  - Output: "Starting fresh pipeline run."
+
+### 5. Initialize Master Pipeline State Variables
+
+- `{full_pipeline_status}` = "initializing" → "initialized"
+- `{full_steps_completed}` = 1
+- `{phase_1_status}` = value from resume detection, or "pending" for fresh run
+- `{phase_2_status}` = value from resume detection, or "pending" for fresh run
+- `{phase_3_status}` = "pending"
+- Ensure `{planning_artifacts}/` directory exists
+- Ensure `{implementation_artifacts}/` directory exists
+
+### 6. Load Context
+
+- Load `project_context` = `**/project-context.md` (if exists)
+
+### 7. Output Environment Summary
+
+**Output:**
+
+```
+═══════════════════════════════════════════════════
+  Auto Full Pipeline — INITIALIZED
+═══════════════════════════════════════════════════
+
+Project: {project_name}
+User: {user_name}
+Date: {date}
+Language: {communication_language} / {document_output_language}
+
+📋 Requirements: {req_file_path}
+📂 Planning Artifacts: {planning_artifacts}/
+📂 Implementation Artifacts: {implementation_artifacts}/
+
+Mode: {resume_from_step == 2 ? "Fresh Run" : "Resume Mode (skipping to Step " + resume_from_step + ")"}
+
+Pipeline Phases:
+  {resume_from_step <= 2 ? "⬜" : "⏭️"} Phase 1 — Requirements Analysis Pipeline (8 sub-steps)
+  {resume_from_step <= 3 ? "⬜" : "⏭️"} Phase 2 — Sprint Planning Bridge (5 inline steps)
+  ⬜ Phase 3 — Story Development Pipeline (9 sub-steps, batch mode)
+
+Finalization: Step 5 — Unified completion report
+
+Master Step: 1/5
+═══════════════════════════════════════════════════
+```
+
+**Auto-Proceed:** YES — Do NOT wait for user input. Proceed to the step indicated by `{resume_from_step}`:
+- If `{resume_from_step}` == 2: Proceed to step-02 (normal flow)
+- If `{resume_from_step}` == 3: Skip step-02, proceed directly to step-03
+- If `{resume_from_step}` == 4: Skip step-02 and step-03, proceed directly to step-04
+
+---
+
+## SUCCESS METRICS
+
+- Config loaded and all variables resolved
+- Requirements document exists and is readable
+- All three sub-pipeline workflows accessible
+- Master state variables initialized
+- Resume mode correctly detected (if applicable)
+- Environment summary output
+
+## FAILURE MODES
+
+- Missing req.md (cannot proceed without requirements)
+- Missing XiaoMa config (installation incomplete)
+- Missing sub-pipeline workflows (installation incomplete)
+- Directory creation failures

package/src/xmc/workflows/5-full-pipeline/auto-full-pipeline/steps/step-02-run-requirements-pipeline.md

@@ -0,0 +1,120 @@
+---
+name: "step-02-run-requirements-pipeline"
+description: "Execute the complete auto-requirements-pipeline to produce PRD, epics, and architecture design"
+nextStepFile: "./step-03-bridge-sprint-planning.md"
+---
+
+# Step 2 of 5: Execute Requirements Analysis Pipeline
+
+**Goal:** Delegate to the auto-requirements-pipeline to execute the complete requirements analysis lifecycle — from req.md through analysis, PRD creation, validation, epic/story breakdown, and architecture design.
+
+**Role:** Master Pipeline Orchestrator → delegates to auto-requirements-pipeline roles (Analyst xiaofen → Architect xiaojia → PM xiaochan → Architect xiaojia)
+
+---
+
+## EXECUTION SEQUENCE
+
+### 1. Announce Phase Entry
+
+**Output:**
+
+```
+═══════════════════════════════════════════════════
+  Phase 1 of 3 — Requirements Analysis Pipeline
+═══════════════════════════════════════════════════
+
+Starting automated requirements analysis...
+This phase will produce:
+  • Requirements Analysis
+  • Current Architecture Analysis
+  • PRD (Product Requirements Document)
+  • Validated PRD
+  • Epics and User Stories
+  • Architecture Design
+
+Delegating to auto-requirements-pipeline...
+───────────────────────────────────────────────────
+```
+
+### 2. Execute Auto Requirements Pipeline
+
+Read fully and follow: `{project-root}/_xiaoma/xmc/workflows/1-analysis/auto-requirements-pipeline/workflow.md`
+
+**Critical Full Pipeline Mode Instructions:**
+
+- **FULLY AUTOMATED:** Do NOT pause for user input at any point
+- Execute ALL 8 sub-steps of the requirements pipeline sequentially (step-01 through step-08)
+- When any sub-step presents a menu or asks for user confirmation: auto-select the appropriate proceed/continue option
+- When any sub-step delegates to another workflow (create-prd, validate-prd, create-epics, create-architecture): follow the pipeline mode instructions within those delegation steps
+- **IMPORTANT:** The requirements pipeline's step-01 will also validate prerequisites — since we already validated in our step-01, these checks should pass. If they fail unexpectedly, propagate the HALT
+- Continue through ALL 8 sub-steps until the requirements pipeline reaches its own step-08 (finalize) and completes
+- **Do NOT stop after the requirements pipeline's finalize step outputs "Next Steps" guidance** — those next steps are handled by THIS full pipeline automatically
+
+### 3. Verify Requirements Pipeline Output
+
+After the requirements pipeline completes, verify ALL expected output artifacts exist:
+
+1. **Requirements Analysis** — `{planning_artifacts}/requirements-analysis.md` — REQUIRED
+2. **Architecture Analysis** — `{planning_artifacts}/current-architecture-analysis.md` — REQUIRED
+3. **PRD** — `{planning_artifacts}/prd.md` — CRITICAL (must exist)
+4. **Epics** — `{planning_artifacts}/epics.md` — CRITICAL (must exist)
+5. **Architecture Design** — `{planning_artifacts}/architecture.md` — REQUIRED
+6. **Pipeline Status** — `{planning_artifacts}/pipeline-status.json` — OPTIONAL (informational)
+
+**Verification Logic:**
+
+- If `prd.md` AND `epics.md` both exist: `{phase_1_status}` = "success"
+- If either `prd.md` OR `epics.md` is missing: `{phase_1_status}` = "failed" → HALT — "Requirements pipeline failed to produce critical artifacts. Missing: {list missing}. Cannot proceed to development phase."
+- If `requirements-analysis.md`, `current-architecture-analysis.md`, or `architecture.md` is missing: Output WARNING but continue — "Non-critical artifact missing: {filename}. Development may have reduced context."
+
+### 4. Check Pipeline Status JSON (Optional)
+
+If `{planning_artifacts}/pipeline-status.json` exists:
+
+- Read and verify `status` == "complete"
+- If status != "complete": Output WARNING — "Requirements pipeline reported status '{status}' instead of 'complete'. Proceeding with available artifacts."
+
+### 5. Update Master Pipeline State
+
+- `{full_pipeline_status}` = "requirements-phase-complete"
+- `{full_steps_completed}` = 2
+
+**Output:**
+
+```
+───────────────────────────────────────────────────
+  ✅ Phase 1 Complete — Requirements Analysis
+───────────────────────────────────────────────────
+
+Artifacts produced:
+  ✅/❌ requirements-analysis.md
+  ✅/❌ current-architecture-analysis.md
+  ✅/❌ prd.md
+  ✅/❌ epics.md
+  ✅/❌ architecture.md
+
+Phase 1 Status: {phase_1_status}
+Master Step: 2/5
+
+Proceeding to Phase 2 — Sprint Planning Bridge...
+───────────────────────────────────────────────────
+```
+
+**Auto-Proceed:** YES — Do NOT wait for user input. Immediately proceed to step-03.
+
+---
+
+## SUCCESS METRICS
+
+- All 8 sub-steps of requirements pipeline executed
+- PRD and Epics produced (critical)
+- Requirements analysis, architecture analysis, and architecture design produced (important)
+- Pipeline status JSON generated
+- Phase 1 status set to "success"
+
+## FAILURE MODES
+
+- Requirements pipeline HALT propagated (any of its 8 sub-steps)
+- PRD not generated (critical — cannot create stories without PRD)
+- Epics not generated (critical — cannot create sprint status without epics)
+- Validation loop exceeded max iterations in sub-pipeline

package/src/xmc/workflows/5-full-pipeline/auto-full-pipeline/steps/step-03-bridge-sprint-planning.md

@@ -0,0 +1,119 @@
+---
+name: "step-03-bridge-sprint-planning"
+description: "Bridge phase: auto-run sprint planning to generate sprint-status.yaml from epics, connecting requirements analysis output to story development input"
+nextStepFile: "./step-04-run-story-pipeline.md"
+---
+
+# Step 3 of 5: Bridge — Sprint Planning
+
+**Goal:** Generate `sprint-status.yaml` from the epics produced in Phase 1. This bridges the requirements analysis output to the story development pipeline input. Without this step, the story pipeline cannot determine which stories to process.
+
+**Role:** SM (xiaomin) — Scrum Master generating sprint tracking
+
+---
+
+## EXECUTION SEQUENCE
+
+### 1. Announce Phase Entry
+
+**Output:**
+
+```
+═══════════════════════════════════════════════════
+  Phase 2 of 3 — Sprint Planning Bridge
+═══════════════════════════════════════════════════
+
+Generating sprint-status.yaml from epics...
+This bridges requirements → development.
+───────────────────────────────────────────────────
+```
+
+### 2. Verify Epics Input
+
+Confirm `{planning_artifacts}/epics.md` exists and is readable (should always pass since Phase 1 verified this, but re-check for fresh context loading):
+
+- If missing: HALT — "epics.md not found. Phase 1 may have failed. Cannot generate sprint status."
+
+Also check for sharded epics format (safety net only — the auto-requirements-pipeline in Phase 1 produces a single `epics.md` file, not a sharded format):
+
+- If `{planning_artifacts}/epics.md` not found, check for `{planning_artifacts}/epics/index.md`
+- If sharded version found, proceed — the sprint planning workflow handles both formats
+- If neither format found: HALT — "No epics found in any format. Phase 1 may have failed."
+
+### 3. Execute Sprint Planning Workflow
+
+Read fully and follow: `{project-root}/_xiaoma/xmc/workflows/4-implementation/xiaoma-sprint-planning/workflow.md`
+
+**Critical Full Pipeline Mode Instructions:**
+
+- **FULLY AUTOMATED:** Do NOT pause for user input
+- The sprint planning workflow is a **single-file workflow** (`workflow.md`) containing 5 inline `<step>` blocks (not separate step files):
+  1. Parse epic files and extract all work items
+  2. Build sprint status structure (epic-N, story keys, retrospective entries)
+  3. Apply intelligent status detection (check for existing story files)
+  4. Generate `{implementation_artifacts}/sprint-status.yaml`
+  5. Validate and report totals
+- Execute ALL 5 inline steps sequentially within the single workflow file
+- Since this is a fresh pipeline run, all stories should default to "backlog" status (no story files exist yet)
+- When the workflow outputs "Next Steps" guidance at the end, **ignore it** — the next steps are handled by THIS full pipeline automatically
+- **Complete ALL steps without stopping**
+
+### 4. Verify Sprint Status Output
+
+After sprint planning completes, verify:
+
+1. **Sprint Status File** — `{implementation_artifacts}/sprint-status.yaml` must exist
+   - If missing: HALT — "Sprint planning failed to generate sprint-status.yaml. Check epics format and retry."
+
+2. **Content Validation** — Read the generated file and verify:
+   - Contains `development_status:` section
+   - Contains at least one story entry (not just epic entries)
+   - Valid YAML syntax
+
+3. **Count Stories** — Parse and count:
+   - Total epics
+   - Total stories
+   - Stories in "backlog" status (should be all stories for a fresh run)
+
+### 5. Update Master Pipeline State
+
+- `{phase_2_status}` = "success"
+- `{full_pipeline_status}` = "bridge-complete"
+- `{full_steps_completed}` = 3
+
+**Output:**
+
+```
+───────────────────────────────────────────────────
+  ✅ Phase 2 Complete — Sprint Planning Bridge
+───────────────────────────────────────────────────
+
+Sprint Status: {implementation_artifacts}/sprint-status.yaml
+  Total Epics: {epic_count}
+  Total Stories: {story_count}
+  Stories in Backlog: {backlog_count}
+
+Phase 2 Status: {phase_2_status}
+Master Step: 3/5
+
+Proceeding to Phase 3 — Story Development Pipeline (batch mode)...
+───────────────────────────────────────────────────
+```
+
+**Auto-Proceed:** YES — Do NOT wait for user input. Immediately proceed to step-04.
+
+---
+
+## SUCCESS METRICS
+
+- sprint-status.yaml generated with valid YAML
+- All epics and stories from epics.md represented
+- Story counts tallied for pipeline tracking
+- Phase 2 status set to "success"
+
+## FAILURE MODES
+
+- Epics file missing or unreadable
+- Sprint planning workflow fails
+- Generated sprint-status.yaml is malformed or empty
+- No story entries found in sprint status

package/src/xmc/workflows/5-full-pipeline/auto-full-pipeline/steps/step-04-run-story-pipeline.md

@@ -0,0 +1,114 @@
+---
+name: "step-04-run-story-pipeline"
+description: "Execute the auto-story-pipeline-batch to develop, review, test, and deliver all stories using Agent subprocess isolation"
+nextStepFile: "./step-05-finalize.md"
+---
+
+# Step 4 of 5: Execute Story Development Pipeline (Batch)
+
+**Goal:** Delegate to the **auto-story-pipeline-batch** to execute the complete story development lifecycle for ALL stories. Each story is processed in an independent Agent subprocess for context isolation.
+
+**Role:** Master Pipeline Orchestrator → delegates to auto-story-pipeline-batch scheduler
+
+---
+
+## EXECUTION SEQUENCE
+
+### 1. Announce Phase Entry
+
+**Output:**
+
+```
+===============================================
+  Phase 3 of 3 — Story Development Pipeline
+===============================================
+
+Starting automated story development in BATCH mode...
+Using Agent subprocess isolation — each story processed independently.
+Processing all {backlog_count} backlog stories sequentially.
+
+For each story, an independent Agent will:
+  1. Create story file from epics
+  2. Validate story (PM quality gate)
+  3. Develop implementation (TDD)
+  4. Adversarial code review
+  5. QA functional testing
+  6. Fix-and-retest loop (if needed)
+  7. Mark story as done
+
+Delegating to auto-story-pipeline-batch...
+-----------------------------------------------
+```
+
+### 2. Execute Auto Story Pipeline Batch
+
+Read fully and follow: `{project-root}/_xiaoma/xmc/workflows/4-implementation/auto-story-pipeline-batch/workflow.md`
+
+**Critical Full Pipeline Mode Instructions:**
+
+- **FULLY AUTOMATED:** Do NOT pause for user input at any point
+- The batch pipeline will automatically process ALL backlog and ready-for-dev stories
+- Each story is handled by an independent Agent subprocess (isolated context)
+- The batch scheduler stays lightweight — only orchestrating the loop
+- **Do NOT stop after individual story completions** — the batch scheduler handles continuation automatically
+- **If a story Agent fails:** The batch scheduler records the failure and continues to the next story
+- Continue until all stories are processed or the batch pipeline finalizes
+
+### 3. Verify Story Pipeline Output
+
+After the batch pipeline completes:
+
+1. **Re-read sprint-status.yaml** — Fresh read from disk to get final state
+2. **Count final statuses:**
+   - Stories with status "done"
+   - Stories with status "backlog" (not yet processed — may indicate early termination)
+   - Stories with status "in-progress" or "review" (stuck — may indicate HALT)
+3. **Determine Phase 3 result:**
+   - If ALL stories are "done": `{phase_3_status}` = "success"
+   - If SOME stories are "done" but others remain: `{phase_3_status}` = "partial" — Output WARNING with count of remaining stories
+   - If NO stories completed: `{phase_3_status}` = "failed" — Output ERROR
+
+### 4. Update Master Pipeline State
+
+- `{full_pipeline_status}` = "development-phase-complete"
+- `{full_steps_completed}` = 4
+
+**Output:**
+
+```
+-----------------------------------------------
+  Phase 3 Complete — Story Development
+-----------------------------------------------
+
+Stories Completed: {done_count}/{total_story_count}
+Stories Remaining: {remaining_count}
+
+Sprint Status Breakdown:
+  Done: {done_count}
+  Backlog: {backlog_count}
+  In Progress: {in_progress_count}
+  Review: {review_count}
+
+Phase 3 Status: {phase_3_status}
+Master Step: 4/5
+
+Proceeding to Finalization...
+-----------------------------------------------
+```
+
+**Auto-Proceed:** YES — Do NOT wait for user input. Immediately proceed to step-05.
+
+---
+
+## SUCCESS METRICS
+
+- Batch story pipeline executed with Agent subprocess isolation
+- All stories processed through create → validate → develop → review → test → complete
+- All story statuses updated to "done" in sprint-status.yaml
+- Epic statuses updated where all stories complete
+
+## FAILURE MODES
+
+- Batch pipeline unable to find backlog stories
+- Individual story Agent failures (recorded but non-blocking)
+- Partial completion (some stories done, others stuck)