ma-agents 3.6.2 → 3.9.0

package/lib/bmad-extension-plugin/skills/close-sprint/SKILL.md

@@ -0,0 +1,418 @@
+---
+name: close-sprint
+description: Close an active sprint — archive done/cancelled items, disposition incomplete items (move to next sprint or return to backlog), set sprint status to closed
+type: skill
+triggers:
+  - "close sprint"
+  - "close active sprint"
+---
+
+# Close Sprint Workflow
+
+Close an active sprint — archive done/cancelled items, disposition incomplete items (move to next sprint or return to backlog), and set sprint status to `closed`.
+
+**Schema Reference:** `_bmad-output/planning-artifacts/sprint-status-schema.md` (Story 17.9)
+
+## Backend Routing
+
+Before executing any file-system operations, determine and route to the correct backend:
+
+1. Read `_bmad-output/implementation-artifacts/sprint-status.yaml` and extract the `tracking_system` field.
+   If the field is absent or the file does not exist, default to `file-system`.
+
+2. If `tracking_system` is `file-system`:
+   Proceed with the **File-System Backend** instructions below.
+
+3. If `tracking_system` is `jira`:
+   a. Perform the Jira operation: Query all issues in the active sprint for project `{jira_project_key}` at `{jira_url}`. For done/cancelled items: transition each to resolved/done Jira state using the issue transition API; then move each corresponding local story file from `{story_location}/{id}.md` to `{story_location}/done/{id}.md` (local file operation — always executes). For incomplete items (not done/cancelled): remove each issue from the sprint using the "remove issue from sprint" operation (returns them to board backlog). Then close the sprint using the sprint close API.
+      Use whatever Jira-capable tool is available in your current tool context.
+      Map Jira entities to the canonical schema (Sprint → sprints[], Backlog → backlog[],
+      Epic → epics[], Jira status → canonical vocabulary per Section 6.3 of the routing spec).
+   b. If the Jira operation SUCCEEDS: continue with the Jira data returned. Jira is the source of truth.
+   c. If the Jira operation FAILS for any reason:
+      - If no Jira-capable tool is available in your current context:
+        Pause and present the user with:
+        > "No Jira-capable tool is available. To use Jira tracking, configure a Jira integration
+        > in your agent (an MCP server, plugin, or native integration connected to the Jira
+        > instance at `{jira_url}`). How would you like to proceed?
+        > (a) Retry — attempt the Jira operation again once a Jira tool is configured
+        > (b) Switch to file management — update sprint-status.yaml and config to use
+        >     file-system backend, then complete this operation locally. This change is permanent."
+      - If a Jira tool attempted the operation but returned an error:
+        Pause and present the user with:
+        > "The Jira operation failed: {actual Jira error details}. How would you like to proceed?
+        > (a) Retry — attempt the Jira operation again
+        > (b) Switch to file management — update sprint-status.yaml and config to use
+        >     file-system backend, then complete this operation locally. This change is permanent."
+      If user chooses (b) in either case: write `tracking_system: file-system` to `sprint-status.yaml`,
+      update `sprint_backend: file-system` in `_bmad/bmm/config.yaml`,
+      then proceed with **File-System Backend** instructions below.
+
+4. **File-System Backend** — execute the workflow steps below.
+
+---
+
+<workflow>
+
+<step n="0" goal="Load configuration and validate file existence">
+  <action>Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve `implementation_artifacts`</action>
+  <action>Set {{status_file}} = `{implementation_artifacts}/sprint-status.yaml`</action>
+
+  <check if="{{status_file}} does NOT exist">
+    <output>**Error:** No sprint-status.yaml found. Run sprint planning first to initialize the file.</output>
+    <action>Exit workflow</action>
+  </check>
+
+  <action>Read the FULL {{status_file}}</action>
+  <action>Parse into {{data}} with sections: metadata, `epics`, `backlog`, and `sprints`</action>
+  <action>Store {{story_location}} from {{data}}.metadata.story_location (e.g., `_bmad-output/implementation-artifacts`)</action>
+</step>
+
+<step n="1" goal="Identify the active sprint">
+  <action>Scan {{data}}.sprints for a sprint with `status: active`</action>
+  <check if="no active sprint found">
+    <output>No active sprint found. Nothing to close.</output>
+    <action>Exit workflow</action>
+  </check>
+  <action>Store the active sprint as {{active_sprint}} (id + full sprint data)</action>
+  <action>Store {{active_sprint_id}} = the sprint's map key (e.g., `sprint-1`)</action>
+</step>
+
+<step n="2" goal="Display sprint summary and confirm closure">
+  <action>Read {{active_sprint}}.items array</action>
+  <action>Store {{all_items}} = {{active_sprint}}.items</action>
+  <action>Store {{total_count}} = length of {{all_items}}</action>
+
+  <!-- Initialize counters and collections (always, to prevent undefined in summary output) -->
+  <action>Set {{done_count}} = 0</action>
+  <action>Set {{cancelled_count}} = 0</action>
+  <action>Set {{moved_to_sprint_count}} = 0</action>
+  <action>Set {{moved_to_sprint_name}} = ""</action>
+  <action>Set {{returned_to_backlog_count}} = 0</action>
+  <action>Set {{archived_done_files}} = []</action>
+  <action>Set {{archived_cancelled_files}} = []</action>
+  <action>Set {{skipped_done}} = []</action>
+  <action>Set {{skipped_cancelled}} = []</action>
+
+  <check if="{{total_count}} == 0">
+    <action>Set {{empty_sprint_fast_path}} = true</action>
+    <action>Jump to step 7 (empty sprint fast path)</action>
+  </check>
+
+  <action>Set {{empty_sprint_fast_path}} = false</action>
+  <action>Categorize items:
+    - {{done_items}} = items where status == `done`
+    - {{cancelled_items}} = items where status == `cancelled`
+    - {{incomplete_items}} = items where status is `ready-for-dev`, `in-progress`, `review`, or `on-hold`
+  </action>
+
+  <output>
+## Sprint Closure Summary: {{active_sprint.name}} ({{active_sprint_id}})
+
+**Total items:** {{total_count}}
+- Done: {{done_items.length}} (will be archived)
+- Cancelled: {{cancelled_items.length}} (will be archived)
+- Incomplete: {{incomplete_items.length}} (requires disposition)
+
+| # | ID | Title | Type | Status | Disposition |
+|---|----|----|----|----|---|
+{{#each done_items}}
+| {{@index+1}} | {{id}} | {{title}} | {{type}} | done | archive to done/ |
+{{/each}}
+{{#each cancelled_items}}
+| {{@index+1}} | {{id}} | {{title}} | {{type}} | cancelled | archive to done/ |
+{{/each}}
+{{#each incomplete_items}}
+| {{@index+1}} | {{id}} | {{title}} | {{type}} | {{status}} | pending decision |
+{{/each}}
+  </output>
+
+  <ask>Proceed with sprint closure? [c] Confirm and proceed / [x] Cancel:</ask>
+  <check if="user selects 'x'">
+    <output>Sprint closure cancelled. No changes made.</output>
+    <action>Exit workflow</action>
+  </check>
+</step>
+
+<step n="3" goal="Archive done items (AC: 2)">
+  <check if="{{done_items}} is empty">
+    <action>Skip to step 4 (done_count stays 0, archived_done_files stays [])</action>
+  </check>
+
+  <action>Ensure `{{story_location}}/done/` directory exists. If it does not exist, create it.</action>
+
+  <action>For each item in {{done_items}}:
+    1. Resolve source path: `{{story_location}}/{{item.id}}.md`
+       - For bug items (type == bug): also try `{{story_location}}/bug-{{item.id_slug}}.md` as fallback (handle case variations)
+    2. Resolve destination path: `{{story_location}}/done/{{item.id}}.md`
+    3. If source file does NOT exist:
+       - Log warning: "File not found: {{source_path}} — skipping file move."
+       - Add item to {{skipped_done}} with reason "source missing"
+       - Continue to next item
+    4. If destination file ALREADY EXISTS in done/:
+       - Log warning: "File already exists at destination: {{destination_path}} — skipping file move."
+       - Add item to {{skipped_done}} with reason "destination exists"
+       - Continue to next item
+    5. Move (rename) the file: source → destination
+    6. Add item to {{archived_done_files}}
+  </action>
+
+  <action>Remove ALL done items from {{active_sprint}}.items in {{data}}</action>
+  <action>Store {{done_count}} = length of {{done_items}}</action>
+</step>
+
+<step n="4" goal="Archive cancelled items (AC: 3)">
+  <check if="{{cancelled_items}} is empty">
+    <action>Skip to step 5 (cancelled_count stays 0, archived_cancelled_files stays [])</action>
+  </check>
+
+  <action>Ensure `{{story_location}}/done/` directory exists (may already exist from step 3)</action>
+
+  <action>For each item in {{cancelled_items}}:
+    1. Resolve source path: `{{story_location}}/{{item.id}}.md`
+       - For bug items (type == bug): also try `{{story_location}}/bug-{{item.id_slug}}.md` as fallback (handle case variations)
+    2. Resolve destination path: `{{story_location}}/done/{{item.id}}.md`
+    3. If source file does NOT exist:
+       - Log warning: "File not found: {{source_path}} — skipping file move."
+       - Add item to {{skipped_cancelled}} with reason "source missing"
+       - Continue to next item
+    4. If destination file ALREADY EXISTS in done/:
+       - Log warning: "File already exists at destination: {{destination_path}} — skipping file move."
+       - Add item to {{skipped_cancelled}} with reason "destination exists"
+       - Continue to next item
+    5. Move (rename) the file: source → destination
+    6. Add item to {{archived_cancelled_files}}
+  </action>
+
+  <action>Remove ALL cancelled items from {{active_sprint}}.items in {{data}}</action>
+  <action>Store {{cancelled_count}} = length of {{cancelled_items}}</action>
+</step>
+
+<step n="5" goal="Disposition incomplete items (AC: 4, 11)">
+  <check if="{{incomplete_items}} is empty">
+    <action>Skip to step 6</action>
+  </check>
+
+  <output>
+## Incomplete Items Requiring Disposition
+
+| # | ID | Title | Type | Status |
+|---|----|----|----|----|
+{{#each incomplete_items}}
+| {{@index+1}} | {{id}} | {{title}} | {{type}} | {{status}} |
+{{/each}}
+
+**Options:**
+**(a)** Move all to the next sprint
+**(b)** Return all to backlog
+**(c)** Decide per item
+  </output>
+
+  <ask>Choose disposition option [a/b/c]:</ask>
+
+  <!-- OPTION A: Move all to next sprint -->
+  <check if="user selects 'a'">
+    <action>Scan {{data}}.sprints for sprints with `status: planning`</action>
+    <action>Store {{planning_sprints}} = list of planning sprints</action>
+
+    <check if="{{planning_sprints}} is empty">
+      <output>**No planning sprint found.** Run `/add-sprint` to create one, or choose option (b) to return items to backlog.</output>
+      <ask>Choose disposition option [b] Return all to backlog / [c] Decide per item:</ask>
+      <check if="user selects 'b'"><goto option_b /></check>
+      <check if="user selects 'c'"><goto option_c /></check>
+    </check>
+
+    <check if="{{planning_sprints}}.length > 1">
+      <output>
+## Planning Sprints Available
+
+| # | Sprint | Capacity | Items | Remaining |
+|---|---|---|---|---|
+{{#each planning_sprints}}
+| {{@index+1}} | {{name}} ({{id}}) | {{capacity}} | {{items_count}} | {{remaining}} |
+{{/each}}
+      </output>
+      <ask>Select target sprint (enter number):</ask>
+      <action>Store {{target_sprint}} = selected planning sprint</action>
+    </check>
+
+    <check if="{{planning_sprints}}.length == 1">
+      <action>Store {{target_sprint}} = {{planning_sprints}}[0]</action>
+    </check>
+
+    <action>Calculate {{new_count}} = {{target_sprint}}.items.length + {{incomplete_items}}.length</action>
+    <check if="{{new_count}} > {{target_sprint}}.capacity">
+      <output>**Capacity Warning:** Adding {{incomplete_items.length}} items would bring {{target_sprint.name}} to {{new_count}}/{{target_sprint.capacity}} capacity (exceeds limit). Proceeding anyway (capacity is advisory).</output>
+    </check>
+
+    <action>For each item in {{incomplete_items}}:
+      1. REMOVE the item from {{active_sprint}}.items in {{data}}
+      2. ADD the item to {{target_sprint}}.items in {{data}}
+      3. PRESERVE the item's current `status` unchanged (no reset)
+    </action>
+    <action>Store {{moved_to_sprint_count}} = length of {{incomplete_items}}</action>
+    <action>Store {{moved_to_sprint_name}} = {{target_sprint}}.name</action>
+    <action>Store {{returned_to_backlog_count}} = 0</action>
+  </check>
+
+  <!-- OPTION B: Return all to backlog -->
+  <check if="user selects 'b'" id="option_b">
+    <action>Calculate {{max_priority}} = max `priority` value among all items currently in {{data}}.backlog (0 if backlog is empty)</action>
+
+    <action>For each item in {{incomplete_items}} (processing in order):
+      1. REMOVE the item from {{active_sprint}}.items in {{data}}
+      2. SET item.status = `ready-for-dev` (schema section 4.5 — status reset on backlog return)
+      3. SET item.priority = {{max_priority}} + 1 (then increment {{max_priority}} for the next item)
+      4. APPEND the item to the END of {{data}}.backlog
+      5. PRESERVE all other fields: `id`, `type`, `epic`, `title`, `severity`
+    </action>
+
+    <action>Re-number ALL {{data}}.backlog items' `priority` fields sequentially 1..N (array position 0 = priority 1) to maintain the denormalized index invariant</action>
+    <action>Store {{returned_to_backlog_count}} = length of {{incomplete_items}}</action>
+    <action>Store {{moved_to_sprint_count}} = 0</action>
+    <action>Store {{moved_to_sprint_name}} = ""</action>
+  </check>
+
+  <!-- OPTION C: Per-item decision -->
+  <check if="user selects 'c'" id="option_c">
+    <action>Initialize {{per_item_sprint_targets}} = {} and {{per_item_backlog}} = []</action>
+    <action>Initialize {{moved_to_sprint_count}} = 0 and {{returned_to_backlog_count}} = 0</action>
+
+    <action>For each item in {{incomplete_items}} (iterate one by one):
+      Display: "**Item:** {{item.id}} — {{item.title}} (status: {{item.status}})"
+    </action>
+    <ask>**[s]** Move to next sprint / **[b]** Return to backlog:</ask>
+
+    <check if="user selects 's'">
+      <action>Scan {{data}}.sprints for sprints with `status: planning`</action>
+      <check if="no planning sprint exists">
+        <output>No planning sprint found. Returning this item to the backlog instead.</output>
+        <action>Add item to {{per_item_backlog}}</action>
+      </check>
+      <check if="planning sprint(s) exist">
+        <check if="multiple planning sprints">
+          <output>Select target sprint:</output>
+          <ask>Planning sprint number:</ask>
+          <action>Store selected sprint as {{item_target_sprint}}</action>
+        </check>
+        <check if="single planning sprint">
+          <action>Store as {{item_target_sprint}}</action>
+        </check>
+        <action>Check capacity warning (same advisory logic as option a)</action>
+        <action>REMOVE item from {{active_sprint}}.items in {{data}}</action>
+        <action>ADD item to {{item_target_sprint}}.items in {{data}} preserving current status</action>
+        <action>Increment {{moved_to_sprint_count}}</action>
+      </check>
+    </check>
+
+    <check if="user selects 'b'">
+      <action>Add item to {{per_item_backlog}}</action>
+    </check>
+
+    <action>After all per-item decisions, process {{per_item_backlog}}:
+      1. Calculate {{max_priority}} = max `priority` value among all items in {{data}}.backlog (0 if empty)
+      2. For each item in {{per_item_backlog}}:
+         - REMOVE item from {{active_sprint}}.items in {{data}}
+         - SET item.status = `ready-for-dev`
+         - SET item.priority = {{max_priority}} + 1 (then increment for next)
+         - APPEND to END of {{data}}.backlog
+      3. Re-number ALL {{data}}.backlog items' `priority` fields sequentially 1..N
+      4. Set {{returned_to_backlog_count}} = length of {{per_item_backlog}}
+    </action>
+    <action>Store {{moved_to_sprint_name}} = name of the planning sprint used (if any items moved to sprint)</action>
+  </check>
+</step>
+
+<step n="6" goal="Validate single-location invariant before write">
+  <action>Build a flat list of all item IDs across {{data}}.backlog and all sprints in {{data}}.sprints</action>
+  <action>Check for any ID that appears more than once across all locations</action>
+  <check if="any duplicate ID found">
+    <output>**Error:** Data integrity violation — item {{duplicate_id}} appears in more than one location. Aborting write to prevent data corruption. Please report this as a bug in the skill.</output>
+    <action>Exit workflow without writing</action>
+  </check>
+</step>
+
+<step n="7" goal="Finalize sprint closure (AC: 5, 8)">
+  <action>Set {{data}}.sprints.{{active_sprint_id}}.status = `closed`</action>
+  <action>Verify {{data}}.sprints.{{active_sprint_id}}.items is now empty (`[]`)</action>
+  <check if="items array is NOT empty">
+    <output>**Warning:** Sprint items array is not empty after disposition. This may indicate a processing error. Proceeding with closure anyway — remaining items are listed below for manual review.</output>
+  </check>
+  <action>Update {{data}}.metadata.last_updated = current ISO-8601 timestamp</action>
+  <action>Preserve {{data}}.metadata.generated unchanged</action>
+  <action>Preserve {{data}}.epics unchanged</action>
+  <action>Preserve all other sprints in {{data}}.sprints unchanged</action>
+
+  <critical>Write the complete updated {{data}} to {{status_file}} as a SINGLE atomic write. This one write includes: item removals from the active sprint, backlog additions, next-sprint additions, sprint status change to closed, and metadata update.</critical>
+</step>
+
+<step n="8" goal="Display summary output">
+  <!-- Handle empty sprint fast path from step 2 -->
+  <check if="{{empty_sprint_fast_path}} == true">
+    <output>
+## Sprint Closed Successfully
+
+**Sprint:** {{active_sprint.name}} ({{active_sprint_id}})
+**Status:** closed
+
+Sprint {{active_sprint.name}} closed. No items to disposition.
+
+**Next Steps:**
+- Use `/add-sprint` to create the next sprint
+- Use `/sprint-status-view` to review the updated status
+    </output>
+    <action>Exit workflow</action>
+  </check>
+
+  <output>
+## Sprint Closed Successfully
+
+**Sprint:** {{active_sprint.name}} ({{active_sprint_id}})
+**Status:** closed
+
+**Disposition:**
+- Done items archived: {{done_count}}
+- Cancelled items archived: {{cancelled_count}}
+{{#if moved_to_sprint_count}}
+- Items moved to {{moved_to_sprint_name}}: {{moved_to_sprint_count}}
+{{/if}}
+{{#if returned_to_backlog_count}}
+- Items returned to backlog: {{returned_to_backlog_count}}
+{{/if}}
+
+{{#if archived_done_files.length}}
+**Files moved to done/:**
+{{#each archived_done_files}}
+- {{id}} → done/
+{{/each}}
+{{/if}}
+
+{{#if archived_cancelled_files.length}}
+**Cancelled files moved to done/:**
+{{#each archived_cancelled_files}}
+- {{id}} → done/
+{{/each}}
+{{/if}}
+
+{{#if skipped_done.length}}
+**Skipped (warnings):**
+{{#each skipped_done}}
+- {{id}} — {{reason}}
+{{/each}}
+{{/if}}
+
+{{#if skipped_cancelled.length}}
+**Skipped (warnings):**
+{{#each skipped_cancelled}}
+- {{id}} — {{reason}}
+{{/each}}
+{{/if}}
+
+**Next Steps:**
+- Use `/add-sprint` to create the next sprint
+- Use `/prioritize-backlog` to reorder the backlog after returns
+- Use `/sprint-status-view` to review the updated status
+  </output>
+</step>
+
+</workflow>

package/lib/bmad-extension-plugin/skills/close-sprint/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: close-sprint
+module: ma-skills

package/lib/bmad-extension-plugin/skills/create-bug-story/SKILL.md

@@ -0,0 +1,195 @@
+---
+name: create-bug-story
+description: Guided workflow to create a structured bug story from a detected defect
+type: skill
+triggers:
+  - "create bug story"
+  - "report bug"
+---
+
+# Create Bug Story Workflow
+
+Guided workflow to create a structured bug story from a detected defect and add it to the backlog as a standalone item.
+
+<workflow>
+
+<step n="1" goal="Gather bug title and severity">
+  <action>Explain: This workflow creates a structured bug story file that enters the backlog alongside user stories.</action>
+  <ask>What is the bug title? (short, descriptive — e.g., "Login fails with empty password field")</ask>
+  <action>Store as {{bug_title}}</action>
+  <action>Validate {{bug_title}} is not empty</action>
+  <check if="{{bug_title}} is empty">
+    <output>❌ Bug title cannot be empty.</output>
+    <goto step="1" />
+  </check>
+
+  <output>
+**Severity levels:**
+- `critical` — Data loss, security breach, or system crash in normal usage
+- `high` — Core feature broken or serious security risk; blocks users
+- `medium` — Feature partially broken or degraded; workaround exists
+- `low` — Minor issue, cosmetic defect, or edge case with minimal user impact
+  </output>
+  <ask>What is the severity? [critical / high / medium / low]</ask>
+  <action>Store as {{severity}}</action>
+  <action>Normalize to lowercase</action>
+  <check if="{{severity}} is not one of: critical, high, medium, low">
+    <output>❌ Severity must be one of: critical, high, medium, low.</output>
+    <goto step="1" />
+  </check>
+</step>
+
+<step n="2" goal="Gather affected component and reproduction steps">
+  <ask>What is the affected component? (e.g., "auth module", "login page", "installer pipeline")</ask>
+  <action>Store as {{affected_component}}</action>
+
+  <ask>What are the reproduction steps? (numbered steps to reproduce the bug — describe them one at a time or as a list)</ask>
+  <action>Store as {{reproduction_steps}}</action>
+</step>
+
+<step n="3" goal="Gather expected vs actual behavior">
+  <ask>What is the expected behavior? (what should happen when working correctly)</ask>
+  <action>Store as {{expected_behavior}}</action>
+
+  <ask>What is the actual behavior? (what actually happens — the defect)</ask>
+  <action>Store as {{actual_behavior}}</action>
+</step>
+
+<step n="4" goal="Gather root cause hypothesis and affected files">
+  <ask>What is your root cause hypothesis? (optional — press Enter to skip; e.g., "Null check missing in validateUser()")</ask>
+  <action>Store as {{root_cause}} (empty string if skipped)</action>
+
+  <ask>What files are affected? (optional — comma-separated paths relative to repo root, press Enter to skip)</ask>
+  <action>Store as {{affected_files}} (empty string if skipped)</action>
+  <action>If provided, split by comma and trim whitespace to form a list of file paths</action>
+
+  <ask>Is there a suggested fix? (optional — brief description or press Enter to skip)</ask>
+  <action>Store as {{suggested_fix}} (empty string if skipped)</action>
+</step>
+
+<step n="5" goal="Confirm all bug details before writing">
+  <action>Derive {{title_slug}} by converting {{bug_title}} to lowercase kebab-case:
+    - Convert to lowercase
+    - Replace spaces and underscores with hyphens
+    - Remove characters that are not alphanumeric or hyphens
+    - Collapse consecutive hyphens into one
+    - Trim leading/trailing hyphens
+  </action>
+  <action>Set {{output_file}} = `_bmad-output/implementation-artifacts/bug-{{title_slug}}.md`</action>
+
+  <output>
+## Bug Story Summary — Please Confirm
+
+- **Title:** {{bug_title}}
+- **Severity:** {{severity}}
+- **Affected Component:** {{affected_component}}
+- **Reproduction Steps:** {{reproduction_steps}}
+- **Expected Behavior:** {{expected_behavior}}
+- **Actual Behavior:** {{actual_behavior}}
+- **Root Cause Hypothesis:** {{root_cause}} *(empty if skipped)*
+- **Affected Files:** {{affected_files}} *(empty if skipped)*
+- **Suggested Fix:** {{suggested_fix}} *(empty if skipped)*
+- **Output File:** `{{output_file}}`
+  </output>
+  <ask>Confirm creation? [y] Yes / [n] Cancel / [e] Edit a field:</ask>
+  <check if="user selects 'e'">
+    <ask>Which field to edit? (title / severity / component / steps / expected / actual / root-cause / files / fix)</ask>
+    <check if="field == 'title' OR field == 'severity'"><goto step="1" /></check>
+    <check if="field == 'component' OR field == 'steps'"><goto step="2" /></check>
+    <check if="field == 'expected' OR field == 'actual'"><goto step="3" /></check>
+    <check if="field == 'root-cause' OR field == 'files' OR field == 'fix'"><goto step="4" /></check>
+    <check if="none of the above matched">
+      <output>❌ Unrecognized field. Valid options: title / severity / component / steps / expected / actual / root-cause / files / fix</output>
+      <goto step="5" />
+    </check>
+  </check>
+  <check if="user selects 'n'">
+    <output>❌ Bug story creation cancelled.</output>
+    <action>Exit workflow</action>
+  </check>
+</step>
+
+<step n="6" goal="Write bug story file">
+  <action>Check if {{output_file}} already exists</action>
+  <check if="file already exists">
+    <output>⚠️ A bug story already exists at `{{output_file}}`.</output>
+    <ask>Overwrite? [y] Yes — overwrite existing / [n] Cancel / [s] Save with unique suffix (e.g. bug-{{title_slug}}-2.md):</ask>
+    <check if="user selects 's'">
+      <action>Find the next available suffix: try bug-{{title_slug}}-2.md, -3.md, etc. until a filename that does not exist is found. Set {{output_file}} to that path.</action>
+    </check>
+    <check if="user selects 'n'">
+      <output>❌ Bug story creation cancelled to preserve existing file.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+  <action>Write bug story to {{output_file}} using the template below.
+    CRITICAL: The YAML frontmatter block MUST be the very first content in the file — no blank lines, no title, nothing before the opening `---`.
+    Format optional fields (root_cause, affected_files, suggested_fix) as follows:
+      - If {{root_cause}} is empty, write: `_Not identified_`
+      - If {{affected_files}} is empty, write: `_Unknown_`; otherwise list each file as a `- path/to/file` bullet
+      - If {{suggested_fix}} is empty, omit the Suggested Fix section entirely
+  </action>
+
+  <action>Write file with this exact structure:
+
+```
+---
+type: bug
+severity: {{severity}}
+title: {{bug_title}}
+---
+
+# Bug: {{bug_title}}
+
+**Severity:** {{severity}}
+**Affected Component:** {{affected_component}}
+
+## Reproduction Steps
+
+{{reproduction_steps}}
+
+## Expected Behavior
+
+{{expected_behavior}}
+
+## Actual Behavior
+
+{{actual_behavior}}
+
+## Root Cause Hypothesis
+
+{{root_cause or "_Not identified_"}}
+
+## Affected Files
+
+{{affected_files list or "_Unknown_"}}
+
+## Suggested Fix
+
+{{suggested_fix — omit section if empty}}
+
+## Notes
+
+- Created via `create-bug-story` workflow
+- Discoverable by sprint workflows via glob: `_bmad-output/implementation-artifacts/bug-*.md`
+- To add to a sprint, run `/add-to-sprint`
+```
+  </action>
+
+  <output>
+✅ **Bug story created successfully!**
+
+- **File:** `{{output_file}}`
+- **Title:** {{bug_title}}
+- **Severity:** {{severity}}
+- **Component:** {{affected_component}}
+
+**Next Steps:**
+- Use `/add-to-sprint` to assign this bug to the current sprint
+- Use `/sprint-status-view` to see all sprint items including this bug
+- To detect more bugs, ensure the `auto-bug-detection` skill is loaded in your session
+  </output>
+</step>
+
+</workflow>

package/lib/bmad-extension-plugin/skills/create-bug-story/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: create-bug-story
+module: ma-skills

package/lib/bmad-extension-plugin/skills/cyber-generate-certs/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: cyber-generate-certs
+description: Generate self-signed certificates using the self-signed-cert skill
+type: skill
+triggers:
+  - "generate certs"
+  - "generate certificates"
+---
+
+# workflow-generate-certs.md
+# Secure Certificate Generation Workflow
+
+Automated workflow for generating self-signed certificates using the `self-signed-cert` skill.
+
+## Instructions
+1.  **Load Skill**: Activate the `self-signed-cert` skill instructions.
+2.  **Requirement Analysis**: Determine common name (CN) and Subject Alternative Names (SANs).
+3.  **Execution**:
+    - **Linux/macOS**:
+        - `bash scripts/generate-cert.sh root my-internal-ca`
+        - `bash scripts/generate-cert.sh cert my-service localhost`
+    - **Windows**:
+        - `.\scripts\generate-cert.ps1 -Type root -Name my-internal-ca`
+        - `.\scripts\generate-cert.ps1 -Type cert -Name my-service -Dns localhost`
+4.  **Packaging**: Provide instructions for importing the cert into trust stores (OS, Browsers) or mounting in Kubernetes secrets.
+5.  **Security**: Ensure private keys are stored with restricted permissions (600).
+6.  **Rotation**: Offer a schedule for certificate renewal.

package/lib/bmad-extension-plugin/skills/cyber-generate-certs/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: cyber-generate-certs
+module: ma-skills