diff --git a/.story_kit/work/1_upcoming/141_story_improve_server_logging_with_timestamps_and_error_visibility.md b/.story_kit/work/1_upcoming/141_story_improve_server_logging_with_timestamps_and_error_visibility.md
new file mode 100644
index 0000000..6899dde
--- /dev/null
+++ b/.story_kit/work/1_upcoming/141_story_improve_server_logging_with_timestamps_and_error_visibility.md
@@ -0,0 +1,22 @@
+---
+name: "Improve server logging with timestamps and error visibility"
+---
+
+# Story 141: Improve server logging with timestamps and error visibility
+
+## User Story
+
+As a developer operating the system, I want server logs to include timestamps and surface errors and warnings prominently, so that I can diagnose problems instead of guessing why things silently failed.
+
+## Acceptance Criteria
+
+- [ ] All log lines emitted by slog!() include an ISO 8601 timestamp prefix
+- [ ] Errors and warnings are logged at distinct severity levels (e.g. ERROR, WARN, INFO) so they can be filtered and stand out visually
+- [ ] Agent lifecycle failures (process crashes, gate failures, worktree setup failures, pipeline advancement errors) are logged at ERROR or WARN level rather than silently swallowed
+- [ ] MCP tool call failures are logged at WARN level with the tool name and error details
+- [ ] Permission request timeouts and denials are logged at WARN level
+- [ ] The get_server_logs MCP tool supports filtering by severity level (e.g. filter by ERROR to see only errors)
+
+## Out of Scope
+
+- TBD