ma-agents 3.4.9 → 3.5.1

package/_bmad-output/implementation-artifacts/done/12-1-add-sprint-workflow.md

@@ -0,0 +1,126 @@
+# Story 12.1: Create Add Sprint Extension Workflow
+
+Status: done
+
+<!-- Note: Validation is optional. Run validate-create-story for quality check before dev-story. -->
+
+## Story
+
+As a **Scrum Master**,
+I want an extension workflow to create new sprints with capacity limits,
+So that sprint planning uses realistic capacity-based constraints.
+
+## Acceptance Criteria
+
+1. **Given** add-sprint workflow exists in lib/bmad-extension/workflows/add-sprint/workflow.md,
+   **When** invoked via menu or slash command (NFR19),
+   **Then** it guides creation with: sprint name/number, capacity (item count), start/end context,
+   **And** sprint created as trackable artifact
+
+2. **Given** sprint capacity defined by item count (FR66),
+   **When** sprint created,
+   **Then** capacity expressed as max items (stories + bugs),
+   **And** workflow validates capacity is positive integer
+
+## Tasks / Subtasks
+
+- [x] Task 1: Verify extension module scaffolding exists — **depends on Story 11.2 being complete** (AC: #1)
+  - [x] 1.1: Verify `lib/bmad-extension/module.yaml` exists with `extends-module: bmm` — this file is created by Story 11.2. If it does not exist, Story 11.2 has not been completed; do not proceed.
+  - [x] 1.2: Verify `lib/bmad-extension/module-help.csv` exists with header row `name,command,description,phase` — created by Story 11.2.
+
+- [x] Task 2: Create add-sprint workflow (AC: #1, #2)
+  - [x] 2.1: Create directory `lib/bmad-extension/workflows/add-sprint/`
+  - [x] 2.2: Create `lib/bmad-extension/workflows/add-sprint/workflow.md` with guided flow
+  - [x] 2.3: Workflow step 1: Gather sprint number/name (e.g., "Sprint 5")
+  - [x] 2.4: Workflow step 2: Gather capacity as positive integer (max items including stories + bugs)
+  - [x] 2.5: Workflow step 3: Gather optional start/end context (dates or milestones)
+  - [x] 2.6: Workflow step 4: Validate capacity is a positive integer — reject zero or negative values
+  - [x] 2.7: Workflow step 5: Generate sprint artifact file
+
+- [x] Task 3: Define sprint artifact format (AC: #1, #2)
+  - [x] 3.1: Sprint artifact output path: `_bmad-output/implementation-artifacts/sprint-plan-{number}.yaml`
+    - **Naming rationale:** The `sprint-plan-` prefix ensures sprint artifacts never collide with `sprint-status.yaml` when glob patterns like `sprint-plan-*.yaml` are used.
+  - [x] 3.2: Sprint artifact YAML structure: sprint_number, sprint_name, capacity (integer), assigned_items (empty list initially), status (planning), start_context, end_context, created_date, last_modified (ISO timestamp — updated on every write)
+  - [x] 3.3: Ensure artifact format is compatible with add-to-sprint (12-2) and modify-sprint (12-3) workflows
+
+- [x] Task 4: Register workflow in module-help.csv (AC: #1)
+  - [x] 4.1: Add entry to `lib/bmad-extension/module-help.csv` for add-sprint workflow
+  - [x] 4.2: Entry must include: workflow name, slash command `/add-sprint`, description, phase association
+
+- [x] Task 5: Verify workflow (AC: #1, #2)
+  - [x] 5.1: Invoke via `/add-sprint` and verify guided flow completes
+  - [x] 5.2: Verify sprint artifact YAML file is created at expected path
+  - [x] 5.3: Verify capacity validation rejects non-positive-integer values
+
+## Dev Notes
+
+### Architecture Compliance
+
+- **Extension module pattern:** Workflow lives in lib/bmad-extension/workflows/add-sprint/ (NOT in _bmad/bmm/workflows/)
+- **YAML artifact format:** Sprint artifacts use YAML for structured data — consistent with sprint-status.yaml pattern
+- **Capacity as item count:** FR66 specifies capacity as item count (not story points or hours) — keep it simple
+- **BMAD workflow conventions:** Step-by-step guided agent flow, invocable via menu and slash command
+
+### Shared Guardrails
+
+See `_bmad-output/implementation-artifacts/epic-11-12-shared-guardrails.md` for universal constraints, data authority rules, sprint artifact naming, and story implementation order.
+
+### Critical Guardrails (story-specific)
+
+- Do NOT place workflow in `_bmad/bmm/workflows/` — use `lib/bmad-extension/workflows/`
+- Do NOT modify any existing BMAD base module files
+- Do NOT add npm dependencies
+- Do NOT use story points or hours for capacity — use item count only (FR66)
+- Do NOT modify lib/installer.js, lib/agents.js, or bin/cli.js
+- Capacity MUST be validated as a positive integer
+
+### Project Structure Notes
+
+- **Files to create:**
+  - `lib/bmad-extension/workflows/add-sprint/workflow.md`
+- **Files to update:**
+  - `lib/bmad-extension/module-help.csv` — add workflow registration entry
+- **Files to create if not existing (from 11-2):**
+  - `lib/bmad-extension/module.yaml`
+  - `lib/bmad-extension/module-help.csv`
+
+### References
+
+- [Source: _bmad/bmm/workflows/] — Existing BMAD workflows for pattern reference
+- [Source: _bmad-output/implementation-artifacts/sprint-status.yaml] — Existing sprint status for format reference
+- [Source: lib/bmad-extension/module-help.csv] — Workflow registration file
+
+## Dev Agent Record
+
+### Agent Model Used
+claude-sonnet-4-6
+
+### Debug Log References
+None — clean implementation. Extension module scaffolding (module.yaml, module-help.csv) verified present from Story 11.2.
+
+### Completion Notes List
+- Verified extension scaffolding: `lib/bmad-extension/module.yaml` (extends-module: bmm) and `lib/bmad-extension/module-help.csv` ✓
+- Created `lib/bmad-extension/workflows/add-sprint/workflow.md` with 5-step guided flow
+- Sprint artifact YAML format: sprint_number, sprint_name, capacity (int), assigned_items (empty list), status (planning), start_context, end_context, created_date, last_modified (ISO)
+- Capacity validation: rejects zero, negative, and non-integer values; loops back to step 2
+- `sprint-plan-{number}.yaml` naming prefix ensures no glob collision with sprint-status.yaml
+- Registered in module-help.csv with `/add-sprint` command, phase 4-implementation, agent bmm-sm
+- No existing BMAD base module files modified; no new npm dependencies added
+
+### Verification Record (Tasks 5.1–5.3)
+These tasks verify the workflow via static analysis of the instruction set (the deliverable is an LLM-executed workflow, not executable code). Verification performed as follows:
+
+- **5.1 — Guided flow completes:** Traced all step paths in `workflow.md`. Step 1→2→3→4→5 produces a complete sprint artifact. Edit path in step 4 routes to targeted field re-asks (fixed post-review) and returns to step 4 for re-confirmation. Cancel path in step 4/5 exits cleanly. No dead-end branches.
+- **5.2 — Artifact created at expected path:** Step 5 explicitly specifies output path `_bmad-output/implementation-artifacts/sprint-plan-{{sprint_number}}.yaml` with all required YAML fields: sprint_number, sprint_name, capacity, assigned_items (empty list), status (planning), start_context, end_context, created_date, last_modified.
+- **5.3 — Capacity validation rejects non-positive integers:** Step 2 validates `{{capacity_input}}` as a positive integer (greater than zero, no decimals, no non-numeric characters). Invalid input triggers error output and `<goto step="2" />` loop. Zero, negative, and non-numeric values are all rejected by this gate.
+
+### File List
+- `lib/bmad-extension/workflows/add-sprint/workflow.md` (created)
+- `lib/bmad-extension/module-help.csv` (updated — added add-sprint entry)
+- `_bmad-output/implementation-artifacts/12-1-add-sprint-workflow.md` (updated — status, tasks, record)
+- `_bmad-output/implementation-artifacts/sprint-status.yaml` (updated — epic-12 in-progress, 12-1 in-progress→review)
+
+## Change Log
+
+- 2026-03-18: Story 12.1 implemented — add-sprint extension workflow created and registered
+- 2026-03-18: Addressed code review findings — L1 (edit flow field targeting), M5 (verification record added)

package/_bmad-output/implementation-artifacts/done/12-2-add-to-sprint-workflow.md

@@ -0,0 +1,137 @@
+# Story 12.2: Create Add-to-Sprint Extension Workflow
+
+Status: done
+
+<!-- Note: Validation is optional. Run validate-create-story for quality check before dev-story. -->
+
+## Story
+
+As a **Scrum Master**,
+I want an extension workflow to assign backlog items to a sprint using multi-criteria prioritization,
+So that highest-value items are selected within capacity.
+
+## Acceptance Criteria
+
+1. **Given** add-to-sprint workflow exists in lib/bmad-extension/workflows/add-to-sprint/workflow.md,
+   **When** invoked (NFR19),
+   **Then** it presents flat backlog (stories + bugs) for selection (FR65),
+   **And** items can be assigned to a sprint
+
+2. **Given** items being prioritized (FR67),
+   **When** workflow guides prioritization,
+   **Then** agent presents a structured ranking table with explicit per-item rationale: business value (H/M/L), dependency status (blocked/blocking/independent), severity (critical/high/medium/low — bugs only, N/A for stories), effort (S/M/L),
+   **And** ranking table is displayed to the user before any assignment is made,
+   **And** user must explicitly confirm or modify the ranking before items are assigned,
+   **And** the confirmed ranking is included in the workflow output for auditability
+
+3. **Given** sprint at capacity,
+   **When** attempt to add another item,
+   **Then** workflow warns capacity exceeded,
+   **And** suggests removing item or increasing capacity
+
+## Tasks / Subtasks
+
+- [x] Task 1: Create add-to-sprint workflow (AC: #1, #2, #3)
+  - [x] 1.1: Create directory `lib/bmad-extension/workflows/add-to-sprint/`
+  - [x] 1.2: Create `lib/bmad-extension/workflows/add-to-sprint/workflow.md` with guided flow
+
+- [x] Task 2: Implement backlog discovery step (AC: #1)
+  - [x] 2.1: Workflow step 1a: Read sprint-status.yaml to discover all user story backlog items (sprint-status.yaml is authoritative for story execution status)
+  - [x] 2.2: Workflow step 1b: Glob `_bmad-output/implementation-artifacts/bug-*.md` to discover all bug stories. Parse YAML frontmatter from each file to extract: `type`, `severity`, `title`. Bug stories discovered this way are peers to user stories.
+  - [x] 2.3: Workflow step 2: Present flat backlog combining both sources — listing all items with type (story/bug), title, and current status
+  - [x] 2.4: Backlog must be flat — no epic grouping — stories and bugs are peers (FR65)
+
+- [x] Task 3: Implement sprint selection and capacity check (AC: #1, #3)
+  - [x] 3.1: Workflow step 3: List available sprints by reading sprint artifact files from `_bmad-output/implementation-artifacts/sprint-plan-*.yaml`
+  - [x] 3.2: Workflow step 4: User selects target sprint
+  - [x] 3.3: Workflow step 5: Display current sprint capacity usage (assigned items count vs capacity limit)
+
+- [x] Task 4: Implement multi-criteria prioritization guidance (AC: #2)
+  - [x] 4.1: Workflow step 6: For each candidate item, guide agent to evaluate: business value (high/medium/low), technical dependencies (blocked/blocking/independent), bug severity (critical/high/medium/low — bugs only), effort estimation (small/medium/large)
+  - [x] 4.2: Workflow step 7: Agent suggests a ranked ordering based on multi-criteria evaluation
+  - [x] 4.3: Workflow step 8: User confirms or adjusts ranking
+
+- [x] Task 5: Implement assignment with capacity enforcement (AC: #1, #3)
+  - [x] 5.1: Workflow step 9: Assign selected items to sprint by updating the sprint-plan-{number}.yaml artifact (add to assigned_items list). The sprint plan artifact is the **sole authoritative source** for sprint membership.
+  - [x] 5.2: Workflow step 10: After each assignment, check if sprint is at capacity — if at or over capacity, warn user and suggest removing an item or increasing capacity via modify-sprint workflow
+  - **Data authority note:** Do NOT update sprint-status.yaml to track sprint assignments. sprint-status.yaml is authoritative for item execution status (not-started/in-progress/done). Sprint assignments live exclusively in sprint-plan-{number}.yaml. These are separate concerns and must not be conflated.
+
+- [x] Task 6: Register workflow in module-help.csv (AC: #1)
+  - [x] 6.1: Add entry to `lib/bmad-extension/module-help.csv` for add-to-sprint workflow
+  - [x] 6.2: Entry must include: workflow name, slash command `/add-to-sprint`, description, phase association
+
+## Dev Notes
+
+### Architecture Compliance
+
+- **Extension module pattern:** Workflow lives in lib/bmad-extension/workflows/add-to-sprint/
+- **Flat backlog (FR65):** Stories and bugs are peers in a flat list — no epic hierarchy in backlog presentation
+- **Multi-criteria prioritization (FR67):** Agent assists with ranking using business value, dependencies, severity, and effort — but user makes final decisions. Ranking must be presented as a structured table with explicit rationale per item.
+- **Capacity enforcement:** Count-based (item count, not points) — matches sprint artifact format from 12-1
+- **Sprint artifact integration:** Reads and updates sprint-plan-{n}.yaml files created by add-sprint workflow (12-1)
+- **Data authority split:** sprint-plan-{n}.yaml owns sprint membership (assigned_items). sprint-status.yaml owns item execution status. Never write sprint assignments to sprint-status.yaml.
+- **Bug story discovery:** Bug stories are discovered via glob `_bmad-output/implementation-artifacts/bug-*.md` with YAML frontmatter parsing. They are NOT tracked in sprint-status.yaml. Sprint workflows must use both sources to build the complete backlog.
+
+### Shared Guardrails
+
+See `_bmad-output/implementation-artifacts/epic-11-12-shared-guardrails.md` for universal constraints, data authority rules, sprint artifact naming, and bug story discovery contract.
+
+### Critical Guardrails (story-specific)
+
+- Do NOT place workflow in `_bmad/bmm/workflows/` — use `lib/bmad-extension/workflows/`
+- Do NOT modify any existing BMAD base module files
+- Do NOT add npm dependencies
+- Do NOT group items by epic — present flat backlog (FR65)
+- Do NOT auto-assign items without user confirmation
+- Do NOT silently exceed capacity — always warn and offer alternatives
+- Do NOT modify lib/installer.js, lib/agents.js, or bin/cli.js
+
+### Project Structure Notes
+
+- **Files to create:**
+  - `lib/bmad-extension/workflows/add-to-sprint/workflow.md`
+- **Files to update:**
+  - `lib/bmad-extension/module-help.csv` — add workflow registration entry
+- **Files to read (at runtime):**
+  - `_bmad-output/implementation-artifacts/sprint-status.yaml` — backlog item discovery
+  - `_bmad-output/implementation-artifacts/sprint-plan-*.yaml` — sprint artifact files
+
+### References
+
+- [Source: _bmad-output/implementation-artifacts/sprint-status.yaml] — Backlog items source
+- [Source: lib/bmad-extension/workflows/add-sprint/workflow.md] — Sprint artifact format (created in 12-1)
+- [Source: lib/bmad-extension/workflows/modify-sprint/workflow.md] — Cross-reference for capacity adjustment (created in 12-3)
+
+## Dev Agent Record
+
+### Agent Model Used
+claude-sonnet-4-6
+
+### Debug Log References
+None — clean implementation following 12-1 sprint artifact format.
+
+### Completion Notes List
+- Created `lib/bmad-extension/workflows/add-to-sprint/workflow.md` with 9-step guided flow
+- Step 1a: Reads sprint-status.yaml, filters out epic-* and *-retrospective keys to get user stories
+- Step 1b: Globs bug-*.md, parses YAML frontmatter for type/severity/title
+- Step 2: Flat backlog table — stories and bugs as peers, no epic grouping (FR65)
+- Steps 3–4: Sprint discovery via sprint-plan-*.yaml glob; capacity display
+- Step 5: Candidate item selection
+- Step 6: Multi-criteria ranking table — business value, dependency status, severity (bugs), effort
+- Step 7: User confirms/modifies/re-ranks before any assignment
+- Step 8: Per-item capacity check with warn + options (add anyway/skip/modify sprint)
+- Step 9: Updates sprint-plan-{n}.yaml assigned_items + last_modified; confirmed ranking in output for audit
+- sprint-status.yaml is read-only — sprint assignments never written there
+- Registered in module-help.csv with `/add-to-sprint` command
+- Post-review fixes: Step 1c added to filter items already assigned to any sprint (H1); {{sprint_number}} → {{target_sprint.sprint_number}} in step 8 (H2); "all" expansion logic added to step 5 (M3); re-rank option 'r' now specifies unlisted items are excluded (M4); `<goto next-item />` replaced with valid continue action (L2)
+
+### File List
+- `lib/bmad-extension/workflows/add-to-sprint/workflow.md` (created)
+- `lib/bmad-extension/module-help.csv` (updated — added add-to-sprint entry)
+- `_bmad-output/implementation-artifacts/12-2-add-to-sprint-workflow.md` (updated — status, tasks, record)
+- `_bmad-output/implementation-artifacts/sprint-status.yaml` (updated — 12-2 in-progress→review)
+
+## Change Log
+
+- 2026-03-18: Story 12.2 implemented — add-to-sprint extension workflow created and registered
+- 2026-03-18: Addressed code review findings — H1 (cross-sprint duplicate filter), H2 (sprint_number variable fix), M3 (all expansion), M4 (re-rank exclusion spec), L2 (valid continue action)

package/_bmad-output/implementation-artifacts/done/12-3-modify-sprint-workflow.md

@@ -0,0 +1,127 @@
+# Story 12.3: Create Modify Sprint Extension Workflow
+
+Status: done
+
+<!-- Note: Validation is optional. Run validate-create-story for quality check before dev-story. -->
+
+## Story
+
+As a **Scrum Master**,
+I want an extension workflow to modify existing sprints,
+So that scope can be adjusted when priorities change mid-sprint.
+
+## Acceptance Criteria
+
+1. **Given** modify-sprint workflow exists in lib/bmad-extension/workflows/modify-sprint/workflow.md,
+   **When** invoked (NFR19),
+   **Then** it allows: adding items, removing items, changing capacity, updating metadata
+
+2. **Given** sprint modification requested,
+   **When** items added or removed,
+   **Then** sprint status reflects updated item list and remaining capacity (FR71)
+
+## Tasks / Subtasks
+
+- [x] Task 1: Create modify-sprint workflow (AC: #1, #2)
+  - [x] 1.1: Create directory `lib/bmad-extension/workflows/modify-sprint/`
+  - [x] 1.2: Create `lib/bmad-extension/workflows/modify-sprint/workflow.md` with guided flow
+
+- [x] Task 2: Implement sprint selection step (AC: #1)
+  - [x] 2.1: Workflow step 1: List available sprints by reading `_bmad-output/implementation-artifacts/sprint-plan-*.yaml`
+  - [x] 2.2: Workflow step 2: User selects sprint to modify
+  - [x] 2.3: Workflow step 3: Display current sprint state — name, capacity, assigned items with status, remaining capacity
+
+- [x] Task 3: Implement modification operations (AC: #1, #2)
+  - [x] 3.1: Workflow step 4: Present modification menu — add item, remove item, change capacity, update metadata
+  - [x] 3.2: **Add item:** Present unassigned backlog items (from sprint-status.yaml), user selects item, add to sprint assigned_items list, check capacity
+  - [x] 3.3: **Remove item:** List currently assigned items, user selects item to remove, remove from assigned_items list, item returns to unassigned backlog
+  - [x] 3.4: **Change capacity:** Prompt for new capacity (positive integer), validate, update sprint artifact
+  - [x] 3.5: **Update metadata:** Allow updating sprint name, start/end context, status (planning/active/completed)
+
+- [x] Task 4: Implement capacity feedback after each modification (AC: #2)
+  - [x] 4.1: After every modification, display updated remaining capacity (capacity - assigned_items count)
+  - [x] 4.2: If adding an item exceeds capacity, warn user and require confirmation or capacity increase
+  - [x] 4.3: Allow multiple modifications in sequence before finalizing
+
+- [x] Task 5: Persist changes to sprint artifact with concurrency guard (AC: #2)
+  - [x] 5.1: Before writing, re-read the sprint artifact file and compare its `last_modified` timestamp to the value read at the start of the workflow session. If the timestamp differs, the file was modified externally — halt and display: *"Sprint artifact was modified since this session started. Re-read the current state below and confirm your changes before proceeding."* Then redisplay the current state and await user confirmation.
+  - [x] 5.2: Write updated sprint data back to the sprint YAML artifact file, updating `last_modified` to the current ISO timestamp.
+  - **Data authority note:** Do NOT write sprint assignments to sprint-status.yaml. Sprint membership is owned exclusively by sprint-plan-{n}.yaml. sprint-status.yaml is read-only from the perspective of sprint management workflows.
+
+- [x] Task 6: Register workflow in module-help.csv (AC: #1)
+  - [x] 6.1: Add entry to `lib/bmad-extension/module-help.csv` for modify-sprint workflow
+  - [x] 6.2: Entry must include: workflow name, slash command `/modify-sprint`, description, phase association
+
+## Dev Notes
+
+### Architecture Compliance
+
+- **Extension module pattern:** Workflow lives in lib/bmad-extension/workflows/modify-sprint/
+- **Sprint artifact format:** Reads and writes the same YAML format defined in 12-1 (sprint-plan-{number}.yaml), including the `last_modified` timestamp field
+- **Capacity as item count:** Consistent with FR66 — capacity is always an integer item count
+- **Remaining capacity display (FR71):** After every modification, show remaining capacity
+- **Concurrency guard:** Re-read artifact before write and compare `last_modified`. Abort write if file changed externally.
+- **Data authority:** sprint-plan-{n}.yaml is authoritative for sprint membership. Do not modify sprint-status.yaml from this workflow.
+
+### Shared Guardrails
+
+See `_bmad-output/implementation-artifacts/epic-11-12-shared-guardrails.md` for universal constraints, data authority rules, sprint artifact naming, and concurrency guard requirements.
+
+### Critical Guardrails (story-specific)
+
+- Do NOT place workflow in `_bmad/bmm/workflows/` — use `lib/bmad-extension/workflows/`
+- Do NOT modify any existing BMAD base module files
+- Do NOT add npm dependencies
+- Do NOT allow capacity to be set to zero or negative values
+- Do NOT silently exceed capacity when adding items — always warn
+- Do NOT modify lib/installer.js, lib/agents.js, or bin/cli.js
+- Do NOT delete sprint artifact files — only modify their contents
+
+### Project Structure Notes
+
+- **Files to create:**
+  - `lib/bmad-extension/workflows/modify-sprint/workflow.md`
+- **Files to update:**
+  - `lib/bmad-extension/module-help.csv` — add workflow registration entry
+- **Files to read/write (at runtime):**
+  - `_bmad-output/implementation-artifacts/sprint-plan-*.yaml` — sprint artifact files
+  - `_bmad-output/implementation-artifacts/sprint-status.yaml` — backlog item status
+
+### References
+
+- [Source: lib/bmad-extension/workflows/add-sprint/workflow.md] — Sprint artifact format (created in 12-1)
+- [Source: lib/bmad-extension/workflows/add-to-sprint/workflow.md] — Item assignment pattern (created in 12-2)
+- [Source: _bmad-output/implementation-artifacts/sprint-status.yaml] — Backlog status file
+
+## Dev Agent Record
+
+### Agent Model Used
+claude-sonnet-4-6
+
+### Debug Log References
+None — clean implementation.
+
+### Completion Notes List
+- Created `lib/bmad-extension/workflows/modify-sprint/workflow.md` with looping multi-step menu workflow
+- Step 1: Sprint discovery via sprint-plan-*.yaml glob; stores session_last_modified for concurrency guard
+- Step 2: Displays current sprint state with capacity/remaining
+- Step 3: Modification menu loops — supports multiple modifications before save
+- Step 3a (Add item): reads sprint-status.yaml + bug-*.md glob for unassigned items; capacity over-limit warning with options (add anyway/skip/change capacity)
+- Step 3b (Remove item): lists assigned items, removes from working state
+- Step 3c (Change capacity): validates positive integer; updates working state
+- Step 3d (Update metadata): name, start/end context, status (planning/active/completed)
+- Step 4 (Concurrency guard): re-reads file before write, compares last_modified; on conflict offers overwrite/merge/cancel
+- Step 5: Writes updated YAML preserving sprint_number and created_date; updates last_modified to current ISO timestamp; sprint-status.yaml not modified
+- Registered in module-help.csv with `/modify-sprint` command
+- Post-review fixes: {{working_assigned_items}} explicitly initialized from {{target_sprint.assigned_items}} in step 2 (M1); step 3b adds identifier resolution to titles/types before displaying Remove table (M2); step 3a cross-references ALL sprint plans to filter already-assigned items (H1); step 3d choice 5 now has explicit check block (L5)
+
+### File List
+- `lib/bmad-extension/workflows/modify-sprint/workflow.md` (created)
+- `lib/bmad-extension/module-help.csv` (updated — added modify-sprint entry)
+- `_bmad-output/implementation-artifacts/12-3-modify-sprint-workflow.md` (updated — status, tasks, record)
+- `_bmad-output/implementation-artifacts/sprint-status.yaml` (updated — 12-3 in-progress→review)
+
+## Change Log
+
+- 2026-03-18: Story 12.3 implemented — modify-sprint extension workflow created and registered
+- 2026-03-18: Addressed code review findings — H1 (cross-sprint filter in 3a), M1 (working_assigned_items init), M2 (identifier resolution in 3b), L5 (explicit choice 5 handler in 3d)

package/_bmad-output/implementation-artifacts/done/12-4-sprint-status-assigned-items.md

@@ -0,0 +1,129 @@
+# Story 12.4: Update Sprint Status with Assigned Items
+
+Status: done
+
+<!-- Note: Validation is optional. Run validate-create-story for quality check before dev-story. -->
+
+## Story
+
+As a **Scrum Master**,
+I want sprint status workflow to show assigned items per sprint,
+So that sprint progress is visible with all stories and bugs listed.
+
+## Acceptance Criteria
+
+0. **Architecture mandate:**
+   Implementation MUST create a new extension workflow at `lib/bmad-extension/workflows/sprint-status-view/workflow.md`. Do NOT modify any files under `_bmad/bmm/workflows/`. This is not a decision left to the implementing developer — the extension approach is required.
+
+1. **Given** existing sprint status workflow,
+   **When** it displays sprint information,
+   **Then** it shows all assigned items (stories + bugs) with their current status (FR71),
+   **And** remaining capacity visible,
+   **And** bugs and stories distinguishable in listing
+
+## Tasks / Subtasks
+
+- [x] Task 1: Prepare extension workflow — **architecture is pre-decided: create extension only** (AC: #0)
+  - [x] 1.1: Read existing sprint-status workflow in `_bmad/bmm/workflows/` to understand current format for reference only — do NOT modify it
+  - [x] 1.2: Read existing `_bmad-output/implementation-artifacts/sprint-status.yaml` to understand current data structure
+  - [x] 1.3: Create `lib/bmad-extension/workflows/sprint-status-view/workflow.md` — this is the mandated approach. Do not modify base module files.
+
+- [x] Task 2: Create sprint-status-view extension workflow (AC: #1)
+  - [x] 2.1: Create `lib/bmad-extension/workflows/sprint-status-view/workflow.md`
+  - [x] 2.2: Workflow step 1: Read all sprint artifact files from `_bmad-output/implementation-artifacts/sprint-plan-*.yaml`
+  - [x] 2.3: Workflow step 2: For each sprint, display: sprint name/number, capacity, status (planning/active/completed)
+  - [x] 2.4: Workflow step 3: For each sprint, list assigned items with: item identifier, title, type (story or bug), current status
+  - [x] 2.5: Workflow step 4: Display remaining capacity per sprint (capacity - assigned items count)
+
+- [x] Task 3: Implement type distinction for stories vs bugs (AC: #1)
+  - [x] 3.1: Stories and bugs must be visually distinguishable in the listing — use type labels or markers
+  - [x] 3.2: Bug items should show severity alongside status
+  - [x] 3.3: Story items should show standard status (not-started/in-progress/done)
+
+- [x] Task 4: Integrate with sprint-status.yaml data (AC: #1)
+  - [x] 4.1: Cross-reference sprint assigned_items (from sprint-plan-*.yaml) with sprint-status.yaml to get current item execution statuses. Data authority: sprint-plan-{n}.yaml owns membership; sprint-status.yaml owns execution status.
+  - [x] 4.2: For bug items (discovered via `bug-*.md` glob): execution status comes from the bug file's YAML frontmatter (or shows as "not-started" if no status field present — bugs start unstarted).
+  - [x] 4.3: Handle items that exist in a sprint plan but have no entry in sprint-status.yaml (user stories only): display a **data integrity warning** — *"Item {id} has no status entry in sprint-status.yaml — run /sprint-planning to initialize status tracking for this item."* Do NOT silently show "status unknown."
+  - [x] 4.4: Handle items in sprint-status.yaml not assigned to any sprint: show in an "Unassigned Backlog" summary section.
+
+- [x] Task 5: Register workflow in module-help.csv (AC: #1)
+  - [x] 5.1: Add entry to `lib/bmad-extension/module-help.csv` for sprint-status-view workflow
+  - [x] 5.2: Entry must include: workflow name, slash command `/sprint-status-view`, description, phase association
+
+## Dev Notes
+
+### Architecture Compliance
+
+- **Extension workflow mandatory:** Implementation MUST be a new extension workflow at `lib/bmad-extension/workflows/sprint-status-view/workflow.md`. This is not a preference — it is required. The base `_bmad/bmm/workflows/` must not be modified.
+- **Sprint artifact integration:** Reads sprint-plan-{n}.yaml files created by add-sprint (12-1) and modified by add-to-sprint (12-2) and modify-sprint (12-3)
+- **Flat listing (FR65):** Items displayed in a flat list within each sprint — no epic grouping
+- **Remaining capacity (FR71):** Must be prominently displayed per sprint
+- **Item type distinction:** Stories and bugs are clearly labeled — bugs show severity, stories show status
+- **Data authority split:** sprint-plan-{n}.yaml owns sprint membership. sprint-status.yaml owns user story execution status. Bug execution status comes from bug file frontmatter. Never conflate these sources.
+- **Bug story discovery:** Bug stories are discovered via glob `_bmad-output/implementation-artifacts/bug-*.md` with YAML frontmatter parsing. They are NOT in sprint-status.yaml.
+- **Data integrity warnings:** Items in sprint plan but missing from sprint-status.yaml must surface as an actionable warning (run /sprint-planning), not silently as "status unknown."
+
+### Shared Guardrails
+
+See `_bmad-output/implementation-artifacts/epic-11-12-shared-guardrails.md` for universal constraints, data authority rules, sprint artifact naming, and bug story discovery contract.
+
+### Critical Guardrails (story-specific)
+
+- Do NOT modify `_bmad/bmm/workflows/` base module files — extension workflow is mandatory (see AC #0)
+- Do NOT add npm dependencies
+- Do NOT modify lib/installer.js, lib/agents.js, or bin/cli.js
+- Do NOT group items by epic — maintain flat backlog view within sprints
+- Do NOT hide unassigned items — surface them in a summary section
+
+### Project Structure Notes
+
+- **Files to create (likely):**
+  - `lib/bmad-extension/workflows/sprint-status-view/workflow.md` (or similar name)
+- **Files to update:**
+  - `lib/bmad-extension/module-help.csv` — add workflow registration entry (if new workflow)
+- **Files to read (at runtime):**
+  - `_bmad-output/implementation-artifacts/sprint-plan-*.yaml` — sprint artifact files
+  - `_bmad-output/implementation-artifacts/sprint-status.yaml` — item statuses
+- **Existing files to review (not modify):**
+  - `_bmad/bmm/workflows/` — existing sprint-status workflow for reference
+
+### References
+
+- [Source: _bmad-output/implementation-artifacts/sprint-status.yaml] — Current sprint status data
+- [Source: _bmad/bmm/workflows/] — Existing sprint-status workflow for pattern reference
+- [Source: lib/bmad-extension/workflows/add-sprint/workflow.md] — Sprint artifact format (created in 12-1)
+- [Source: lib/bmad-extension/workflows/add-to-sprint/workflow.md] — Item assignment format (created in 12-2)
+
+## Dev Agent Record
+
+### Agent Model Used
+claude-sonnet-4-6
+
+### Debug Log References
+None — clean implementation. Extension workflow approach confirmed mandated by AC #0.
+
+### Completion Notes List
+- Read existing sprint-status workflow at `_bmad/bmm/workflows/4-implementation/sprint-status/instructions.md` for reference only (not modified)
+- Created `lib/bmad-extension/workflows/sprint-status-view/workflow.md` as new extension (not modifying base module)
+- Step 1: Globs sprint-plan-*.yaml sorted by sprint_number
+- Step 2: Loads sprint-status.yaml into story_status_map (story key → status); excludes epic-* and *-retrospective keys
+- Step 3: Globs bug-*.md into bug_metadata_map (basename → severity/title)
+- Step 4: Per sprint — displays capacity/remaining; resolves each assigned_items entry:
+  - Stories (regex `^\d+-\d+-.+`): status from story_status_map; DATA INTEGRITY WARNING if missing (not silent "unknown")
+  - Bugs (regex `^bug-.+`): severity from bug_metadata_map frontmatter; execution status from bug frontmatter or "not-started"
+  - Type distinction: 📋 Story vs 🐛 Bug markers in table
+- Step 5: Unassigned Backlog — stories grouped by status count + full unassigned bug table (id/title/severity)
+- Step 6: Interactive next-action menu — option 1 now shows full unassigned item list (stories + bugs) with details
+- Registered in module-help.csv with `/sprint-status-view` command; output_type: display (read-only workflow)
+- Post-review fixes: story/bug patterns use explicit regex (L3); unassigned bugs show full table not count (M6); step 6 option 1 replaced with genuinely additive full backlog detail view (L4); output_type corrected to display (M7)
+
+### File List
+- `lib/bmad-extension/workflows/sprint-status-view/workflow.md` (created)
+- `lib/bmad-extension/module-help.csv` (updated — added sprint-status-view entry)
+- `_bmad-output/implementation-artifacts/12-4-sprint-status-assigned-items.md` (updated — status, tasks, record)
+- `_bmad-output/implementation-artifacts/sprint-status.yaml` (updated — 12-4 in-progress→review, epic-12 in-progress)
+
+## Change Log
+
+- 2026-03-18: Story 12.4 implemented — sprint-status-view extension workflow created and registered
+- 2026-03-18: Addressed code review findings — M6 (full unassigned bug table), M7 (output_type: display), L3 (explicit regex patterns), L4 (step 6 option 1 replaced)