@zeyue0329/xiaoma-cli 1.11.0 → 1.13.0

package/src/xmc/workflows/4-implementation/auto-story-pipeline/steps/step-02-create-story.md

@@ -5,7 +5,6 @@ nextStepFile: "./step-03-validate-story.md"
 input_variables:
   - "epic_key"
   - "story_template"
-  - "batch_mode"
 output_variables:
   - "created_story"
   - "story_details"

package/src/xmc/workflows/4-implementation/auto-story-pipeline/steps/step-08-complete-story.md

@@ -1,7 +1,7 @@
 ---
 name: "step-08-complete-story"
 description: "Mark story as done, update sprint-status, and generate completion summary"
-nextStepFile: "./step-09-cycle-check.md"
+nextStepFile: "./step-09-finalize.md"
 ---
 
 # Step 8 of 9: Complete Story
@@ -88,14 +88,13 @@ Pipeline Phases Completed:
 ### 6. Pipeline Status Update
 
 - Set `{pipeline_status}` = "story-completed"
-- Reset `{fix_iteration}` = 0 (for next story if batch mode)
 - Set `{steps_completed}` = `{steps_completed}` + 1
 
 ---
 
 ## NEXT STEP
 
-**NEXT:** Read fully and follow: `{project-root}/_xiaoma/xmc/workflows/4-implementation/auto-story-pipeline/steps/step-09-cycle-check.md`
+**NEXT:** Read fully and follow: `{project-root}/_xiaoma/xmc/workflows/4-implementation/auto-story-pipeline/steps/step-09-finalize.md`
 
 ---
 
@@ -112,4 +111,4 @@ Pipeline Phases Completed:
 - Marking story done without verifying all gates
 - Not updating sprint-status.yaml
 - Not checking epic-level completion
-- Not resetting fix_iteration for next story
+- Not generating completion summary

package/src/xmc/workflows/4-implementation/auto-story-pipeline/steps/step-09-finalize.md

@@ -0,0 +1,69 @@
+---
+name: "step-09-finalize"
+description: "Finalize the single-story pipeline run and output completion report."
+nextStepFile: null
+---
+
+# Step 9 of 9: Pipeline Finalization
+
+**Goal:** Generate the final completion report for this single-story pipeline run.
+
+**Role:** Pipeline Orchestrator
+
+---
+
+## EXECUTION SEQUENCE
+
+### 1. Refresh Sprint Status
+
+1. Load the FULL file: `{sprint_status}`
+2. Read ALL lines from beginning to end — do not skip any content
+3. Recount all stories by current status:
+   - `{backlog_count}` — Stories with status "backlog"
+   - `{ready_count}` — Stories with status "ready-for-dev"
+   - `{in_progress_count}` — Stories with status "in-progress"
+   - `{review_count}` — Stories with status "review"
+   - `{done_count}` — Stories with status "done"
+
+### 2. Generate Final Report
+
+Output:
+```
+Auto Story Pipeline — COMPLETE
+
+Pipeline Summary:
+- Mode: single
+- Story Processed: {current_story_key}
+- Steps Executed: {steps_completed}
+- Pipeline Status: finalized
+
+Sprint Status (current):
+- Backlog: {backlog_count} remaining
+- Ready for Dev: {ready_count}
+- In Progress: {in_progress_count}
+- In Review: {review_count}
+- Done: {done_count}
+
+The automated story development pipeline has finished.
+```
+
+**IF `{backlog_count}` == 0 AND `{ready_count}` == 0 AND `{in_progress_count}` == 0 AND `{review_count}` == 0:**
+- Output: "All stories in the sprint are complete! Consider running epic-retrospective (ER) to review the work."
+
+**IF `{backlog_count}` > 0 OR `{ready_count}` > 0:**
+- Output: "There are still {backlog_count + ready_count} pending stories. Run ASPB (`/xiaoma-auto-story-pipeline-batch`) to process all remaining stories in batch mode, or run ASP again to process the next story."
+
+**HALT** — Pipeline complete.
+
+---
+
+## SUCCESS METRICS
+
+- Final sprint status refreshed from disk
+- Comprehensive completion report generated
+- User informed of remaining stories and next steps
+
+## FAILURE MODES
+
+- Not refreshing sprint status before generating report
+- Skipping final report generation

package/src/xmc/workflows/4-implementation/auto-story-pipeline/workflow.md

@@ -1,11 +1,11 @@
 ---
 name: auto-story-pipeline
-description: "Automated end-to-end story development pipeline: create → validate → develop → review → test → fix → done. Use when the user says 'run auto pipeline', 'automate story development', or 'auto story pipeline'"
+description: "Automated end-to-end story development pipeline (single story): create → validate → develop → review → test → fix → done. Use when the user says 'run auto pipeline', 'automate story development', or 'auto story pipeline'. For batch processing of all stories, use xiaoma-auto-story-pipeline-batch (ASPB) instead."
 ---
 
 # Auto Story Pipeline Workflow
 
-**Goal:** Execute the complete automated story development lifecycle — from story creation through validation, development, code review, testing, bug fixing, and final delivery — as a single continuous pipeline.
+**Goal:** Execute the complete automated story development lifecycle for a **single story** — from story creation through validation, development, code review, testing, bug fixing, and final delivery — as a single continuous pipeline.
 
 **Your Role:** Pipeline Orchestrator. You switch expert roles at each phase:
 - **SM (xiaomin)** — Story creation and sprint coordination
@@ -19,6 +19,8 @@ description: "Automated end-to-end story development pipeline: create → valida
 - 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
 
+> **Note:** This workflow processes a **single story** (or resumes a specific story). For batch processing of all backlog stories, use the **Auto Story Pipeline Batch** skill (`ASPB` or `/xiaoma-auto-story-pipeline-batch`), which uses Agent subprocess isolation for each story.
+
 ---
 
 ## WORKFLOW ARCHITECTURE
@@ -32,22 +34,15 @@ This uses **step-file architecture** for focused execution across a long-running
 
 ### State Variables
 
-- `{pipeline_mode}` — "single" (one story) or "batch" (all backlog stories)
+- `{pipeline_mode}` — "single" (process next backlog story) or "resume" (resume a specific story by key)
 - `{current_story_key}` — Key of story being processed (e.g., "1-2-user-auth")
-- `{current_story_path}` — Full path to current story file (derived in step-01 after resolving `{current_story_key}`; re-set in step-02 skip branch for batch cycles). **CRITICAL:** In batch mode, this variable is reset for each story iteration (step-09 → step-02 loop). Whenever re-reading the story file in subsequent steps (e.g., step-08 final validation, step-03 re-checks), always perform a FRESH read directly from disk using this path variable. Do NOT rely on cached/stale in-memory state from earlier steps in the same cycle, as intermediate steps (step-04, step-05, step-06, step-07) may have modified the file
-- `{fix_iteration}` — Bug fix loop counter (max controlled by `{max_fix_iterations}`, default 5; reset per story)
+- `{current_story_path}` — Full path to current story file (derived in step-01 after resolving `{current_story_key}`). Whenever re-reading the story file in subsequent steps (e.g., step-08 final validation, step-03 re-checks), always perform a FRESH read directly from disk using this path variable. Do NOT rely on cached/stale in-memory state from earlier steps, as intermediate steps (step-04, step-05, step-06, step-07) may have modified the file
+- `{fix_iteration}` — Bug fix loop counter (max controlled by `{max_fix_iterations}`, default 5)
 - `{max_fix_iterations}` — Maximum fix-and-retest cycles per story (configurable via `max_fix_iterations` in config.yaml; default 5 if not set)
 - `{fix_source}` — Origin of failures being fixed in step-07: "code-review" (step-05 routed here with unresolvable issues), "qa-testing" (step-06 routed here with test failures), or "mixed" (both code review and QA issues); set in step-07 section 2; determines post-fix routing (code-review/mixed → inline targeted re-check before step-08; qa-testing → step-08 directly)
-- `{stories_completed}` — Count of stories completed in this pipeline run
 - `{pipeline_status}` — Current pipeline phase for tracking
-- `{validation_attempt}` — Story validation attempt counter (used in step-03, max 3; re-initialized at start of step-03 for each story)
-- `{steps_completed}` — Count of pipeline step files executed in this run (initialized to 0 in step-01; accumulates across all stories in batch mode)
-- `{backlog_count}` — Count of stories with status "backlog" (initialized in step-01; refreshed in step-09 batch checkpoints and final finalization)
-- `{ready_count}` — Count of stories with status "ready-for-dev" (initialized in step-01; refreshed in step-09)
-- `{in_progress_count}` — Count of stories with status "in-progress" (initialized in step-01; refreshed in step-09)
-- `{review_count}` — Count of stories with status "review" (initialized in step-01; refreshed in step-09)
-- `{done_count}` — Count of stories with status "done" (initialized in step-01; refreshed in step-09)
-- `{found_status}` — Status of the next processable story found during step-09 section 2 search: "backlog" or "ready-for-dev"; explicitly set alongside `{current_story_key}` when a story is selected; used in section 3.5 progress checkpoint output; local to step-09 and not persisted between stories
+- `{validation_attempt}` — Story validation attempt counter (used in step-03, max 3; re-initialized at start of step-03)
+- `{steps_completed}` — Count of pipeline step files executed in this run (initialized to 0 in step-01)
 
 ### Status Machine
 

package/src/xmc/workflows/4-implementation/auto-story-pipeline/xiaoma-skill-manifest.yaml

@@ -1,3 +1,3 @@
 canonicalId: xiaoma-auto-story-pipeline
 type: workflow
-description: "Automated end-to-end story development pipeline. Use when the user says 'run auto pipeline', 'automate story development', or 'auto story pipeline'"
+description: "Automated end-to-end story development pipeline (single story). Use when the user says 'run auto pipeline', 'automate story development', or 'auto story pipeline'. For batch processing, use xiaoma-auto-story-pipeline-batch (ASPB)."

package/src/xmc/workflows/4-implementation/auto-story-pipeline-batch/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: auto-story-pipeline-batch
+description: "Batch automated story development pipeline with Agent subprocess isolation. Processes ALL backlog stories sequentially, each in an independent Agent context. Use when the user says 'batch story pipeline', 'ASB', 'auto story batch', or 'batch auto pipeline'"
+---
+
+Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/4-implementation/auto-story-pipeline-batch/workflow.md

@@ -0,0 +1,333 @@
+---
+name: auto-story-pipeline-batch
+description: "Batch automated story development pipeline with Agent subprocess isolation. Each story is processed in an independent Agent context to prevent context bloat. Use when the user says 'batch story pipeline', 'ASPB', 'auto story batch', or 'batch auto pipeline'"
+---
+
+# Auto Story Pipeline — Batch Mode (Agent Subprocess Isolation)
+
+**Goal:** Execute the complete automated story development lifecycle for ALL backlog stories — processing each story in an **independent Agent subprocess** to prevent context bloat and ensure isolation. Fully automatic from start to finish, zero human intervention until the queue is empty.
+
+**Your Role:** Pipeline Batch Scheduler. You coordinate the batch loop, delegating each story's full lifecycle (create → validate → develop → review → test → fix → done) to independent Agent subprocesses. You stay lightweight — query queue, launch Agent, read results, continue or finalize.
+
+- Communicate all responses in {communication_language} and generate all documents in {document_output_language}
+- Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution until ALL stories are processed or a HALT condition is triggered
+- **Fully automatic, no human intervention** — From start to finish, user needs no commands
+
+---
+
+## Core Architecture: Agent-Isolated Processing
+
+**Why this architecture:** Each story is delegated to an **independent Agent subprocess**. Agents naturally have isolated context spaces, releasing upon completion without polluting the main conversation. The main conversation only handles lightweight scheduling loops.
+
+```
+Main conversation (scheduler, minimal context)
+  ├── Agent #1 → Process Story A (isolated context, released after completion)
+  ├── Agent #2 → Process Story B (isolated context, released after completion)
+  ├── Agent #3 → Process Story C (isolated context, released after completion)
+  └── ...until queue is empty
+```
+
+### Core Rules (Strictly Follow)
+
+1. **Each story processed by independent Agent** — Use Agent tool to launch general-purpose subprocess, pass complete story info and processing instructions to Agent, Agent independently completes the full story lifecycle (step-02 through step-08)
+2. **Main loop stays lightweight** — Main conversation only: query sprint-status → launch Agent → read Agent results → query remaining → continue or end
+3. **Serial processing** — Process one story at a time, wait for Agent completion before next, avoid concurrent modification conflicts
+4. **Fully automatic, no human intervention** — From start to finish, user needs no commands
+
+---
+
+## 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`
+- `max_fix_iterations` (default: 5 if not set)
+- `date` as system-generated current datetime
+
+### Paths
+
+- `story_pipeline_path` = `{project-root}/_xiaoma/xmc/workflows/4-implementation/auto-story-pipeline`
+- `sprint_status` = `{implementation_artifacts}/sprint-status.yaml`
+- `validation_checklist` = `{story_pipeline_path}/checklist.md`
+
+### Related Workflows (Passed to Agent)
+
+These paths will be passed to each Agent subprocess so it can delegate to existing workflow logic:
+
+- `create_story_workflow` = `{project-root}/_xiaoma/xmc/workflows/4-implementation/xiaoma-create-story/workflow.md`
+- `dev_story_workflow` = `{project-root}/_xiaoma/xmc/workflows/4-implementation/xiaoma-dev-story/workflow.md`
+- `code_review_workflow` = `{project-root}/_xiaoma/xmc/workflows/4-implementation/xiaoma-code-review/workflow.md`
+- `qa_test_workflow` = `{project-root}/_xiaoma/xmc/workflows/xiaoma-qa-generate-e2e-tests/workflow.md`
+
+### Context
+
+- `project_context` = `**/project-context.md` (load if exists)
+
+---
+
+## WORKFLOW
+
+<workflow>
+
+<step n="1" goal="Validate environment, analyze sprint status, and display overview">
+
+### 1.1 Validate Prerequisites
+
+Check that the following required artifacts exist:
+
+1. **Epics File** — `{planning_artifacts}/*epic*.md` must exist
+   - If missing: HALT — "No epics file found. Run the planning workflow first to create epics."
+
+2. **Sprint Status File** — `{sprint_status}` must exist
+   - If missing:
+     a. Output INFO — "sprint-status.yaml not found. Auto-generating via Sprint Planning..."
+     b. Read and follow the sprint-planning workflow: `{project-root}/_xiaoma/xmc/workflows/4-implementation/xiaoma-sprint-planning/workflow.md`
+     c. After sprint-planning completes, verify `{sprint_status}` now exists
+     d. If still missing: HALT — "Failed to auto-generate sprint-status.yaml. Run Sprint Planning (SP) manually."
+
+3. **Planning Artifacts** — At least one of `{planning_artifacts}/*prd*.md` or `{planning_artifacts}/*architecture*.md` should exist
+   - If missing: Output warning but continue — "Planning documents not found. Story creation may have limited context."
+
+### 1.2 Analyze Sprint Status
+
+1. Load the FULL file: `{sprint_status}`
+2. Read ALL lines from beginning to end — do not skip any content
+3. Parse the `development_status` section completely
+4. Count stories by status:
+   - `backlog_count` — Stories with status "backlog"
+   - `ready_count` — Stories with status "ready-for-dev"
+   - `in_progress_count` — Stories with status "in-progress"
+   - `review_count` — Stories with status "review"
+   - `done_count` — Stories with status "done"
+5. If `backlog_count` == 0 AND `ready_count` == 0:
+   - HALT — "No backlog or ready-for-dev stories found. All stories are either in-progress, in review, or done."
+
+### 1.3 Display Overview and Begin
+
+**Output:**
+
+```
+===============================================
+  Auto Story Pipeline — Batch Mode
+  (Agent Subprocess Isolation)
+===============================================
+
+Sprint Status Summary:
+- Backlog: {backlog_count} stories
+- Ready for Dev: {ready_count} stories
+- In Progress: {in_progress_count} stories
+- Review: {review_count} stories
+- Done: {done_count} stories
+
+Processing all {backlog_count + ready_count} pending stories sequentially.
+Each story will be processed in an independent Agent subprocess.
+
+Starting fully automatic batch processing...
+-----------------------------------------------
+```
+
+Initialize tracking variables:
+- `stories_completed` = 0
+- `stories_failed` = 0
+- `failed_story_keys` = [] (empty list — tracks story keys that failed, to avoid infinite loops)
+- `story_results` = [] (empty list — accumulates result summaries for the final report)
+
+Enter Step 2 to start the batch loop.
+
+</step>
+
+<step n="2" goal="Loop: process each story in an independent Agent subprocess (fully automatic)">
+
+<!-- Loop start: find the next processable story -->
+
+### 2.1 Find Next Processable Story
+
+1. Load the FULL file: `{sprint_status}` (always fresh read from disk)
+2. Read ALL lines from beginning to end
+3. Parse the `development_status` section completely
+4. Find the FIRST story (reading top to bottom) where:
+   - Key matches pattern: number-number-name (e.g., "1-2-user-auth")
+   - NOT an epic key (epic-X) or retrospective (epic-X-retrospective)
+   - Key is NOT in the `failed_story_keys` list (skip previously failed stories to avoid infinite loops)
+   - Status value equals "backlog"
+5. If no "backlog" story found, search again for the FIRST story with status "ready-for-dev" (also skipping `failed_story_keys`)
+6. If no processable story found: queue is empty, go to Step 3
+
+### 2.2 Output Progress
+
+```
+Processing story: {current_story_key} (status: {current_story_status})
+Stories completed so far: {stories_completed}
+```
+
+### 2.3 Launch Independent Agent Subprocess
+
+<critical>
+
+Use the Agent tool to launch a **general-purpose subprocess** to process this story.
+
+The Agent's prompt MUST contain the following complete information for independent work:
+
+**1. Story Information:**
+- Story key: `{current_story_key}`
+- Current status: `{current_story_status}` (backlog or ready-for-dev)
+- Story file path: `{implementation_artifacts}/{current_story_key}.md`
+
+**2. Configuration (inline all resolved values):**
+- project_name: `{project_name}`
+- user_name: `{user_name}`
+- communication_language: `{communication_language}`
+- document_output_language: `{document_output_language}`
+- user_skill_level: `{user_skill_level}`
+- planning_artifacts: `{planning_artifacts}`
+- implementation_artifacts: `{implementation_artifacts}`
+- sprint_status: `{sprint_status}`
+- max_fix_iterations: `{max_fix_iterations}`
+- date: current datetime
+
+**3. Workflow Paths (for delegation):**
+- create_story_workflow: `{create_story_workflow}`
+- dev_story_workflow: `{dev_story_workflow}`
+- code_review_workflow: `{code_review_workflow}`
+- qa_test_workflow: `{qa_test_workflow}`
+- validation_checklist: `{validation_checklist}`
+
+**4. Project Context:**
+- Include the content of project-context.md if it exists (pass the actual content, not just the path)
+
+**5. Processing Instructions:**
+
+Tell the Agent to execute the following steps sequentially for the story. The Agent should read and follow each step file from the story pipeline:
+
+a. **IF story status is "backlog":** Read and follow `{story_pipeline_path}/steps/step-02-create-story.md` — Create the user story file
+b. Read and follow `{story_pipeline_path}/steps/step-03-validate-story.md` — PM validation (quality gate, max 3 attempts)
+c. Read and follow `{story_pipeline_path}/steps/step-04-develop-story.md` — Development implementation (TDD)
+d. Read and follow `{story_pipeline_path}/steps/step-05-code-review.md` — Adversarial code review (auto-fix HIGH/MEDIUM issues)
+e. Read and follow `{story_pipeline_path}/steps/step-06-test-story.md` — QA functional testing (real data, no mocks)
+f. Read and follow `{story_pipeline_path}/steps/step-07-fix-and-retest.md` — Fix-and-retest loop if needed (max {max_fix_iterations} iterations)
+g. Read and follow `{story_pipeline_path}/steps/step-08-complete-story.md` — Mark story done, update sprint-status.yaml
+
+**Important instructions for the Agent:**
+- Execute ALL steps in exact order; do NOT skip steps
+- If story status is "ready-for-dev", skip step-02 (creation) and start at step-03 (validation)
+- **CRITICAL: After completing step-08, STOP immediately. Do NOT continue to step-09-finalize.md.** Step-08's "NEXT STEP" section points to step-09, but you must ignore that instruction. Step-09 is for single-story mode finalization only. In batch mode, the main scheduler handles finalization. After step-08 completes, return the STORY_RESULT summary below and exit.
+- Do NOT stop because of "milestones" or "significant progress" — continue until the story is DONE (step-08 completed) or a HALT condition is triggered
+- Each step file loads fresh to combat context degradation — read each step file fully before executing
+- When reading the story file in later steps, always perform a FRESH read from disk (the file may have been modified by earlier steps)
+- Initialize `fix_iteration` = 0 and `validation_attempt` = 0 at the start
+
+**6. Return Format:**
+When done, return a structured summary:
+```
+STORY_RESULT:
+- story_key: {story_key}
+- final_status: done | halted | failed
+- fix_iterations_used: {count}
+- validation_attempts: {count}
+- files_modified: [list of files]
+- summary: {one-line description of what was done}
+- error: {error message if halted/failed, empty otherwise}
+```
+
+</critical>
+
+### 2.4 Read Agent Result and Handle Errors
+
+Read the Agent's returned processing result summary.
+
+**IF the Agent succeeded (returned `final_status: done`):**
+- Increment `stories_completed` counter
+- Record the story result in `story_results` list
+
+**IF the Agent failed or halted (returned `final_status: failed` or `halted`, or produced no result / error):**
+- Increment `stories_failed` counter
+- Add the story key to `failed_story_keys` list (prevents re-selecting this story in the next loop iteration)
+- Record the failure result in `story_results` list (including error details)
+- **Do NOT halt the batch** — continue to the next story
+- Output: "Story {current_story_key} failed/halted. Skipping and continuing to next story."
+
+### 2.5 Output Progress
+
+1. Output brief one-line result for this story
+
+### 2.6 Refresh Sprint Status and Check Remaining
+
+1. Re-read `{sprint_status}` from disk (fresh read)
+2. Recount stories by status:
+   - Update `backlog_count`, `ready_count`, `in_progress_count`, `review_count`, `done_count`
+3. Output batch progress checkpoint:
+
+```
+===============================================
+  Batch Progress Checkpoint
+===============================================
+- Stories Completed So Far: {stories_completed}
+- Sprint Status (refreshed): Backlog {backlog_count} | Ready {ready_count} | In Progress {in_progress_count} | Review {review_count} | Done {done_count}
+- Pipeline Continuing...
+===============================================
+```
+
+4. If `backlog_count` > 0 OR `ready_count` > 0: Continue loop — return to Step 2.1
+5. If `backlog_count` == 0 AND `ready_count` == 0: Queue is empty, go to Step 3
+
+</step>
+
+<step n="3" goal="Output final batch processing report">
+
+### 3.1 Refresh Sprint Status
+
+1. Load the FULL file: `{sprint_status}` (final fresh read)
+2. Recount all stories by status
+
+### 3.2 Generate Final Report
+
+**Output:**
+
+```
+===============================================
+  Auto Story Pipeline (Batch) — COMPLETE
+===============================================
+
+Pipeline Summary:
+- Mode: Batch (Agent Subprocess Isolation)
+- Stories Completed: {stories_completed}
+- Pipeline Status: finalized
+
+Stories Processed:
+{for each completed story: key, final_status, fix_iterations_used, summary}
+
+Sprint Status (current):
+- Backlog: {backlog_count} remaining
+- Ready for Dev: {ready_count}
+- In Progress: {in_progress_count}
+- In Review: {review_count}
+- Done: {done_count}
+
+The automated batch story development pipeline has finished.
+===============================================
+```
+
+**IF `backlog_count` == 0 AND `ready_count` == 0 AND `in_progress_count` == 0 AND `review_count` == 0:**
+- Output: "All stories in the sprint are complete! Consider running epic-retrospective (ER) to review the work."
+
+**HALT** — Pipeline complete.
+
+</step>
+
+</workflow>
+
+---
+
+## Important Notes
+
+1. **Agent isolation is key** — Each story is processed in an independent Agent subprocess with isolated context. No `/clear` needed, no mutual interference between stories
+2. **Fully automatic** — User only calls once, then fully automatic until all stories are processed
+3. **Serial safety** — One story at a time, avoid concurrent modifications to the same codebase
+4. **Error tolerance** — If an Agent fails to process a story, the story status remains unchanged in sprint-status.yaml. The main loop records the failure and continues to the next story
+5. **Agent prompt quality** — The prompt passed to each Agent must include complete story info + all configuration paths + processing instructions + return format, enabling fully independent work
+6. **Reuses existing step files** — Agents read and follow the same step-02 through step-08 files from auto-story-pipeline, avoiding code duplication

package/src/xmc/workflows/4-implementation/auto-story-pipeline-batch/xiaoma-skill-manifest.yaml

@@ -0,0 +1,3 @@
+canonicalId: auto-story-pipeline-batch
+type: workflow
+description: "Batch automated story development pipeline with Agent subprocess isolation. Each story is processed in an independent Agent context to prevent context bloat. Use when the user says 'batch story pipeline', 'ASB', 'auto story batch', or 'batch auto pipeline'"

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

@@ -40,8 +40,8 @@ Check that the following required artifacts and workflows exist:
 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** — `{project-root}/_xiaoma/xmc/workflows/4-implementation/auto-story-pipeline/workflow.md` must be readable
-   - If missing: HALT — "Auto Story Pipeline 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."