diff --git a/docs/smoke-test.md b/docs/smoke-test.md
new file mode 100644
index 0000000..383ed4d
--- /dev/null
+++ b/docs/smoke-test.md
@@ -0,0 +1,30 @@
+# Chorus Smoke Test
+
+Run this after every deploy before considering a release done.
+
+## Manual-share path
+1. Share a text message (or a screenshot) from an Android phone to the
+   `#personal-text` channel in the Chorus Discord server via the native
+   Share Sheet.
+2. Confirm a ping appears in `#inbox` within a few seconds, tagging
+   `@chorus-triage` and showing a snippet.
+3. Open a thread on that ping.
+4. Confirm the thread gets a "Logged in Chorus" reply.
+5. Open the Chorus web app and confirm the item appears in the triage
+   list with modality `personal_text`, stage `new`.
+6. Click the item, set type to `Other`, stage to `Done`, save.
+7. Confirm the item disappears from the default (non-done) list view and
+   reappears when toggling "include done".
+
+## Auto-read path
+1. Send a real email to the BH email address configured in `.env`.
+2. Wait up to 2 minutes (poll interval) and confirm a ping appears in
+   `#inbox` with modality `bh_email` and a snippet of the email body.
+3. Open a thread on the ping, confirm ingestion, and confirm the item
+   appears in the web app with the correct sender/date.
+
+## Idempotency check
+1. Restart the bot container (`docker compose restart bot`) mid-way
+   through testing.
+2. Confirm no duplicate pings or duplicate triage rows appear for
+   messages already processed before the restart.