@zeyue0329/xiaoma-cli 1.11.0 → 1.13.0

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

@@ -1,147 +0,0 @@
----
-name: "step-09-cycle-check"
-description: "Check if there are more stories to process. Loop back for batch mode or finalize the pipeline."
-nextStepFile_loop: "./step-02-create-story.md"
-nextStepFile: null
----
-
-# Step 9 of 9: Cycle Check
-
-**Goal:** Determine if the pipeline should process another story (batch mode) or finalize (single mode / all stories done).
-
-**Role:** Pipeline Orchestrator
-
----
-
-## EXECUTION SEQUENCE
-
-### 1. Check Pipeline Mode
-
-**IF `{pipeline_mode}` == "single":**
-- This was a single-story run — proceed directly to finalization (section 4)
-
-**IF `{pipeline_mode}` == "batch":**
-- Continue to section 2 to check for more stories
-
-### 2. Find Next Processable Story
-
-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. First, 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)
-   - Status value equals "backlog"
-   - If found: Set `{found_status}` = "backlog"
-5. If no "backlog" story is found, search again for the FIRST story where:
-   - Key matches the same pattern (not epic, not retrospective)
-   - Status value equals "ready-for-dev"
-   - *(Mirrors step-01's initial story selection: "backlog, or ready-for-dev if no backlog")*
-   - If found: Set `{found_status}` = "ready-for-dev"
-
-### 3. Evaluate Next Story
-
-**IF a backlog or ready-for-dev story is found:**
-- Set `{current_story_key}` = found story key
-- Set `{current_story_path}` = "" (will be set during creation/validation)
-- Set `{fix_iteration}` = 0
-- *(Note: `{found_status}` was already set in section 2 above — "backlog" or "ready-for-dev" — and is used in the progress checkpoint output below.)*
-
-**3.5. Batch Mode Progress Checkpoint**
-
-Before looping back to step-02 for the next story, refresh sprint status counts and output a progress summary:
-
-1. Reload the FULL file: `{sprint_status}` (status counts are stale since step-01 initialization)
-2. Recount all stories by current status:
-   - Update `{backlog_count}` — Stories with status "backlog"
-   - Update `{ready_count}` — Stories with status "ready-for-dev"
-   - Update `{in_progress_count}` — Stories with status "in-progress"
-   - Update `{review_count}` — Stories with status "review"
-   - Update `{done_count}` — Stories with status "done"
-3. Output progress summary:
-
-```
-═══════════════════════════════════════════════════
-  Batch Progress Checkpoint
-═══════════════════════════════════════════════════
-- Stories Completed So Far: {stories_completed}
-- Starting Next Story: {current_story_key} (status: {found_status})
-- Sprint Status (refreshed): Backlog {backlog_count} | Ready {ready_count} | In Progress {in_progress_count} | Review {review_count} | Done {done_count}
-- Pipeline Continuing...
-═══════════════════════════════════════════════════
-```
-
-- **NEXT:** Loop back to step-02 (create story) — step-02's section 1 skip logic will detect "ready-for-dev" stories, skip creation, and route them to step-03 (validate) before development begins
-
-**IF no backlog or ready-for-dev story is found:**
-- All processable stories have been completed — proceed to finalization (section 4)
-
-### 4. Pipeline Finalization
-
-**4.1 Refresh Sprint Status Counters**
-
-Before generating the final report, reload current sprint status to get up-to-date counts (these values were set at pipeline start and may be stale after processing multiple stories in batch mode):
-
-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:
-   - Update `{backlog_count}` — Stories with status "backlog"
-   - Update `{ready_count}` — Stories with status "ready-for-dev"
-   - Update `{in_progress_count}` — Stories with status "in-progress"
-   - Update `{review_count}` — Stories with status "review"
-   - Update `{done_count}` — Stories with status "done"
-
-**4.2 Generate Final Report**
-
-Output:
-```
-Auto Story Pipeline — COMPLETE
-
-Pipeline Summary:
-- Mode: {pipeline_mode}
-- Stories Completed: {stories_completed}
-- Steps Executed: {steps_completed}
-- Pipeline Status: finalized
-
-Stories Processed:
-{for each completed story: key, title, fix iterations used}
-
-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."
-
-**HALT** — Pipeline complete.
-
----
-
-## NEXT STEP
-
-**If more stories to process (batch mode):**
-**NEXT:** Read fully and follow: `{project-root}/_xiaoma/xmc/workflows/4-implementation/auto-story-pipeline/steps/step-02-create-story.md`
-
-**If pipeline complete:**
-**HALT** — Output final report and end.
-
----
-
-## SUCCESS METRICS
-
-- Correct determination of whether to continue or finalize
-- Next story correctly identified for batch mode
-- State variables properly reset for next cycle
-- Comprehensive final report generated
-
-## FAILURE MODES
-
-- Continuing batch mode when no backlog or ready-for-dev stories remain
-- Not resetting state variables for next story cycle
-- Skipping final report generation