What problem does it solve? When an AI-assisted workflow stage finishes, users are often left unsure what to do next — whether to commit, which command to run, or whether to start a fresh session. This Skill standardizes the final output of any flow so every ending hands the user a concrete next move. ## Core Features & Use Cases - Four-field hand-back block: Prints Landed (what was produced and where), Yours now (user-only actions), Next command (with the argument filled in), and This session or a fresh one (with a one-clause reason). - Terminal-point triggering: Auto-loads at any flow ending — a finished stage, a verdict, a report, or a stop-with-a-question — so no ending is left ambiguous. - Guardrail enforcement: Forbids placeholder arguments, non-existent commands, blanket commit advice, and any suggestion to merge or push to trunk. - Use Case: After a ticket pipeline stage finishes green, the flow prints the commit sha, states nothing is left for the user, and gives the literal next command like /cut-backlog with a note to run it in a fresh session. ## Quick Start Ask the assistant to end the current workflow stage with a next-steps block that states what landed, what you must do, and the exact next command to run.