diff --git a/.story_kit/work/1_upcoming/283_bug_pipeline_does_not_check_manual_qa_flag_before_advancing_from_qa_to_merge.md b/.story_kit/work/1_upcoming/283_bug_pipeline_does_not_check_manual_qa_flag_before_advancing_from_qa_to_merge.md
deleted file mode 100644
index e62be91..0000000
--- a/.story_kit/work/1_upcoming/283_bug_pipeline_does_not_check_manual_qa_flag_before_advancing_from_qa_to_merge.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-name: "Pipeline does not check manual_qa flag before advancing from QA to merge"
----
-
-# Bug 283: Pipeline does not check manual_qa flag before advancing from QA to merge
-
-## Description
-
-Story 247 added the manual_qa front matter field and the MCP tooling to set it, but the pipeline in pool.rs never actually checks the flag. After QA passes gates and coverage, stories move straight to merge regardless of manual_qa setting.
-
-## How to Reproduce
-
-1. Create a story with manual_qa: true in front matter
-2. Let it go through the coder and QA stages
-3. Observe that it moves directly to merge without waiting for human approval
-
-## Actual Result
-
-Stories always advance from QA to merge automatically, ignoring the manual_qa flag.
-
-## Expected Result
-
-Stories with manual_qa: true should pause after QA passes and wait for human approval before moving to merge. Stories with manual_qa: false (the default) should advance automatically as they do now.
-
-## Acceptance Criteria
-
-- [ ] Pipeline checks manual_qa front matter field after QA gates pass
-- [ ] manual_qa defaults to false — stories advance automatically unless explicitly opted in
-- [ ] Stories with manual_qa: true wait in 3_qa for human approval via accept_story or the UI
-- [ ] Stories with manual_qa: false proceed directly from QA to merge as before
diff --git a/.story_kit/work/1_upcoming/284_story_matrix_bot_status_command_shows_pipeline_and_agent_availability.md b/.story_kit/work/1_upcoming/284_story_matrix_bot_status_command_shows_pipeline_and_agent_availability.md
new file mode 100644
index 0000000..27523ac
--- /dev/null
+++ b/.story_kit/work/1_upcoming/284_story_matrix_bot_status_command_shows_pipeline_and_agent_availability.md
@@ -0,0 +1,22 @@
+---
+name: "Matrix bot status command shows pipeline and agent availability"
+---
+
+# Story 284: Matrix bot status command shows pipeline and agent availability
+
+## User Story
+
+As a user in a Matrix room, I want to type "{bot_name} status" and get a formatted summary of the full pipeline (upcoming through done) with agent assignments, plus which agents are currently free, so that I can check project status without leaving chat.
+
+## Acceptance Criteria
+
+- [ ] Chat command "{bot_name} status" triggers a pipeline status display (bot name comes from display_name in bot.toml)
+- [ ] Output shows all stages: upcoming, current, qa, merge, done — with story names and IDs
+- [ ] Each active story shows its assigned agent name and model
+- [ ] Output includes a section showing which agents are free (not currently assigned to any story)
+- [ ] Response is formatted for readability in Matrix (monospace or markdown as appropriate)
+- [ ] Command is handled at the bot level — does not require a full Claude invocation
+
+## Out of Scope
+
+- TBD