Add story 44: Agent Completion Report via MCP
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -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
|
||||||
Reference in New Issue
Block a user