Reporting back to the person

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.

A hook: a script Claude Code runs on its own at a set moment.

Present finished work with clickable URLs and UX stories. Use when handing off completed work for the human to consume.

Status check-in after every substantive turn — 1-7 sentences that instantly clarify what you're working on, what just happened, what the intent was, what's predicted next, with quick single-letter commands attached. Replaces verbose agent narration with synthesized signal the person can scan in 5 seconds instead of reading paragraphs. Use after finishing any substantive task, when the person says START, when handing off mid-work, when you sense the person needs to observe state for human-in-the-loop review, or when about to ask a clarifying question and want to surface state first. Triggers: status update, what are you working on, where are you, check in, update me, what's the status, surface state, START, observability, human in the loop, what just happened, where do things stand.

Translate agent-speak into plain human language. Use when writing explanations, status updates, proposals, or any communication

ALWAYS ON for every communication a human will read — every chat reply, status update, report, proposal, plan, commit message, comment, or doc, with no exempt category. Holds general, load-bearing directives for how to communicate to any human (conversational synthesis grounded in a real person's intended vs actual experience, no undefined terms, exact conditions when referencing code, broken is scope not "how it works"). Also governs writing in the first person as the specific person you're working with, which additionally requires selecting from their own verbatim material — the skill's name comes from its original build, which preserved one person's own voice; the mechanism generalizes to whoever you're working with.

MANDATORY discipline for any communication that references code — to the person you're working with, in comments, in docs, in proposals, in reports. A code reference is worthless-to-negative unless it is fused with the exact literal conditions (numbers, states, inputs the system actually checks) AND the precise user journey that makes the statement true. Force-read whenever you reference code, and especially on triggers like "what exact ux", "i don't understand", "what are the conditions". Read this BEFORE writing the code reference, not after.

HOW to communicate with the person you're working with. This is not a checker or validator — it is the way you talk. When invoked, immediately apply this pattern to your NEXT response about your actual work. Do not use this to analyze your own communication.

The final 30-second sanity check before going live. Produces a tiny guide the person you're working with walks through to confirm the work actually does what it was supposed to do. Use after ALL agent testing is complete — that person is NOT the tester, they are the final stamp of approval. Also use when they say 'prove it', 'show me', 'is this actually working'.

Generate a trustworthy, human-legible outcome report after completing dispatched work. Each item translates code changes into UX-testable statements with verification evidence grounding. The person you're working with reads this in 30 seconds and knows what happened.

Summarize unfinished assigned work for the person you're working with, in UX-first language. Use when asked what is left, what is in progress, or to communicate incomplete work without technical jargon; translate into user-facing flows and call out what remains with concrete blockers.

Response predictor v2 — queries an oracle built from real agent-conversation history to predict what the person you're working with would say to your output. Replaces a local keyword-matching predictor with semantic retrieval and synthesis over that history. Use before declaring work done, before presenting work, or when you need to anticipate their reaction.

Run the mandatory completion protocol before returning control. Use when finishing any substantive piece of work.

A hook: a script Claude Code runs on its own at a set moment.