ma-agents 3.6.2 → 3.9.0

package/_bmad-output/implementation-artifacts/done/17-2-flat-backlog-model.md

@@ -1,264 +0,0 @@
-# Story 17.2: Flat Backlog Model
-
-Status: review
-
-<!-- Note: Validation is optional. Run validate-create-story for quality check before dev-story. -->
-
-## Story
-
-As a **Scrum Master**,
-I want a flat backlog file listing all stories and bugs in priority order, independent of their parent epic,
-So that sprint planning works from a single prioritized list, not epic-grouped sections.
-
-## Acceptance Criteria
-
-1. **Given** the backlog is generated from the epics document,
-   **When** the backlog file is created at `{implementation_artifacts}/backlog.yaml`,
-   **Then** it contains ALL stories and bugs as a flat ordered list:
-   ```yaml
-   backlog:
-     - id: "5-5-explicit-parameter-passing"
-       type: story
-       epic: 5
-       title: "Explicit Parameter Passing"
-       priority: 1
-       status: backlog
-     - id: "BUG-path-spaces"
-       type: bug
-       epic: null
-       title: "Fix space-in-path bug"
-       priority: 2
-       status: backlog
-       severity: high
-   ```
-
-2. **Given** a story is assigned to a sprint,
-   **When** the backlog is viewed,
-   **Then** the item shows `sprint: sprint-3` indicating its assignment,
-   **And** it is still visible in the backlog (with sprint annotation) for reference.
-
-3. **Given** stories exist across multiple epics,
-   **When** the backlog is ordered,
-   **Then** ordering is by the `priority` field, not by epic number,
-   **And** items from different epics can be interleaved based on priority.
-
-4. **Given** an item has status `done`,
-   **When** the backlog is generated or refreshed,
-   **Then** it is NOT included in the backlog (done items live in the done archive).
-
-## Tasks / Subtasks
-
-- [x] Task 1: Define backlog.yaml schema (AC: #1, #2, #3, #4)
-  - [x] 1.1: Create the authoritative backlog YAML schema documentation in `_bmad-output/implementation-artifacts/sprint-management-guardrails.md` (renamed by Story 17.1). Schema fields per item:
-    - `id` (string): Story IDs follow `{epic}-{story}-{slug}` format; Bug IDs follow `BUG-{slug}` format (per Story 17.1 Item ID Format Contract)
-    - `type` (enum): `story` or `bug`
-    - `epic` (int|null): Epic number for stories; `null` for bugs (FR64 — bugs don't belong to epics)
-    - `title` (string): Human-readable title, always quoted in YAML
-    - `priority` (int): Sequential integer starting from 1, lower = higher priority
-    - `status` (enum): `backlog | ready-for-dev | in-progress | review` (done items excluded per AC #4)
-    - `sprint` (string|null): Sprint ID if assigned (e.g., `sprint-3`), `null` if unassigned
-    - `severity` (enum|null): `critical | high | medium | low` for bugs only, `null` for stories
-  - [x] 1.2: Add backlog schema to guardrails doc under a new "Backlog Model" section
-
-- [x] Task 2: Create `generate-backlog` SKILL.md (AC: #1, #3, #4)
-  - [x] 2.1: Create skill package at `lib/bmad-extension/skills/generate-backlog/SKILL.md` with YAML frontmatter:
-    ```yaml
-    ---
-    name: generate-backlog
-    description: Generate or refresh the flat backlog from epics and bug story files
-    type: skill
-    triggers:
-      - "generate backlog"
-      - "refresh backlog"
-    ---
-    ```
-  - [x] 2.2: Create `lib/bmad-extension/skills/generate-backlog/bmad-skill-manifest.yaml`
-  - [x] 2.3: Implement the workflow steps in SKILL.md:
-    - **Step 1: Load sources**
-      - Read `_bmad-output/planning-artifacts/epics.md` (or sharded equivalent)
-      - Glob `_bmad-output/implementation-artifacts/bug-*.md` for bug story files
-      - Read existing `_bmad-output/implementation-artifacts/backlog.yaml` if it exists (to preserve priority overrides and sprint assignments)
-    - **Step 2: Extract stories from epics**
-      - Parse each epic section for stories with format `{epic_num}-{story_num}-{slug}`
-      - Extract: id, title, epic number
-      - Look up current status from `sprint-status.yaml` development_status entries
-      - Exclude any item with status `done` (AC #4)
-    - **Step 3: Extract bugs**
-      - For each `bug-*.md` file, parse YAML frontmatter for: type, severity, title
-      - Derive id as `BUG-{slug}` from filename (strip `bug-` prefix, uppercase to `BUG-`)
-      - Set `epic: null` for all bugs
-      - Exclude any bug with status `done`
-    - **Step 4: Merge with existing backlog**
-      - If existing backlog.yaml exists, preserve `priority` and `sprint` assignments for items that still exist
-      - New items (not in existing backlog) get appended at the end with sequential priorities after existing items
-      - Items in existing backlog that no longer exist in sources are removed
-      - Items that have become `done` since last generation are removed
-    - **Step 5: Write backlog.yaml**
-      - Sort items by `priority` field (ascending)
-      - Re-number priorities as sequential integers 1..N (no gaps)
-      - Write to `_bmad-output/implementation-artifacts/backlog.yaml`
-      - Include header comment with generation timestamp
-    - **Step 6: Report**
-      - Display summary: total items, stories count, bugs count, new items added, items removed
-
-- [x] Task 3: Register in module-help.csv (AC: #1)
-  - [x] 3.1: Add row to `lib/bmad-extension/module-help.csv`:
-    ```
-    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",
-    ```
-
-- [x] Task 4: Update sprint-planning workflow to call generate-backlog (AC: #1)
-  - [x] 4.1: Identify the sprint-planning workflow location (`_bmad/bmm/4-implementation/bmad-sprint-planning/workflow.md`)
-  - [x] 4.2: **Do NOT modify** the bmm workflow directly — instead, add a note in the generate-backlog SKILL.md that sprint-planning should invoke `/generate-backlog` as its first step when backlog model is available
-  - [x] 4.3: Add guidance in the SKILL.md output that explains the relationship: "Sprint-planning workflow should run `/generate-backlog` first to ensure the backlog is current before selecting stories for sprint creation"
-
-- [x] Task 5: Update guardrails with data authority (AC: #1, #2)
-  - [x] 5.1: Add to `sprint-management-guardrails.md` Data Authority Rules table:
-    | Concern | Authoritative Source | Read By |
-    |---|---|---|
-    | Item priority ordering | `backlog.yaml` | 17.4, 17.5, 17.7, 17.8 |
-    | Sprint membership | `sprints/sprint-{id}.yaml` | 17.4, 17.5, 17.6, 17.8 |
-  - [x] 5.2: Document that `sprint-status.yaml` is now a **derived file** — generated from backlog.yaml + sprint files (Story 17.8 will implement the derivation)
-  - [x] 5.3: Document backlog discovery glob: `_bmad-output/implementation-artifacts/backlog.yaml` (single file, not globbed)
-
-- [x] Task 6: Verify (AC: #1, #2, #3, #4)
-  - [x] 6.1: Trace SKILL.md logic — confirm all story extraction paths produce valid backlog entries
-  - [x] 6.2: Verify bug entries have `epic: null` and include `severity` field
-  - [x] 6.3: Verify done items are excluded from output
-  - [x] 6.4: Verify priority re-numbering produces sequential integers with no gaps
-  - [x] 6.5: Verify existing priority/sprint assignments are preserved on re-generation
-  - [x] 6.6: Verify sprint field shows sprint ID when assigned, null when unassigned
-
-## Dev Notes
-
-### Architecture Compliance
-
-- **SKILL.md is the authoritative file:** Following Epic 15 pattern, create the skill as a SKILL.md package at `lib/bmad-extension/skills/generate-backlog/`
-- **Extension module pattern:** Skill lives in `lib/bmad-extension/skills/` (NOT in `_bmad/bmm/workflows/`)
-- **YAML artifact format:** Backlog uses YAML, consistent with sprint files
-- **Single file model:** The backlog is ONE file (`backlog.yaml`), not sharded — it's the flat list of all active items
-- **Idempotent generation:** Running generate-backlog multiple times with no source changes produces identical output (minus timestamp)
-
-### Backlog YAML Schema (Authoritative)
-
-```yaml
-# backlog.yaml — Flat prioritized backlog
-# Generated by generate-backlog skill
-# Last generated: {ISO-8601 timestamp}
-
-backlog:
-  - id: "5-5-explicit-parameter-passing"   # Story ID: {epic}-{story}-{slug}
-    type: story                             # enum: story | bug
-    epic: 5                                 # int for stories, null for bugs
-    title: "Explicit Parameter Passing"     # always quoted
-    priority: 1                             # sequential int, 1 = highest
-    status: backlog                         # from sprint-status.yaml
-    sprint: null                            # sprint-{id} if assigned, null if not
-    severity: null                          # null for stories
-  - id: "BUG-path-spaces"                  # Bug ID: BUG-{slug}
-    type: bug
-    epic: null                              # bugs don't belong to epics (FR64)
-    title: "Fix space-in-path bug"
-    priority: 2
-    status: backlog
-    sprint: "sprint-3"                      # assigned to sprint-3
-    severity: high                          # bug-specific: critical|high|medium|low
-```
-
-### Relationship to sprint-status.yaml
-
-- `sprint-status.yaml` continues to exist but is now a **derived view** — generated from `backlog.yaml` + `sprints/sprint-{id}.yaml` files
-- Story 17.8 implements the derivation logic
-- Until 17.8 lands, `sprint-status.yaml` remains the manual source of truth for story status
-- The `generate-backlog` skill READS status from `sprint-status.yaml` but NEVER WRITES to it
-
-### What Changes from Current Model
-
-| Aspect | Current (Epic 12) | New (Epic 17) |
-|---|---|---|
-| Priority source | Epic order in sprint-status.yaml | `priority` field in backlog.yaml |
-| Item ordering | Grouped by epic | Flat, interleaved by priority |
-| Bug inclusion | Discovered via glob, not in status file | First-class entries in backlog.yaml |
-| Sprint assignment | Only in sprint-plan files | Also annotated in backlog.yaml `sprint` field |
-| Done items | Remain in sprint-status.yaml forever | Excluded from backlog (archived in done/) |
-
-### Impact on Other Epic 17 Stories
-
-- **17.4 (Backlog-to-Sprint):** Reads backlog.yaml to present unassigned items, writes `sprint` field when assigning
-- **17.5 (Sprint-to-Backlog):** Clears `sprint` field when removing from sprint
-- **17.6 (Done Item Cleanup):** Removes done items from backlog.yaml
-- **17.7 (Prioritization):** Reorders `priority` field in backlog.yaml
-- **17.8 (Sprint Status Display):** Reads backlog.yaml for unassigned items section
-
-### Critical Guardrails (Story-Specific)
-
-- Do NOT modify any files under `_bmad/bmm/workflows/` or `_bmad/core/`
-- Do NOT add npm dependencies
-- Do NOT modify `lib/installer.js`, `lib/agents.js`, or `bin/cli.js`
-- Do NOT modify `sprint-status.yaml` — only READ from it for status lookup
-- Do NOT include `done` items in the backlog — they are archived
-- Do NOT auto-assign priorities based on severity or business value — initial generation uses epic order, subsequent prioritization is via Story 17.7
-- Backlog must preserve existing priority/sprint data on re-generation (idempotent merge)
-- Always quote the `title` field in YAML output
-- Bug entries MUST have `epic: null` (FR64)
-- **Modify SKILL.md, not just workflow.md** — SKILL.md is the file invoked by skill resolution
-
-### Project Structure Notes
-
-- **Files to create:**
-  - `lib/bmad-extension/skills/generate-backlog/SKILL.md` — new skill (authoritative)
-  - `lib/bmad-extension/skills/generate-backlog/bmad-skill-manifest.yaml` — skill manifest
-- **Files to modify:**
-  - `lib/bmad-extension/module-help.csv` — add generate-backlog row
-  - `_bmad-output/implementation-artifacts/sprint-management-guardrails.md` — add backlog schema, data authority rules (assumes Story 17.1 has renamed this file)
-- **Files to create (output):**
-  - `_bmad-output/implementation-artifacts/backlog.yaml` — generated output (not committed to template, generated at runtime)
-- **Files NOT to touch:**
-  - `_bmad-output/implementation-artifacts/sprint-status.yaml` (read-only from this workflow)
-  - Any files under `_bmad/` or `lib/installer.js`
-  - Sprint files under `sprints/` (read-only for sprint assignment lookup)
-
-### References
-
-- [Source: _bmad-output/planning-artifacts/epics.md#Epic 17, Story 17.2] — Story requirements and acceptance criteria
-- [Source: _bmad-output/planning-artifacts/prd.md#FR65] — Flat backlog model, not grouped by epic
-- [Source: _bmad-output/planning-artifacts/prd.md#FR66] — Sprint capacity as item count
-- [Source: _bmad-output/planning-artifacts/prd.md#FR128] — Bugs as story type in backlog
-- [Source: _bmad-output/planning-artifacts/prd.md#FR130] — Done items removed from sprint status
-- [Source: _bmad-output/implementation-artifacts/17-1-sprint-entity-model.md] — Sprint YAML schema, Item ID Format Contract
-- [Source: _bmad-output/implementation-artifacts/epic-11-12-shared-guardrails.md] — Current guardrails (to be renamed/updated by 17.1)
-- [Source: lib/bmad-extension/skills/add-to-sprint/SKILL.md] — Current add-to-sprint workflow that reads from sprint-status.yaml (to be reworked in 17.4)
-- [Source: lib/bmad-extension/skills/create-bug-story/SKILL.md] — Bug story creation workflow and file format
-- [Source: lib/bmad-extension/module-help.csv] — Workflow registration
-
-### Git Intelligence
-
-Recent commits show Epic 15/16 patterns. Key conventions:
-- Conventional commit format: `feat(epic-17): story 17-2 flat backlog model`
-- SKILL.md + bmad-skill-manifest.yaml is the standard skill package format
-- `module-help.csv` uses `skill:{name}` to resolve to SKILL.md
-
-## Change Log
-
-- 2026-03-30: Story implemented — generate-backlog skill created with flat backlog YAML schema, registered in module-help.csv, guardrails updated with backlog model and data authority rules.
-
-## Dev Agent Record
-
-### Agent Model Used
-
-Claude Opus 4.6 (1M context)
-
-### Debug Log References
-
-None — clean implementation.
-
-### Completion Notes List
-
-Created generate-backlog skill (SKILL.md + manifest). Registered in module-help.csv. Updated guardrails with backlog model schema.
-
-### File List
-
-- `lib/bmad-extension/skills/generate-backlog/SKILL.md` (new)
-- `lib/bmad-extension/skills/generate-backlog/bmad-skill-manifest.yaml` (new)
-- `lib/bmad-extension/module-help.csv` (modified)
-- `sprint-management-guardrails.md` (modified)

package/_bmad-output/implementation-artifacts/done/17-3-bug-as-story-type.md

@@ -1,208 +0,0 @@
-# Story 17.3: Bug as Story Type
-
-Status: review
-
-<!-- Note: Validation is optional. Run validate-create-story for quality check before dev-story. -->
-
-## Story
-
-As a **Test Engineer**,
-I want bugs to appear in the backlog alongside stories as a distinct type,
-So that bugs are prioritized and assigned to sprints using the same workflow as stories.
-
-## Acceptance Criteria
-
-1. **Given** a bug is created via the bug-story workflow (Epic 11, FR61),
-   **When** the bug story file is created,
-   **Then** it is added to the backlog with `type: bug`,
-   **And** it includes bug-specific fields: `severity` (critical/high/medium/low), `version_found`, `bug_type`.
-
-2. **Given** bugs and stories coexist in the backlog,
-   **When** the backlog is displayed or used for sprint planning,
-   **Then** bugs are visually distinguished (type field) but sorted by the same priority field as stories,
-   **And** a critical bug can be prioritized above any story.
-
-3. **Given** a bug follows the same lifecycle as a story,
-   **When** the bug progresses through statuses,
-   **Then** it uses the same flow: `backlog -> ready-for-dev -> in-progress -> review -> done`,
-   **And** done bugs are archived the same way as done stories (FR130, FR131).
-
-## Tasks / Subtasks
-
-- [x] Task 1: Extend bug story file format with new fields (AC: #1)
-  - [x] 1.1: Update `lib/bmad-extension/skills/create-bug-story/SKILL.md` to gather two additional optional fields:
-    - `version_found` (string, optional): The version/commit where the bug was found (e.g., "3.0.0", "commit abc123"). Press Enter to skip -> stored as empty string.
-    - `bug_type` (enum, optional): Classification of bug. Options: `regression | functional | performance | security | ui | data | integration | other`. Press Enter to skip -> defaults to `functional`.
-  - [x] 1.2: Add `version_found` and `bug_type` prompts as a new step between current Step 3 (expected/actual) and Step 4 (root cause):
-    - Prompt: "What version or commit was this bug found in? (optional, press Enter to skip)"
-    - Prompt: "What type of bug is this? [regression / functional / performance / security / ui / data / integration / other] (optional, defaults to functional)"
-    - Validate bug_type against the enum list; reject invalid values with error and re-prompt
-  - [x] 1.3: Update YAML frontmatter template in Step 6 to include new fields:
-    ```yaml
-    ---
-    type: bug
-    severity: {{severity}}
-    title: {{bug_title}}
-    version_found: "{{version_found}}"
-    bug_type: {{bug_type}}
-    status: backlog
-    ---
-    ```
-  - [x] 1.4: Add `status: backlog` to the YAML frontmatter — this is the initial lifecycle status for newly created bugs, enabling the backlog generator (Story 17.2) to read bug status directly from the file
-  - [x] 1.5: Update the confirmation display in Step 5 to show the new fields
-
-- [x] Task 2: Add backlog integration to create-bug-story (AC: #1, #2)
-  - [x] 2.1: After writing the bug file in Step 6, add a new Step 7 that checks if `backlog.yaml` exists:
-    - If exists: read it, append new bug entry at the end (lowest priority), re-number priorities, write back
-    - If not exists: note in output that user should run `/generate-backlog` to include this bug
-  - [x] 2.2: Bug entry format for backlog.yaml (per Story 17.2 schema):
-    ```yaml
-    - id: "BUG-{{title_slug}}"
-      type: bug
-      epic: null
-      title: "{{bug_title}}"
-      priority: {{next_priority}}
-      status: backlog
-      sprint: null
-      severity: {{severity}}
-    ```
-  - [x] 2.3: After appending to backlog, display: "Bug added to backlog at priority {{priority}}. Use `/prioritize-backlog` to adjust priority."
-
-- [x] Task 3: Update backlog schema for bug-specific fields (AC: #1, #2)
-  - [x] 3.1: Update `_bmad-output/implementation-artifacts/sprint-management-guardrails.md` Backlog Model section (added by Story 17.2) to document:
-    - Bug entries have `severity` field (non-null)
-    - Bug entries have `epic: null` (invariant)
-    - Bug entries use `BUG-{slug}` ID format (uppercase prefix)
-  - [x] 3.2: Document the bug lifecycle: `backlog -> ready-for-dev -> in-progress -> review -> done`
-  - [x] 3.3: Document that bug status is tracked in the bug file's YAML frontmatter `status` field (not in sprint-status.yaml)
-
-- [x] Task 4: Ensure lifecycle parity with stories (AC: #3)
-  - [x] 4.1: Verify that the dev-story workflow can process bug files (it reads the story file by path — bug files follow the same markdown structure with different frontmatter)
-  - [x] 4.2: Add a note in SKILL.md output that done bugs are archived by Story 17.6's cleanup process to `done/BUG-{slug}.md`
-  - [x] 4.3: Verify the create-bug-story SKILL.md slug derivation produces IDs compatible with the Item ID Format Contract from Story 17.1:
-    - Bug file: `bug-{slug}.md` (lowercase prefix)
-    - Bug ID in backlog/sprint: `BUG-{slug}` (uppercase prefix)
-    - These must use the same slug — just different prefix casing
-
-- [x] Task 5: Update module-help.csv description (AC: #1)
-  - [x] 5.1: Update the `create-bug-story` row in `lib/bmad-extension/module-help.csv` description to mention backlog integration:
-    - Current: "Create a structured bug story from a detected defect and add to backlog."
-    - Updated: "Create a structured bug story with severity and type classification, add to backlog.yaml."
-
-- [x] Task 6: Verify (AC: #1, #2, #3)
-  - [x] 6.1: Trace create-bug-story SKILL.md — confirm new fields are gathered, validated, and written to frontmatter
-  - [x] 6.2: Verify bug entry in backlog.yaml follows schema (type: bug, epic: null, severity present)
-  - [x] 6.3: Verify `version_found` and `bug_type` default handling (empty string and "functional" respectively)
-  - [x] 6.4: Verify `status: backlog` is in frontmatter for new bugs
-  - [x] 6.5: Verify slug derivation: `bug-{slug}.md` filename maps to `BUG-{slug}` backlog ID
-
-## Dev Notes
-
-### Architecture Compliance
-
-- **SKILL.md is the authoritative file:** The create-bug-story skill is at `lib/bmad-extension/skills/create-bug-story/SKILL.md`
-- **Extension module pattern:** Modifications stay in `lib/bmad-extension/skills/create-bug-story/`
-- **Backward compatible:** Existing bug files without `version_found`, `bug_type`, or `status` fields still work — the generate-backlog skill (17.2) treats missing fields as defaults
-- **Bug ID Format Contract:** Bug file is `bug-{slug}.md`, Bug ID in backlog/sprint is `BUG-{slug}` — same slug, different prefix casing
-
-### Extended Bug Frontmatter Schema
-
-```yaml
----
-type: bug                    # always "bug"
-severity: critical           # critical | high | medium | low
-title: "Login fails"         # always quoted
-version_found: "3.0.0"      # optional, empty string if skipped
-bug_type: regression         # regression|functional|performance|security|ui|data|integration|other
-status: backlog              # backlog|ready-for-dev|in-progress|review|done
----
-```
-
-### Bug Lifecycle (Same as Stories)
-
-```
-backlog -> ready-for-dev -> in-progress -> review -> done
-```
-
-- Bug status is tracked in the bug file's own YAML frontmatter `status` field
-- Stories track status in `sprint-status.yaml` — bugs do NOT appear there
-- Done bugs are archived to `done/BUG-{slug}.md` by Story 17.6
-
-### Backward Compatibility
-
-Existing `bug-*.md` files created before this story will not have `version_found`, `bug_type`, or `status` fields. Consumers must handle:
-- Missing `version_found` -> treat as empty/unknown
-- Missing `bug_type` -> treat as `functional`
-- Missing `status` -> treat as `backlog`
-
-### Impact on Other Epic 17 Stories
-
-- **17.2 (Flat Backlog):** generate-backlog reads bug frontmatter including new fields
-- **17.4 (Backlog-to-Sprint):** Displays bug type and severity in prioritization UI
-- **17.6 (Done Item Cleanup):** Archives done bugs to `done/` subfolder
-- **17.7 (Prioritization):** Uses severity as a prioritization criterion for bugs
-- **17.8 (Sprint Status Display):** Shows bug type distinction in sprint view
-
-### Critical Guardrails (Story-Specific)
-
-- Do NOT modify any files under `_bmad/bmm/workflows/` or `_bmad/core/`
-- Do NOT add npm dependencies
-- Do NOT modify `lib/installer.js`, `lib/agents.js`, or `bin/cli.js`
-- Do NOT modify `sprint-status.yaml` — bugs are NOT tracked there
-- Do NOT change existing bug file format in a breaking way — new fields are additive only
-- Bug entries in backlog MUST have `epic: null` (FR64)
-- Bug IDs MUST use `BUG-{slug}` format with uppercase prefix
-- `version_found` and `bug_type` MUST be optional (backward compatible with existing bugs)
-
-### Project Structure Notes
-
-- **Files to modify (primary):**
-  - `lib/bmad-extension/skills/create-bug-story/SKILL.md` — add version_found, bug_type, status fields; add backlog integration step
-  - `lib/bmad-extension/module-help.csv` — update create-bug-story description
-  - `_bmad-output/implementation-artifacts/sprint-management-guardrails.md` — document bug lifecycle and frontmatter schema
-- **Files NOT to touch:**
-  - `lib/bmad-extension/workflows/create-bug-story/workflow.md` — legacy copy, sync or leave (SKILL.md is authoritative)
-  - `sprint-status.yaml` — bugs are not tracked here
-  - Any files under `_bmad/` or `lib/installer.js`
-
-### References
-
-- [Source: _bmad-output/planning-artifacts/epics.md#Epic 17, Story 17.3] — Story requirements and acceptance criteria
-- [Source: _bmad-output/planning-artifacts/prd.md#FR128] — Bugs as story type in backlog with same lifecycle
-- [Source: _bmad-output/planning-artifacts/prd.md#FR65] — Flat backlog containing both stories and bugs
-- [Source: _bmad-output/planning-artifacts/prd.md#FR130] — Done items removed from sprint status
-- [Source: _bmad-output/planning-artifacts/prd.md#FR131] — Done story files moved to done/ subfolder
-- [Source: _bmad-output/implementation-artifacts/17-1-sprint-entity-model.md] — Item ID Format Contract (BUG-{slug})
-- [Source: _bmad-output/implementation-artifacts/17-2-flat-backlog-model.md] — Backlog YAML schema
-- [Source: lib/bmad-extension/skills/create-bug-story/SKILL.md] — Current bug creation workflow to extend
-- [Source: lib/bmad-extension/module-help.csv] — Workflow registration
-
-### Git Intelligence
-
-Recent commits show Epic 15/16 patterns. Key conventions:
-- Conventional commit format: `feat(epic-17): story 17-3 bug as story type`
-- SKILL.md modifications follow the additive pattern — extend, don't rewrite
-
-## Change Log
-
-- 2026-03-30: Story implemented — extended create-bug-story with version_found, bug_type, status fields and backlog integration.
-
-## Dev Agent Record
-
-### Agent Model Used
-
-Claude Opus 4.6 (1M context)
-
-### Debug Log References
-
-None — clean implementation.
-
-### Completion Notes List
-
-Extended create-bug-story SKILL.md with version_found, bug_type, status fields. Added backlog integration step. Updated module-help.csv description. Updated guardrails with bug lifecycle.
-
-### File List
-
-- `lib/bmad-extension/skills/create-bug-story/SKILL.md` (modified)
-- `lib/bmad-extension/module-help.csv` (modified)
-- `sprint-management-guardrails.md` (modified)