diff --git a/.story_kit/work/1_backlog/308_bug_token_cost_breakdown_missing_from_expanded_work_item_detail_panel.md b/.story_kit/work/1_backlog/308_bug_token_cost_breakdown_missing_from_expanded_work_item_detail_panel.md
deleted file mode 100644
index a6d4496..0000000
--- a/.story_kit/work/1_backlog/308_bug_token_cost_breakdown_missing_from_expanded_work_item_detail_panel.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-name: "Token cost breakdown missing from expanded work item detail panel"
----
-
-# Bug 308: Token cost breakdown missing from expanded work item detail panel
-
-## Description
-
-Story 300 implemented the token cost badge on the pipeline board but skipped the acceptance criterion for showing per-agent cost breakdown in the expanded work item detail panel. When you click into a story, there's no cost information visible.
-
-## How to Reproduce
-
-1. Click on a work item that has token usage data (cost badge visible on board)
-2. Look at the expanded detail panel
-3. No cost breakdown is shown
-
-## Actual Result
-
-Expanded work item detail panel shows no token cost information.
-
-## Expected Result
-
-Detail panel shows per-agent cost breakdown (coder, QA, mergemaster sessions) with token counts and cost in USD for the selected story.
-
-## Acceptance Criteria
-
-- [ ] WorkItemDetailPanel fetches token cost data using the existing /work-items/:story_id/token-cost endpoint
-- [ ] Shows per-agent session breakdown: agent name, model, token counts (input/output/cache), cost
-- [ ] Shows total cost for the story
-- [ ] Shows empty state when no token data exists
diff --git a/.story_kit/work/1_backlog/310_story_bot_delete_command_removes_a_story_from_the_pipeline.md b/.story_kit/work/1_backlog/310_story_bot_delete_command_removes_a_story_from_the_pipeline.md
new file mode 100644
index 0000000..530d8f3
--- /dev/null
+++ b/.story_kit/work/1_backlog/310_story_bot_delete_command_removes_a_story_from_the_pipeline.md
@@ -0,0 +1,24 @@
+---
+name: "Bot delete command removes a story from the pipeline"
+---
+
+# Story 310: Bot delete command removes a story from the pipeline
+
+## User Story
+
+As a project owner in a Matrix room, I want to type "{bot_name} delete {story_number}" to remove a story/bug/spike from the pipeline, so that I can clean up obsolete or duplicate work items from chat.
+
+## Acceptance Criteria
+
+- [ ] '{bot_name} delete {number}' finds the story/bug/spike by number across all pipeline stages and deletes the file
+- [ ] Confirms deletion with the story name and stage it was in
+- [ ] Returns a friendly message if no story with that number exists
+- [ ] Stops any running agent on the story before deleting
+- [ ] Removes the worktree if one exists for the story
+- [ ] Registered in the command registry so it appears in help output
+- [ ] Handled at bot level without LLM invocation
+- [ ] Commits the deletion to git
+
+## Out of Scope
+
+- TBD