story-kit: done 304_story_mcp_tool_to_move_stories_between_pipeline_stages

This commit is contained in:
Dave
2026-03-19 10:59:50 +00:00
parent f4376b01e1
commit b6f99ce7a2
2 changed files with 23 additions and 21 deletions

View File

@@ -1,21 +0,0 @@
---
name: "Bot show command displays story text in chat"
---
# Story 305: Bot show command displays story text in chat
## User Story
As a project owner in a Matrix room, I want to type "{bot_name} show {story_number}" and see the full story text displayed in chat, so that I can review story details without accessing the file system.
## Acceptance Criteria
- [ ] '{bot_name} show {number}' finds the story/bug/spike by number across all pipeline stages and displays its full markdown content
- [ ] Output is formatted for readability in Matrix
- [ ] Returns a friendly message if no story with that number exists
- [ ] Registered in the command registry so it appears in help output
- [ ] Handled at bot level without LLM invocation
## Out of Scope
- TBD

View File

@@ -0,0 +1,23 @@
---
name: "MCP tool to move stories between pipeline stages"
---
# Story 304: MCP tool to move stories between pipeline stages
## User Story
As a bot operator (Timmy), I want an MCP tool that moves stories between pipeline stages, so that I don't need shell mv permissions to manage the pipeline.
## Acceptance Criteria
- [ ] New MCP tool 'move_story' accepts story_id and target_stage (e.g. 'backlog', 'current', 'qa', 'merge', 'done')
- [ ] Validates the story exists before moving
- [ ] Handles the file move between stage directories
- [ ] Returns a confirmation message with the old and new stage
- [ ] Works for stories, bugs, spikes, and refactors
- [ ] Replaces the need for shell mv commands to move story files
- [ ] Tool description tells bots to prefer specific tools (accept_story, move_story_to_merge, request_qa) when available, and use move_story only for arbitrary moves that lack a dedicated tool (e.g. moving to backlog, moving ghost stories back to current)
## Out of Scope
- TBD