From a5ee6890f516ad7f6962f5c46d8c062824f57527 Mon Sep 17 00:00:00 2001 From: dave Date: Mon, 23 Mar 2026 17:58:23 +0000 Subject: [PATCH] storkit: create 376_story_rename_mcp_whatsup_tool_to_status_for_consistency --- ..._whatsup_tool_to_status_for_consistency.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 .storkit/work/1_backlog/376_story_rename_mcp_whatsup_tool_to_status_for_consistency.md diff --git a/.storkit/work/1_backlog/376_story_rename_mcp_whatsup_tool_to_status_for_consistency.md b/.storkit/work/1_backlog/376_story_rename_mcp_whatsup_tool_to_status_for_consistency.md new file mode 100644 index 0000000..8bf2b84 --- /dev/null +++ b/.storkit/work/1_backlog/376_story_rename_mcp_whatsup_tool_to_status_for_consistency.md @@ -0,0 +1,21 @@ +--- +name: "Rename MCP whatsup tool to status for consistency" +--- + +# Story 376: Rename MCP whatsup tool to status for consistency + +## User Story + +As a developer using storkit's MCP tools, I want the MCP tool to be called `status` instead of `whatsup`, so that the naming is consistent between the bot command (`status`), the web UI slash command (`/status`), and the MCP tool. + +## Acceptance Criteria + +- [ ] MCP tool is renamed from 'whatsup' to 'status' +- [ ] MCP tool is discoverable as 'status' via tools/list +- [ ] The tool still accepts a story_id parameter and returns the same triage data +- [ ] Old 'whatsup' tool name is removed from the MCP registry +- [ ] Any internal references to the whatsup tool name are updated + +## Out of Scope + +- TBD