From 1f5a384cbbe5a6cd4d3f1e97d13c3b994a6a278b Mon Sep 17 00:00:00 2001 From: Dave Date: Mon, 23 Feb 2026 14:49:40 +0000 Subject: [PATCH] story-kit: create 78_story_create_spike_mcp_tool --- .../78_story_create_spike_mcp_tool.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 .story_kit/work/1_upcoming/78_story_create_spike_mcp_tool.md diff --git a/.story_kit/work/1_upcoming/78_story_create_spike_mcp_tool.md b/.story_kit/work/1_upcoming/78_story_create_spike_mcp_tool.md new file mode 100644 index 0000000..127c594 --- /dev/null +++ b/.story_kit/work/1_upcoming/78_story_create_spike_mcp_tool.md @@ -0,0 +1,22 @@ +--- +name: "Create spike MCP tool" +test_plan: pending +--- + +# Story 78: Create spike MCP tool + +## User Story + +As a user, I want to create spikes via the MCP API, so that spike work items are created consistently with proper YAML front matter just like stories and bugs. + +## Acceptance Criteria + +- [ ] A create_spike MCP tool exists with name and description parameters +- [ ] create_spike_file function in server/src/http/workflow.rs generates a properly formatted spike markdown file with YAML front matter +- [ ] The spike file is created in .story_kit/work/1_upcoming/ with the naming pattern N_spike_slug.md +- [ ] The name value is quoted in front matter to handle YAML-special characters +- [ ] cargo clippy and cargo test pass + +## Out of Scope + +- TBD