add-goalUse when the owner gives Terylon's leader a goal in a sentence — \"the leader should take X\", \"add a goal for Y\" — and wants the leader to plan it. Files the goal with goal_add, or a concrete ask as a task under the goal it serves, and reports the leader's answer.
briefingUse when the owner asks what is new in Terylon, what waits on them, or how the leader stands — plans at the gate, verified stories waiting for their merge, open questions, blocked stories, a paused leader. Reads Terylon's briefing, says in a few lines what waits on the owner and offers the one next
hand-overUse when the owner wants a story worked out and handed to Terylon's leader — \"write the spec for this\", \"turn this into a plan and give it to the leader\", \"hand this story over\" — from a rough idea through a specification and a plan to tasks_add.
merge-gateUse when the owner wants to merge a verified Terylon story, asks what proves it, or says \"merge 327\" / \"return it\" — walks the verdict and its evidence, then hands the decision to the one gate, merge, which the owner makes in the console.
review-planUse when a Terylon plan waits at the plan gate and the owner wants it reviewed — \"look at plan 41\", \"what is waiting to be approved\" — before approving all, some or edited stories, or sending it back. Reads the plan, the policy and the memory, flags collisions and under-specified stories, and re
show-storyUse when the owner asks about one Terylon story in flight — \"how is 333 doing\", \"why is it blocked\", \"summarise the story in the session\". Reports its step, cost, attempts, pull request and verdicts, says what it needs, and offers the act that fits without taking it.