From a5c4fb553a479740216e59becf0afd6f89676600 Mon Sep 17 00:00:00 2001 From: Dave Date: Tue, 17 Mar 2026 16:41:47 +0000 Subject: [PATCH] story-kit: create 267_story_mcp_update_story_tool_should_support_front_matter_fields --- ...tool_should_support_front_matter_fields.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 .story_kit/work/1_upcoming/267_story_mcp_update_story_tool_should_support_front_matter_fields.md diff --git a/.story_kit/work/1_upcoming/267_story_mcp_update_story_tool_should_support_front_matter_fields.md b/.story_kit/work/1_upcoming/267_story_mcp_update_story_tool_should_support_front_matter_fields.md new file mode 100644 index 0000000..2fddf6a --- /dev/null +++ b/.story_kit/work/1_upcoming/267_story_mcp_update_story_tool_should_support_front_matter_fields.md @@ -0,0 +1,19 @@ +--- +name: "MCP update_story tool should support front matter fields" +--- + +# Story 267: MCP update_story tool should support front matter fields + +## User Story + +As an operator using the MCP tools, I want update_story to accept optional front matter fields (like agent, manual_qa, etc.) so that I can update story metadata without editing files by hand. + +## Acceptance Criteria + +- [ ] update_story MCP tool accepts optional agent parameter to set/change the agent front matter field +- [ ] update_story MCP tool accepts optional arbitrary front matter key-value pairs +- [ ] Front matter updates are auto-committed via the filesystem watcher like other story mutations + +## Out of Scope + +- TBD