complete_story
Complete a story with a mandatory summary, validating that acceptance criteria are set and requiring explanations for any unchecked items before finalizing.
Instructions
Mark a story done and append a mandatory completion summary note in one atomic call. Validates acceptance criteria before completing: if the AC section has not been set (contains only the placeholder), completion is blocked — call set_acceptance_criteria first. IMPORTANT: if a criterion is actually done, mark it [x] in the story file via set_acceptance_criteria BEFORE calling this tool — do not leave it unchecked. If criteria remain unchecked (genuinely not done), incomplete_items is required with one explanation per unchecked item explaining WHY it was not completed (e.g. deferred, out of scope). incomplete_items is for unfinished work only — never use it to confirm completed work. On success, removes the story from backlog.md and returns {story_id, completed_at, backlog_removed}.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| incomplete_items | No | Required when the story has unchecked (genuinely unfinished) acceptance criteria. Each string must explain WHY that criterion was not met (e.g. 'Deferred to STORY-010 — rarity system not yet designed'). One entry per unchecked item, in the order they appear. DO NOT use this field to confirm items that are done — if a criterion is done, tick it [x] via set_acceptance_criteria first, then retry. Never prefix entries with 'Done:' — if it is done, it should not appear here at all. | |
| story_id | Yes | Story ID to complete, e.g. STORY-047 | |
| summary | Yes | Completion summary describing what was done. Appended as a timestamped note to the story file. |