From 54d34d1a8567e4a69c7ab5b15aa338fadce03097 Mon Sep 17 00:00:00 2001 From: Dave Date: Fri, 20 Feb 2026 14:09:11 +0000 Subject: [PATCH] Add story 44: Agent Completion Report via MCP Co-Authored-By: Claude Opus 4.6 --- .../44_agent_completion_report_via_mcp.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 .story_kit/stories/upcoming/44_agent_completion_report_via_mcp.md diff --git a/.story_kit/stories/upcoming/44_agent_completion_report_via_mcp.md b/.story_kit/stories/upcoming/44_agent_completion_report_via_mcp.md new file mode 100644 index 0000000..fc5f218 --- /dev/null +++ b/.story_kit/stories/upcoming/44_agent_completion_report_via_mcp.md @@ -0,0 +1,22 @@ +--- +name: Agent Completion Report via MCP +test_plan: pending +--- + +# Story 44: Agent Completion Report via MCP + +## User Story + +As an agent finishing work on a story, I want to report my completion status via an MCP tool, so that the system can deterministically advance the workflow without relying on prompt compliance. + +## Acceptance Criteria + +- [ ] MCP tool report_completion(story_id, agent_name, summary) allows agents to signal they are done +- [ ] Server rejects the report if the agent's worktree has uncommitted changes +- [ ] Server runs acceptance gates (clippy, tests) automatically on report +- [ ] Completion status and results are stored on the agent record for retrieval by wait_for_agent or the supervisor +- [ ] Agent prompts are updated to call report_completion as their final action + +## Out of Scope + +- TBD