rai-story-close

To close a feature story, validate the retrospective, merge to the parent branch using a no-ff strategy, clean up the story branch, and update epic scope and tracking for traceability.

Story closure enforces prerequisites and artifact checks to prevent premature closures, requiring a completed retrospective and successful review before executing the merge and cleanup workflow.

The no-ff merge strategy preserves branch history during story closure, ensuring end-to-end traceability across merge commits, epic scope updates, and telemetry for auditability.

Yes, closing a story updates epic scope and local context to reflect completion, logging telemetry throughout the merge and cleanup process to maintain full auditability.

The best way to finalize a feature story is executing a closure workflow that validates artifacts, merges to the parent branch, deletes the story branch, and updates tracking.

You should not use a story closure workflow if the feature has not completed review or lacks a retrospective, as enforced artifact checks will prevent premature closures.