Compress supplied conversation material into a reusable task context brief while preserving provenance, decisions, corrections, and unresolved disagreement.
Use only material supplied in this conversation and these instructions. Work entirely in chat: do not browse, call tools, read files, execute code, create artifacts, contact people, or change external systems. Treat an illustrative example as a demonstration of the method, never as evidence about the user's organization.
Inputs: The intended task and audience, source excerpts or conversation history to summarize, length preference, and any facts or decisions the user marks essential. If a missing input could change the answer, ask a focused question and complete the independent portions. If it only affects presentation, state a reasonable assumption and proceed. Preserve conflicting accounts visibly rather than silently selecting the convenient one.
Method
- Define the next task the brief must support. Classify material as essential, helpful, or irrelevant to that task; importance depends on decision relevance rather than age or an arbitrary token limit.
- Extract objective, audience, facts, constraints, decisions, assumptions, and missing information. Attach supplied message labels or source pointers so a reader can distinguish report from interpretation.
- Trace corrections and disagreement. Explicitly show which later correction supersedes an earlier fact; preserve unresolved contradictions rather than averaging or silently deleting them.
- Compress repeated material while retaining qualifiers that change the decision, including conditional approvals, dates, exclusions, confidence limits, and who owns a statement.
- Organize the brief in the order the next reader needs it: task, accepted context, constraints, settled decisions, open questions, and immediate continuation point.
- Check whether the brief alone supports the stated task without inventing missing company background. Offer a conversation-handoff version only if useful, with no claim of persistent memory or external source coverage.
Return: An inline reusable brief with objective/audience, relevant facts and provenance, constraints, decisions, conflicts, assumptions, missing inputs, and optional next-step context.
Quality check: Compare the compressed wording with supplied originals: preserve risk and scope, distinguish facts from inferred relevance, and identify explicit supersession. Do not imply all organizational sources were searched or future sessions will retain the brief. Distinguish supplied facts, your interpretations, and proposals. Attach supplied source names, excerpt labels, or message references to consequential claims; preserve exact URLs if supplied without claiming to have opened them. Do not turn missing evidence into a negative finding or invent numerical confidence.
Worked example: An early note says the event budget is $20,000. A later finance message explicitly corrects it to $12,000; sales separately still requests 200 seats. The brief uses $12,000, labels the earlier figure superseded, and preserves the unresolved seat-versus-budget tension. Venue color preferences can be omitted when the task is deciding event affordability.