merge-readiness

<Purpose> Merge Readiness is a post-task explainability gate. After implementation, tests, QA, and review evidence exist, it generates a human-readable explanation of the change, then asks the human targeted questions to verify they can explain why the change exists, what changed, what tradeoffs were made, what risks were considered, and how the team should understand it. </Purpose> <Use_When> - A task, PR, or change set is functionally complete and needs a final human-understanding check before merge readiness - Tests, QA, code review, security review, or other verification has already run, or missing evidence must be explicitly recorded - The user wants AI to explain the change and then quiz the human on whether they can explain it - You need a durable session audit record showing why the team can trust and understand the change before asking for merge approval </Use_When> <Do_Not_Use_When> - Requirements are still unclear before implementation; use `/deep-interview` - The implementation is not done; use `/ralph`, `/team`, or `/autopilot` - Tests or QA have not run and the user expects this command to replace them - The user wants code review findings; use `/review` or the relevant review workflow </Do_Not_Use_When> <Why_This_Exists> Real delivery is not only code that works. Teams need to understand why a change exists, what changed, what was deliberately not done, which risks were considered, and what future maintainers should believe about the change. This workflow ma...