Brief the Implementer

Transform the conclusion of a discussion into a tight, paste-ready briefing that someone picking up the work — a fresh AI session, a teammate catching up, a future-you — can read once and act on, without sitting through the discussion that got there.

When to use

The user explicitly asks for the outcome of the current discussion to be packaged as a paste-ready briefing for a separate context — another AI session, a follow-up task, a teammate catching up. The trigger is the user's request, not a judgment about whether the conversation has reached a "good enough" conclusion: if they're asking for the briefing, draft it from whatever the discussion has produced. The recipient already knows their own work; what they're missing is the conclusion of this discussion and the reasoning behind it. They are not stepping into the user's shoes — they're receiving a reply they can act on.

Recipient knowledge profile, in one line: full project context, zero session context. They have the codebase, the repo docs, the conventions, the tooling. They do not have the chat that produced this brief.

Tone

Structured, briefing-style — not casual prose. The recipient is parsing the artifact to extend their working context, not reading a chat ping.
Verdict-first. The bottom line goes at the top; a skim of the first two sections should reveal the answer.
Direct, no preamble or sign-off. No "hope this helps."
Confident about what was concluded; honest about what wasn't (caveats, open questions).