@zeyue0329/xiaoma-cli 1.8.3 → 1.8.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
package/src/xmc/workflows/4-implementation/auto-story-pipeline/steps/step-01-init-and-validate.md
CHANGED
|
@@ -18,12 +18,19 @@ nextStepFile: "./step-02-create-story.md"
|
|
|
18
18
|
|
|
19
19
|
Check that the following required artifacts exist:
|
|
20
20
|
|
|
21
|
-
1. **
|
|
22
|
-
- If missing: HALT — "No sprint-status.yaml found. Run `sprint-planning` (SP) first to initialize sprint tracking."
|
|
23
|
-
|
|
24
|
-
2. **Epics File** — `{planning_artifacts}/*epic*.md` must exist
|
|
21
|
+
1. **Epics File** — `{planning_artifacts}/*epic*.md` must exist
|
|
25
22
|
- If missing: HALT — "No epics file found. Run the planning workflow first to create epics."
|
|
26
23
|
|
|
24
|
+
2. **Sprint Status File** — `{sprint_status}` must exist
|
|
25
|
+
- If missing:
|
|
26
|
+
a. Output INFO — "sprint-status.yaml not found. Auto-generating via Sprint Planning..."
|
|
27
|
+
b. Verify epics file exists (checked in step 1 above) — if epics are present, proceed with auto-generation
|
|
28
|
+
c. Read and follow the sprint-planning workflow: `{project-root}/_xiaoma/xmc/workflows/4-implementation/xiaoma-sprint-planning/workflow.md`
|
|
29
|
+
d. Execute the sprint-planning workflow fully — it will parse epics, detect story statuses, and generate `{sprint_status}`
|
|
30
|
+
e. After sprint-planning completes, verify `{sprint_status}` now exists
|
|
31
|
+
f. If `{sprint_status}` still does not exist after auto-generation attempt: HALT — "Failed to auto-generate sprint-status.yaml. Check that epics are correctly formatted and try running Sprint Planning (SP) manually: /xiaoma-sprint-planning"
|
|
32
|
+
g. Output INFO — "sprint-status.yaml auto-generated successfully. Continuing pipeline..."
|
|
33
|
+
|
|
27
34
|
3. **Planning Artifacts** — At least one of `{planning_artifacts}/*prd*.md` or `{planning_artifacts}/*architecture*.md` should exist
|
|
28
35
|
- If missing: Output warning but continue — "Planning documents not found. Story creation may have limited context."
|
|
29
36
|
|
|
@@ -163,6 +170,7 @@ Based on the starting step determined in section 5 above, proceed to the correct
|
|
|
163
170
|
|
|
164
171
|
## FAILURE MODES
|
|
165
172
|
|
|
166
|
-
- Proceeding without sprint-status.yaml
|
|
173
|
+
- Proceeding without sprint-status.yaml AND without auto-generating it
|
|
174
|
+
- Auto-generation of sprint-status.yaml fails silently without HALT
|
|
167
175
|
- Not initializing state variables
|
|
168
176
|
- Starting batch mode with no backlog stories
|