ma-agents 3.4.8 → 3.5.0

package/lib/bmad-extension/module-help.csv

@@ -3,6 +3,7 @@ ma-skills,anytime,SRE Agent,bmad-ma-agent-sre,,skill:bmad-ma-agent-sre,bmad-ma-a
 ma-skills,anytime,DevOps Agent,bmad-ma-agent-devops,,skill:bmad-ma-agent-devops,bmad-ma-agent-devops,false,bmm-devops,,"DevOps Engineer agent for CI/CD pipeline automation, Infrastructure as Code, and cloud-native technologies.",output_folder,"agent customization",
 ma-skills,anytime,Cyber Agent,bmad-ma-agent-cyber,,skill:bmad-ma-agent-cyber,bmad-ma-agent-cyber,false,bmm-cyber,,"Cyber Security Analyst agent for vulnerability assessment, threat modeling, and system hardening.",output_folder,"agent customization",
 ma-skills,anytime,MIL-498 Agent,bmad-ma-agent-mil498,,skill:bmad-ma-agent-mil498,bmad-ma-agent-mil498,false,bmm-mil498,,"MIL-STD-498 Documentation Expert agent for defense industry standards and Data Item Descriptions.",output_folder,"agent customization",
+ma-skills,anytime,ML Scientist Agent,bmad-ma-agent-ml,,skill:bmad-ma-agent-ml,bmad-ma-agent-ml,false,bmm-demerzel,,"Machine Learning Scientist agent for hypothesis-driven ML lifecycle with scientific rigor.",output_folder,"agent customization",
 ma-skills,4-implementation,Generate SSS,mil498-sss,,skill:mil498-sss,bmad-mil-generate-sss,false,bmm-mil498,,"Generate a MIL-STD-498 System/Subsystem Specification (SSS).",output_folder,"MIL-498 document",
 ma-skills,4-implementation,Generate SSDD,mil498-ssdd,,skill:mil498-ssdd,bmad-mil-generate-ssdd,false,bmm-mil498,,"Generate a MIL-STD-498 System/Subsystem Design Description (SSDD).",output_folder,"MIL-498 document",
 ma-skills,4-implementation,Generate OCD,mil498-ocd,,skill:mil498-ocd,bmad-mil-generate-ocd,false,bmm-mil498,,"Generate a MIL-STD-498 Operational Concept Description (OCD).",output_folder,"MIL-498 document",
@@ -10,6 +11,7 @@ ma-skills,4-implementation,Generate SDP,mil498-sdp,,skill:mil498-sdp,bmad-mil-ge
 ma-skills,4-implementation,Generate SRS,mil498-srs,,skill:mil498-srs,bmad-mil-generate-srs,false,bmm-mil498,,"Generate a MIL-STD-498 Software Requirements Specification (SRS).",output_folder,"MIL-498 document",
 ma-skills,4-implementation,Generate SDD,mil498-sdd,,skill:mil498-sdd,bmad-mil-generate-sdd,false,bmm-mil498,,"Generate a MIL-STD-498 Software Design Description (SDD).",output_folder,"MIL-498 document",
 ma-skills,4-implementation,Generate STD,mil498-std,,skill:mil498-std,bmad-mil-generate-std,false,bmm-mil498,,"Generate a MIL-STD-498 Software Test Description (STD).",output_folder,"MIL-498 document",
+ma-skills,4-implementation,Requirements Quality,mil498-requirement-quality,,skill:mil498-requirement-quality,mil498-requirement-quality,false,bmm-mil498,,"Evaluate requirements against 14 quality criteria — produces per-requirement audit table, Missing Elements report, and Overall Quality Score.",output_folder,"requirements audit",
 ma-skills,4-implementation,Check Deployment Status,sre-check-deployment-status,,skill:sre-check-deployment-status,bmad-sre-check-deployment-status,false,bmm-sre,,"Check deployment status across Kubernetes namespaces and report issues.",output_folder,"status report",
 ma-skills,4-implementation,Check Secrets,sre-check-secrets,,skill:sre-check-secrets,bmad-sre-check-secrets,false,bmm-sre,,"Debug and verify secret configurations in Kubernetes clusters.",output_folder,"status report",
 ma-skills,4-implementation,Check System Status,sre-check-system-status,,skill:sre-check-system-status,bmad-sre-check-system-status,false,bmm-sre,,"Perform overall system status check across cluster resources.",output_folder,"status report",
@@ -29,26 +31,29 @@ ma-skills,4-implementation,Vault Secrets,cyber-vault-secrets,,skill:cyber-vault-
 ma-skills,4-implementation,Verify Docker Users,cyber-verify-docker-users,,skill:cyber-verify-docker-users,bmad-cyber-verify-docker-users,false,bmm-cyber,,"Verify Docker image user configurations and hardening compliance.",output_folder,"verification report",
 ma-skills,4-implementation,Verify Image Signature,cyber-verify-image-signature,,skill:cyber-verify-image-signature,bmad-cyber-verify-image-signature,false,bmm-cyber,,"Verify Docker image signatures for supply chain integrity.",output_folder,"verification report",
 ma-skills,4-implementation,Vulnerability Scan,cyber-vulnerability-scan,,skill:cyber-vulnerability-scan,bmad-cyber-vulnerability-scan,false,bmm-cyber,,"Orchestrate vulnerability scanning across project components.",output_folder,"scan report",
-ma-skills,4-implementation,Create Bug Story,create-bug-story,,skill:create-bug-story,create-bug-story,false,bmm-dev,,"Create a structured bug story with severity and type classification, add to backlog.yaml.",_bmad-output/implementation-artifacts,"bug story",
-ma-skills,4-implementation,Add Sprint,add-sprint,,skill:add-sprint,add-sprint,false,bmm-sm,,"Create a new sprint entity with capacity limits and optional ISO dates (YAML schema).",_bmad-output/implementation-artifacts/sprints,"sprint entity",
-ma-skills,4-implementation,Modify Sprint,modify-sprint,,skill:modify-sprint,modify-sprint,false,bmm-sm,,"Modify existing sprint — add/remove items, change capacity, update metadata.",_bmad-output/implementation-artifacts,"sprint plan",
-ma-skills,4-implementation,Add to Sprint,add-to-sprint,,skill:add-to-sprint,add-to-sprint,false,bmm-sm,,"Assign backlog items to a sprint from flat prioritized backlog.",_bmad-output/implementation-artifacts,"sprint plan",
+ma-skills,4-implementation,ML Ideation,ml-ideation,,skill:ml-ideation,ml-ideation,false,bmm-demerzel,,"Frame an ML research problem, produce a Research Thesis and PRD.",_bmad-output,"research thesis",
+ma-skills,4-implementation,ML EDA,ml-eda,,skill:ml-eda,ml-eda,false,bmm-demerzel,,"Exploratory Data Analysis — establish baselines and produce an EDA report.",_bmad-output,"EDA report",
+ma-skills,4-implementation,ML Architecture,ml-architecture,,skill:ml-architecture,ml-architecture,false,bmm-demerzel,,"Define model architecture, stack, and experiment tracking strategy.",_bmad-output,"architecture spec",
+ma-skills,4-implementation,ML Detailed Design,ml-detailed-design,,skill:ml-detailed-design,ml-detailed-design,false,bmm-demerzel,,"Break implementation into INF-* and EXP-* tasks.",_bmad-output,"task breakdown",
+ma-skills,4-implementation,ML TechSpec,ml-techspec,,skill:ml-techspec,ml-techspec,false,bmm-demerzel,,"Lock experiment parameters and performance tiers before training.",_bmad-output,"TechSpec",
+ma-skills,4-implementation,ML Infra,ml-infra,,skill:ml-infra,ml-infra,false,bmm-demerzel,,"Build ML infrastructure, manage dependencies, and run smoke tests.",_bmad-output,"infra report",
+ma-skills,4-implementation,ML Experiment,ml-experiment,,skill:ml-experiment,ml-experiment,false,bmm-demerzel,,"Execute training experiments against locked TechSpec and log metrics.",_bmad-output,"experiment log",
+ma-skills,4-implementation,ML Analysis,ml-analysis,,skill:ml-analysis,ml-analysis,false,bmm-demerzel,,"Evaluate experiment outcomes against TechSpec success tiers.",_bmad-output,"analysis report",
+ma-skills,4-implementation,ML Hyperparameter Optimization,ml-hparam,,skill:ml-hparam,ml-hparam,false,bmm-demerzel,,"Automated hyperparameter optimization (Optuna, W&B Sweeps, Ray Tune).",_bmad-output,"hparam report",
+ma-skills,4-implementation,ML Revision,ml-revision,,skill:ml-revision,ml-revision,false,bmm-demerzel,,"Amend hypothesis and requirements based on experiment findings.",_bmad-output,"revision doc",
+ma-skills,4-implementation,ML Advise,ml-advise,,skill:ml-advise,ml-advise,false,bmm-demerzel,,"Search past experiments, surface findings and failure warnings.",_bmad-output,"advisory report",
+ma-skills,4-implementation,ML Retrospective,ml-retrospective,,skill:ml-retrospective,ml-retrospective,false,bmm-demerzel,,"Capture session learnings and update project context.",_bmad-output,"retrospective",
+ma-skills,4-implementation,Create Bug Story,create-bug-story,,skill:create-bug-story,create-bug-story,false,bmm-dev,,"Create a structured bug story from a detected defect and add to backlog.",_bmad-output/implementation-artifacts,"bug story",
+ma-skills,4-implementation,Dev Story,bmad-dev-story,,skill:bmad-dev-story,bmad-dev-story,false,bmm-dev,,"Execute story implementation following a context filled story spec file.",_bmad-output/implementation-artifacts,"story implementation",
+ma-skills,4-implementation,Sprint Planning,bmad-sprint-planning,,skill:bmad-sprint-planning,bmad-sprint-planning,false,bmm-sm,,"Bootstrap or update the unified sprint-status.yaml from epics with three sections (epics, backlog, sprints).",_bmad-output/implementation-artifacts,"sprint plan",
+ma-skills,4-implementation,Generate Backlog,generate-backlog,,skill:generate-backlog,generate-backlog,false,bmm-sm,,"Generate or refresh the backlog section of sprint-status.yaml from epics and bug stories.",_bmad-output/implementation-artifacts,"backlog",
+ma-skills,4-implementation,Add Sprint,add-sprint,,skill:add-sprint,add-sprint,false,bmm-sm,,"Create a new sprint entry in the sprints section of sprint-status.yaml with capacity limits, optional ISO dates, and auto-incremented ID.",_bmad-output/implementation-artifacts,"sprint plan",
+ma-skills,4-implementation,Add to Sprint,add-to-sprint,,skill:add-to-sprint,add-to-sprint,false,bmm-sm,,"Move backlog items to a sprint in the unified sprint-status.yaml using movement semantics.",_bmad-output/implementation-artifacts,"sprint plan",
+ma-skills,4-implementation,Remove from Sprint,remove-from-sprint,,skill:remove-from-sprint,remove-from-sprint,false,bmm-sm,,"Move items from a sprint back to the backlog in the unified sprint-status.yaml using reverse movement semantics.",_bmad-output/implementation-artifacts,"sprint plan",
+ma-skills,4-implementation,Modify Sprint,modify-sprint,,skill:modify-sprint,modify-sprint,false,bmm-sm,,"Modify an existing sprint's metadata (name, capacity, dates, status) within the sprints section of sprint-status.yaml.",_bmad-output/implementation-artifacts,"sprint plan",
+ma-skills,4-implementation,Sprint Status View,sprint-status-view,,skill:sprint-status-view,sprint-status-view,false,bmm-sm,,"Display formatted sprint progress, backlog, and epic status from the unified sprint-status.yaml.",_bmad-output/implementation-artifacts,"status display",
+ma-skills,4-implementation,Sprint Status Health,bmad-sprint-status,,skill:bmad-sprint-status,bmad-sprint-status,false,bmm-sm,,"Analyze sprint health, surface risk flags, and recommend next actions from the unified sprint-status.yaml.",_bmad-output/implementation-artifacts,"health summary",
+ma-skills,4-implementation,Cleanup Done,cleanup-done,,skill:cleanup-done,cleanup-done,false,bmm-sm,,"Archive done and cancelled items — remove from sprint-status.yaml and move files to done/ subfolder.",_bmad-output/implementation-artifacts,"archival",
+ma-skills,4-implementation,Close Sprint,close-sprint,,skill:close-sprint,close-sprint,false,bmm-sm,,"Close an active sprint — archive done/cancelled items, disposition incomplete items, set sprint status to closed.",_bmad-output/implementation-artifacts,"sprint plan",
+ma-skills,4-implementation,Prioritize Backlog,prioritize-backlog,,skill:prioritize-backlog,prioritize-backlog,false,bmm-sm,,"Reprioritize backlog items using multiple criteria -- severity, business value, dependencies, type, age.",_bmad-output/implementation-artifacts,"backlog",
 ma-skills,4-implementation,Project Context Expansion,project-context-expansion,,skill:project-context-expansion,project-context-expansion,false,bmm-sm,,"Post-retrospective companion to update project-context.md with new rules.",_bmad-output,"project context",
-ma-skills,4-implementation,Sprint Status View,sprint-status-view,,skill:sprint-status-view,sprint-status-view,false,bmm-sm,,"View sprint status with capacity, items, and backlog. Regenerates sprint-status.yaml.",_bmad-output/implementation-artifacts,"status display",
-ma-skills,4-implementation,Generate Backlog,generate-backlog,,skill:generate-backlog,generate-backlog,false,bmm-sm,,"Generate or refresh flat backlog from epics and bug stories.",_bmad-output/implementation-artifacts,"backlog",
-ma-skills,4-implementation,Remove from Sprint,remove-from-sprint,,skill:remove-from-sprint,remove-from-sprint,false,bmm-sm,,"Remove items from a sprint and return to unassigned backlog.",_bmad-output/implementation-artifacts,"sprint plan",
-ma-skills,4-implementation,Cleanup Done,cleanup-done,,skill:cleanup-done,cleanup-done,false,bmm-sm,,"Archive done items — move files to done/ and remove from sprint/backlog.",_bmad-output/implementation-artifacts,"archived items",
-ma-skills,4-implementation,Prioritize Backlog,prioritize-backlog,,skill:prioritize-backlog,prioritize-backlog,false,bmm-sm,,"Reprioritize backlog using multiple criteria — severity, value, dependencies.",_bmad-output/implementation-artifacts,"backlog",
-ma-skills,anytime,ML Agent (Demerzel),bmad-ma-agent-ml,,skill:bmad-ma-agent-ml,bmad-ma-agent-ml,false,bmm-demerzel,,"Machine Learning Scientist specializing in falsifiable hypothesis validation and failure-cost analysis.",output_folder,"agent customization",
-ma-skills,1-research,ML Ideation & PRD,ml-ideation,,skill:ml-ideation,ml-ideation,false,bmm-demerzel,,"Frame ML research problem, define requirements, and produce Research Thesis and PRD.",_bmad-output/planning-artifacts,"ML documents",
-ma-skills,1-research,ML EDA & Research,ml-eda,,skill:ml-eda,ml-eda,false,bmm-demerzel,,"Perform exploratory data analysis, establish baselines, and produce EDA report.",_bmad-output/planning-artifacts,"EDA report",
-ma-skills,1-research,ML Architecture Design,ml-architecture,,skill:ml-architecture,ml-architecture,false,bmm-demerzel,,"Design model architecture, stack, and experiment tracking strategy.",_bmad-output/planning-artifacts,"arch design",
-ma-skills,4-implementation,ML Detailed Design,ml-detailed-design,,skill:ml-detailed-design,ml-detailed-design,false,bmm-demerzel,,"Break down infrastructure and experiment tasks from architecture.",_bmad-output/planning-artifacts,"task breakdown",
-ma-skills,4-implementation,ML TechSpec (Contract),ml-techspec,,skill:ml-techspec,ml-techspec,false,bmm-demerzel,,"Lock experiment parameters and performance tiers before training.",_bmad-output/planning-artifacts,"techspec contract",
-ma-skills,4-implementation,ML Infra & Sync,ml-infra,,skill:ml-infra,ml-infra,false,bmm-demerzel,,"Build ML infrastructure, manage dependencies, and run smoke tests.",_bmad-output/implementation-artifacts,"infra status",
-ma-skills,4-implementation,ML Experiment,ml-experiment,,skill:ml-experiment,ml-experiment,false,bmm-demerzel,,"Execute training experiments against locked TechSpec and log metrics.",_bmad-output/implementation-artifacts,"experiments log",
-ma-skills,4-implementation,ML Results Analysis,ml-analysis,,skill:ml-analysis,ml-analysis,false,bmm-demerzel,,"Evaluate experiment outcomes against TechSpec success tiers.",_bmad-output/implementation-artifacts,"analysis report",
-ma-skills,4-implementation,ML HPO (Tuning),ml-hparam,,skill:ml-hparam,ml-hparam,false,bmm-demerzel,,"Perform automated hyperparameter optimization (conditional).",_bmad-output/implementation-artifacts,"tuning results",
-ma-skills,4-implementation,ML Iterative Revision,ml-revision,,skill:ml-revision,ml-revision,false,bmm-demerzel,,"Amend hypothesis and requirements based on experiment findings.",_bmad-output/planning-artifacts,"amended docs",
-ma-skills,anytime,ML Advise & Search,ml-advise,,skill:ml-advise,ml-advise,false,bmm-demerzel,,"Search past experiments and surface findings or failure warnings.",_bmad-output,"findings report",
-ma-skills,anytime,ML Retrospective,ml-retrospective,,skill:ml-retrospective,ml-retrospective,false,bmm-demerzel,,"Capture session learnings and update project context.",_bmad-output,"session learnings",

package/lib/bmad-extension/skills/add-sprint/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: add-sprint
-description: Guided workflow to create a new sprint entity with capacity limits, optional ISO dates, and structured YAML schema for sprint planning
+description: Guided workflow to create a new sprint entry in the sprints section of sprint-status.yaml with capacity limits, optional ISO dates, and auto-incremented ID
 type: skill
 triggers:
   - "add sprint"
@@ -9,198 +9,166 @@ triggers:
 
 # Add Sprint Workflow
 
-Guided workflow to create a new sprint entity with capacity limits, optional ISO dates, and structured YAML schema.
+Guided workflow to create a new sprint entry in the `sprints` section of `sprint-status.yaml` with capacity limits, optional ISO dates, and auto-incremented sprint ID.
 
 <workflow>
 
-<step n="1" goal="Gather and validate sprint number and name">
-  <action>Ask the user for the sprint number</action>
-  <ask>What is the sprint number? (positive integer, e.g., 1, 2, 3)</ask>
-  <action>Store input as {{sprint_number_input}}</action>
-  <action>Validate {{sprint_number_input}} matches `^[1-9]\d*$` (positive integer, no leading zeros, no non-numeric characters)</action>
-  <action>Validate {{sprint_number_input}} is <= 9999</action>
-  <check if="{{sprint_number_input}} fails validation (zero, negative, non-numeric, leading zeros like '03', or > 9999)">
-    <output>❌ Invalid sprint number: "{{sprint_number_input}}". Must be a positive integer (1-9999), no leading zeros.</output>
-    <goto step="1" />
+<step n="0" goal="Load configuration and validate file existence">
+  <action>Resolve the path to `sprint-status.yaml`. Check `_bmad/bmm/config.yaml` for a configured `story_location` path; if not set, default to `_bmad-output/implementation-artifacts/sprint-status.yaml`</action>
+  <action>Attempt to read the file at the resolved path</action>
+  <check if="sprint-status.yaml does not exist">
+    <output>No sprint-status.yaml found. Run sprint planning first to initialize the file.</output>
+    <action>Exit workflow</action>
   </check>
-  <action>Store as {{sprint_number}} (integer)</action>
-  <action>Construct {{sprint_id}} = "sprint-{{sprint_number}}"</action>
+  <action>Read and parse the full file: `epics`, `backlog`, and `sprints` sections plus all metadata fields</action>
+  <action>Store parsed content as {{file_content}}</action>
+</step>
 
-  <!-- Smart default name: detect naming patterns from existing sprints -->
-  <action>Glob `_bmad-output/implementation-artifacts/sprints/sprint-*.yaml` to discover existing sprint files</action>
-  <action>If existing sprints found, read the `name` field from the most recent one (highest sprint number)</action>
-  <action>Infer a smart default name:
-    - If previous name follows a sequential pattern with a numeric suffix (e.g., "app04"), suggest the next increment (e.g., "app05")
-    - If previous name follows a date pattern (e.g., "2026-W14"), suggest the next date interval
-    - If previous name is "Sprint {n}", suggest "Sprint {{sprint_number}}"
-    - If no pattern detected or no existing sprints, default to "Sprint {{sprint_number}}"
-  </action>
-  <ask>Sprint name? (press Enter for "{{default_name}}", or type a custom name):</ask>
-  <action>If user presses Enter or leaves blank, set {{sprint_name}} = "{{default_name}}"</action>
-  <action>If user provides input, store as {{sprint_name}}</action>
+<step n="1" goal="Auto-increment sprint ID and derive default name">
+  <action>Extract all keys from the `sprints` map in {{file_content}}</action>
+  <action>Parse numeric suffix from each key matching pattern `sprint-N` (e.g., `sprint-1` → 1, `sprint-3` → 3)</action>
+  <check if="no sprint keys exist in sprints map">
+    <action>Set {{new_number}} = 1</action>
+    <action>Set {{default_name}} = "Sprint 1"</action>
+  </check>
+  <check if="sprint keys exist">
+    <action>Find the highest numeric suffix among all sprint keys; store as {{max_number}}</action>
+    <action>Set {{new_number}} = {{max_number}} + 1</action>
+    <action>Look up the sprint entry whose key has suffix {{max_number}}; read its `name` field</action>
+    <action>If the name matches pattern "Sprint N" or "Sprint N — description" or "Sprint N - description", set {{default_name}} = "Sprint {{new_number}}"; otherwise set {{default_name}} = "Sprint {{new_number}}" as safe fallback</action>
+  </check>
+  <action>Set {{sprint_id}} = "sprint-{{new_number}}"</action>
+  <action>Set {{sprint_name}} = {{default_name}}</action>
+  <output>
+Auto-generated Sprint ID: **{{sprint_id}}**
+Default Sprint Name: **{{sprint_name}}**
+  </output>
+  <ask>Sprint ID: {{sprint_id}} — press Enter to accept or type a different number:</ask>
+  <check if="user provides a different number">
+    <action>Set {{sprint_id}} = "sprint-{user_number}"</action>
+    <action>Check if {{sprint_id}} already exists as a key in the `sprints` map</action>
+    <check if="sprint_id already exists">
+      <output>Sprint ID {{sprint_id}} already exists in sprint-status.yaml. Please choose a different number.</output>
+      <goto step="1" sub="re-prompt for number only" />
+    </check>
+    <action>Update {{sprint_name}} default to "Sprint {user_number}"</action>
+  </check>
+  <ask>Sprint name: '{{sprint_name}}' — press Enter to accept or type a different name:</ask>
+  <check if="user provides a different name">
+    <action>Set {{sprint_name}} = user input</action>
+  </check>
 </step>
 
-<step n="2" goal="Gather capacity as positive integer">
-  <action>Explain capacity: the maximum number of items (stories + bugs) that can be assigned to this sprint</action>
-  <ask>What is the sprint capacity? (Enter a positive integer — the maximum number of stories/bugs for this sprint)</ask>
+<step n="2" goal="Gather capacity (required)">
+  <action>Explain: capacity is the maximum number of items (stories + bugs) that can be assigned to this sprint. This is advisory — skills will warn but not block when exceeded (per schema section 4.2).</action>
+  <ask>What is the sprint capacity? (Enter a positive integer)</ask>
   <action>Store input as {{capacity_input}}</action>
   <action>Validate {{capacity_input}} is a positive integer (greater than zero, no decimals, no non-numeric characters)</action>
   <check if="{{capacity_input}} is NOT a positive integer">
-    <output>❌ Invalid capacity: "{{capacity_input}}". Capacity must be a positive integer (e.g., 5, 10, 20). Zero and negative values are not allowed.</output>
+    <output>Invalid capacity: "{{capacity_input}}". Capacity must be a positive integer (e.g., 5, 10, 20). Zero and negative values are not allowed.</output>
     <goto step="2" />
   </check>
   <action>Store as {{capacity}} (integer)</action>
 </step>
 
-<step n="3a" goal="Gather optional start date (ISO format)">
-  <action>Explain: start and end dates are optional ISO dates (YYYY-MM-DD format). Press Enter to skip.</action>
-  <ask>Optional — Sprint start date (YYYY-MM-DD, press Enter to skip):</ask>
-  <action>Store input as {{start_input}}</action>
-  <check if="{{start_input}} is not empty">
-    <action>Validate {{start_input}} matches regex `^\d{4}-\d{2}-\d{2}$`</action>
-    <action>Verify {{start_input}} resolves to a real calendar date (reject impossible dates like 2026-02-30, 2026-13-45, etc.)</action>
-    <check if="{{start_input}} fails date validation">
-      <output>❌ Invalid date: "{{start_input}}". Must be a valid date in YYYY-MM-DD format (e.g., 2026-04-01).</output>
-      <goto step="3a" />
+<step n="3" goal="Gather optional start and end dates">
+  <ask>Optional — Sprint start date (ISO format YYYY-MM-DD, press Enter to skip):</ask>
+  <action>Store as {{start_input}}</action>
+  <check if="start_input is not empty">
+    <action>Validate {{start_input}} matches ISO date pattern YYYY-MM-DD (4-digit year, 2-digit month 01-12, 2-digit day 01-31)</action>
+    <check if="start_input does not match ISO date pattern">
+      <output>Invalid date format: "{{start_input}}". Please use YYYY-MM-DD (e.g., 2026-04-15).</output>
+      <goto step="3" sub="re-prompt for start date only" />
     </check>
+    <action>Store as {{start}} = {{start_input}}</action>
   </check>
-  <action>Store as {{start_date}} (valid ISO date string, or empty string "" if skipped)</action>
-</step>
-
-<step n="3b" goal="Gather optional end date (ISO format)">
-  <ask>Optional — Sprint end date (YYYY-MM-DD, press Enter to skip):</ask>
-  <action>Store input as {{end_input}}</action>
-  <check if="{{end_input}} is not empty">
-    <action>Validate {{end_input}} matches regex `^\d{4}-\d{2}-\d{2}$`</action>
-    <action>Verify {{end_input}} resolves to a real calendar date</action>
-    <check if="{{end_input}} fails date validation">
-      <output>❌ Invalid date: "{{end_input}}". Must be a valid date in YYYY-MM-DD format (e.g., 2026-04-14).</output>
-      <goto step="3b" />
+  <check if="start_input is empty">
+    <action>Store as {{start}} = "" (empty string)</action>
+  </check>
+  <ask>Optional — Sprint end date (ISO format YYYY-MM-DD, press Enter to skip):</ask>
+  <action>Store as {{end_input}}</action>
+  <check if="end_input is not empty">
+    <action>Validate {{end_input}} matches ISO date pattern YYYY-MM-DD</action>
+    <check if="end_input does not match ISO date pattern">
+      <output>Invalid date format: "{{end_input}}". Please use YYYY-MM-DD (e.g., 2026-04-28).</output>
+      <goto step="3" sub="re-prompt for end date only" />
+    </check>
+    <check if="end_input is before start and start is not empty">
+      <output>Warning: end date {{end_input}} is before start date {{start}}. Continuing as requested.</output>
     </check>
+    <action>Store as {{end}} = {{end_input}}</action>
   </check>
-  <action>Store as {{end_date}} (valid ISO date string, or empty string "" if skipped)</action>
-
-  <check if="both {{start_date}} and {{end_date}} are non-empty AND {{start_date}} > {{end_date}}">
-    <output>❌ Invalid date range: start date ({{start_date}}) is after end date ({{end_date}}). Start must be on or before end.</output>
-    <goto step="3a" />
+  <check if="end_input is empty">
+    <action>Store as {{end}} = "" (empty string)</action>
   </check>
 </step>
 
-<step n="4" goal="Confirm and validate all inputs">
+<step n="4" goal="Confirmation">
   <output>
-## Sprint Summary — Please Confirm
-
-- **Sprint ID:** {{sprint_id}}
-- **Sprint Name:** "{{sprint_name}}"
-- **Status:** planning
-- **Capacity (max items):** {{capacity}}
-- **Start Date:** {{start_date}} *(empty if skipped)*
-- **End Date:** {{end_date}} *(empty if skipped)*
-- **Items:** [] *(empty — items assigned via /add-to-sprint)*
-- **Output File:** `_bmad-output/implementation-artifacts/sprints/{{sprint_id}}.yaml`
+## New Sprint Summary — Please Confirm
+
+- Sprint ID: {{sprint_id}}
+- Sprint Name: {{sprint_name}}
+- Capacity: {{capacity}} items
+- Start Date: {{start}} *(empty if skipped)*
+- End Date: {{end}} *(empty if skipped)*
+- Status: planning
+- Items: [] *(empty — use /add-to-sprint to assign items)*
+- Target: sprint-status.yaml sprints section
   </output>
-  <ask>Confirm creation? [y] Yes / [n] Cancel / [e] Edit a field:</ask>
+  <ask>Confirm creation? [y] Yes / [n] Cancel / [e] Edit a field</ask>
   <check if="user selects 'e'">
-    <ask>Which field to edit? (number / name / capacity / start / end)</ask>
-    <check if="field == 'number'">
-      <ask>New sprint number? (positive integer, 1-9999)</ask>
-      <action>Store input as {{sprint_number_input}}</action>
-      <action>Validate {{sprint_number_input}} matches `^[1-9]\d*$` and is <= 9999</action>
-      <check if="{{sprint_number_input}} fails validation">
-        <output>❌ Invalid sprint number: "{{sprint_number_input}}". Must be a positive integer (1-9999), no leading zeros.</output>
-        <goto step="4" />
-      </check>
-      <action>Store as {{sprint_number}} (integer)</action>
-      <action>Construct {{sprint_id}} = "sprint-{{sprint_number}}"</action>
-      <action>If sprint name was using previous default "Sprint {old_n}", update to "Sprint {{sprint_number}}"</action>
-      <action>Check if file exists at `_bmad-output/implementation-artifacts/sprints/{{sprint_id}}.yaml`</action>
-      <check if="file already exists at new path">
-        <output>⚠️ A sprint entity already exists at `_bmad-output/implementation-artifacts/sprints/{{sprint_id}}.yaml`. You will be prompted to overwrite at creation.</output>
-      </check>
-      <goto step="4" />
-    </check>
+    <ask>Which field to edit? (id / name / capacity / start / end)</ask>
+    <check if="field == 'id'"><goto step="1" /></check>
     <check if="field == 'name'">
-      <ask>New sprint name (or press Enter to use "Sprint {{sprint_number}}"):</ask>
-      <action>If blank, set {{sprint_name}} = "Sprint {{sprint_number}}"; else store user input as {{sprint_name}}</action>
+      <ask>Sprint name (or press Enter to use "{{sprint_name}}"):</ask>
+      <check if="input is not empty"><action>Set {{sprint_name}} = user input</action></check>
       <goto step="4" />
     </check>
     <check if="field == 'capacity'"><goto step="2" /></check>
-    <check if="field == 'start'"><goto step="3a" /></check>
-    <check if="field == 'end'"><goto step="3b" /></check>
-    <check if="field is not recognized">
-      <output>❌ Unrecognized field: "{{field}}". Valid options: number, name, capacity, start, end.</output>
-      <goto step="4" />
-    </check>
+    <check if="field == 'start'"><goto step="3" sub="start date only" /></check>
+    <check if="field == 'end'"><goto step="3" sub="end date only" /></check>
   </check>
   <check if="user selects 'n'">
-    <output>❌ Sprint creation cancelled.</output>
+    <output>Sprint creation cancelled.</output>
     <action>Exit workflow</action>
   </check>
-  <check if="user input is not 'y', 'n', or 'e'">
-    <output>❌ Unrecognized option: "{{user_input}}". Please enter [y] Yes, [n] Cancel, or [e] Edit a field.</output>
-    <goto step="4" />
-  </check>
 </step>
 
-<step n="5" goal="Generate sprint entity YAML file">
-  <action>Determine output path: `_bmad-output/implementation-artifacts/sprints/{{sprint_id}}.yaml`</action>
-  <action>Ensure directory `_bmad-output/implementation-artifacts/sprints/` exists (create if needed)</action>
-
-  <!-- Overwrite protection for new path -->
-  <action>Check if file already exists at `_bmad-output/implementation-artifacts/sprints/{{sprint_id}}.yaml`</action>
-  <check if="file already exists at new path">
-    <anchor id="overwrite_prompt" />
-    <output>⚠️ A sprint entity already exists at `_bmad-output/implementation-artifacts/sprints/{{sprint_id}}.yaml`.</output>
-    <ask>Overwrite existing sprint? [y] Yes / [n] Cancel:</ask>
-    <check if="user selects 'n'">
-      <output>❌ Sprint creation cancelled to preserve existing sprint.</output>
-      <action>Exit workflow</action>
-    </check>
-    <check if="user input is not 'y' or 'n'">
-      <output>❌ Unrecognized option: "{{user_input}}". Please enter [y] Yes or [n] Cancel.</output>
-      <goto anchor="overwrite_prompt" />
-    </check>
-  </check>
-
-  <!-- Advisory check for old-format file -->
-  <action>Check if file exists at old path: `_bmad-output/implementation-artifacts/sprint-plan-{{sprint_number}}.yaml`</action>
-  <check if="old-format file exists">
-    <output>ℹ️ **Note:** An old-format sprint file exists at `_bmad-output/implementation-artifacts/sprint-plan-{{sprint_number}}.yaml`. The new sprint will be created at the new path. The old file is NOT auto-migrated — review or remove it manually if no longer needed.</output>
-  </check>
-
-  <action>Get current ISO timestamp for created_date and last_modified</action>
-  <action>Write sprint entity YAML to `_bmad-output/implementation-artifacts/sprints/{{sprint_id}}.yaml` with this structure:
-
+<step n="5" goal="Write sprint entry to sprint-status.yaml">
+  <action>Re-read the current content of `sprint-status.yaml` (resolved path from Step 0) to get the latest state</action>
+  <action>Get the current ISO-8601 timestamp for `last_updated`</action>
+  <action>Append a new entry to the `sprints` map with this structure:
 ```yaml
-id: {{sprint_id}}
-name: "{{sprint_name}}"
-status: planning
-capacity: {{capacity}}
-start: "{{start_date}}"
-end: "{{end_date}}"
-items: []
-created_date: "{{current_iso_timestamp}}"
-last_modified: "{{current_iso_timestamp}}"
+  {{sprint_id}}:
+    name: "{{sprint_name}}"
+    status: planning
+    capacity: {{capacity}}
+    start: "{{start}}"
+    end: "{{end}}"
+    items: []
 ```
-
-  **YAML output rules:**
-  - Always quote the `name` field to handle special characters
-  - `start` and `end` are empty string `""` if skipped
-  - `items` is always empty array `[]` at creation
-  - `status` is always `planning` at creation (never `active` or `closed`)
   </action>
+  <action>Preserve the `epics` section unchanged</action>
+  <action>Preserve the `backlog` section unchanged</action>
+  <action>Preserve all existing entries in the `sprints` section unchanged</action>
+  <action>Update the `last_updated` metadata field to the current ISO-8601 timestamp</action>
+  <action>Preserve the `generated` field unchanged (never modify)</action>
+  <action>Write the complete updated file in a single atomic write (read-modify-write pattern)</action>
+</step>
+
+<step n="6" goal="Summary output">
   <output>
-✅ **Sprint created successfully!**
+Sprint created successfully!
 
-- **File:** `_bmad-output/implementation-artifacts/sprints/{{sprint_id}}.yaml`
-- **Sprint:** {{sprint_name}}
-- **Capacity:** {{capacity}} items
-- **Status:** planning
+- Sprint: {{sprint_name}} ({{sprint_id}})
+- Capacity: {{capacity}} items
+- Status: planning
 
-**Next Steps:**
-- Use `/add-to-sprint` to assign backlog items to this sprint
-- Use `/modify-sprint` to update sprint details later
-- Use `/sprint-status-view` to view sprint progress
+Next Steps:
+- Use /add-to-sprint to assign backlog items to this sprint
+- Use /modify-sprint to update sprint details later
+- Use /sprint-status-view to view sprint progress
   </output>
 </step>