diff --git a/.story_kit/work/5_done/283_bug_pipeline_does_not_check_manual_qa_flag_before_advancing_from_qa_to_merge.md b/.story_kit/work/5_done/283_bug_pipeline_does_not_check_manual_qa_flag_before_advancing_from_qa_to_merge.md
new file mode 100644
index 0000000..e62be91
--- /dev/null
+++ b/.story_kit/work/5_done/283_bug_pipeline_does_not_check_manual_qa_flag_before_advancing_from_qa_to_merge.md
@@ -0,0 +1,30 @@
+---
+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