story-done

Auditing acceptance criteria involves cross-checking implementation, tests, and evidence paths to ensure every condition is met before a story is marked Complete. The skill automates this verification across Logic, Integration, Visual, UI, and Config stories.

Automating code-review gating enforces status checks, verifies evidence paths, and prompts for required code-review actions before updating the session state. This prevents stories from closing until all gating rules are satisfied.

Release gating rules are enforced by checking status, evidence paths, and required code-review actions across Logic, Integration, Visual/Feel, UI, and Config/Data stories. The story status updates only when all gating conditions pass.

Yes, you can surface the next ready story automatically after closing the current one. The session state updates upon completion to reflect status changes in production artifacts and immediately discover the next ready story.

You do not need to supply a story path manually to run story completion checks. You can supply the story path explicitly, or the skill will automatically use the active story to close the gate.