← the whole session plugin/skills/on-turn-end/SKILL.md
Run at the end of any substantive turn that produced a work product with a governer score above your configured threshold. Routes you to the right consumption skill so the person you're working with can see, understand, and act on what you did in seconds — never reading pages of output to figure out what you were working on, which part you just touched, or where to look at it. Skip for pure conversation/brainstorm with no work product.
on-turn-end
You are requested to run this command anytime you complete a substantive turn that involves any work product being produced in any form that has a governer score above the configured threshold — the switch turnEnd.scoreAbove, default 40, the same number the end-of-turn hook uses (alignment-harness status shows the session score). If you are in a conversation and just replying, like a brainstorm, do not invoke this skill. This skill will orient you to what exactly is wanted from you.
If you can't get a score for this turn (governer hasn't been set up or run yet), don't silently skip — run this routing anyway for any turn that visibly changed a file or produced a result, and say plainly that you're doing so because no score was available.
When you complete a turn, if:
you have user-facing work product that you have completed, invoke /consume so that you can demonstrate to the person in seconds what exactly you got done, and they can see it.
you have a bug that you fixed, invoke /consume so that you can show the person exactly what the UX is now that it's fixed, and tell them the exact steps to see it themselves.
you have remaining scope that is large, define the next substantive milestone you believe works towards the intent and invoke /gap to show it to them, then invoke /propose so they can approve it before you build it. (If /propose hasn't been pointed at a real destination yet — a vault, a folder, a doc — for this project, write the proposal directly into your reply and say plainly that it isn't filed anywhere durable yet, rather than dropping it silently.)
otherwise, make sure you invoke /update-the-founder to remember how to communicate clearly what you did, so the person doesn't need to read 10 pages of output to (1) remember exactly what you were working on, (2) identify which part you just worked on, and (3) understand what your work product is. (The skill is named after this habit of writing status updates this way — it generalizes to whoever you're actually reporting to.)
if you have a question for them, run /ask.
and if the person has complained at all this turn about your communication style or being confused, run /calibrate to re-align yourself to their expectations.