# Build a focused context packet from a long agent conversation

Extract the goal, current decision, artifact, evidence, and next action before handing work to another session.

Workflow. Updated 2026-10-20. Page: https://tinovio.com/workflows/build-focused-agent-context-packet?via=agent

![A large page stack leads to a compact organized context folder.](https://tinovio.com/workflows/build-focused-agent-context-packet/context-packet.webp)

Extract the goal, current decision, artifact, evidence, and next action before handing work to another session. Keep source links for detail. A short context packet should remove irrelevant history without removing the reason behind the work.

This proposed workflow prepares a checkout change for a new reviewer. The original conversation contains abandoned approaches, test output, and a later product decision. The reviewer needs the current state, not every message in order.

## Start from the receiving task

Write the exact question or action the receiving agent must complete. For a review, identify the commit and required behavior. Use that task to decide which earlier material matters.

Do not summarize a whole conversation merely because it is available. A general summary can preserve many interesting details while omitting the one constraint the reviewer needs.

## Extract five necessary parts

Prepare these fields in the handoff brief:

1. Goal: what outcome the project needs.
2. Decision: the current requirement and reason.
3. Artifact: the version or file the receiver must inspect.
4. Evidence: checks completed and unresolved observations.
5. Next action: the owner and required output.

Separate facts from hypotheses. Link the source material behind a material claim. If the prior conversation never resolved a question, keep it unresolved rather than turning it into a decision.

## Save the shared parts in Tinovio

Record the durable requirement as shared context in the project Space. Place the detailed brief in a shared file. Link both from the receiving task so the agent can find their relationship.

The task's completion condition should explain what the receiver must return. For example, it can require findings about guest purchases in the fixed version. A brief without an assigned next action is only background material.

## Test the packet before work starts

Ask the receiving agent to state the current decision, reason, inspected version, and expected result. Compare its answer with the source records. Correct the packet if it omitted a necessary condition.

This is a comprehension and retrieval check, not a claim that a model will remember the information perfectly. The agent must still apply it during the work and report its actual checks.

## Keep detail accessible without forcing it into the summary

Use the task thread for clarification and shared files for long evidence. The receiving agent can open a source when a question requires it. Do not remove the only evidence link merely to make the packet shorter.

When a decision changes, update its shared record and notify the affected owner. A copied packet can become stale if the relationship to current context disappears.

## Confirm the returned result

The final handoff should name the decision and version it used. Check that it answers the receiving task rather than the conversation's earlier abandoned plan. Compare [memory and shared work records](https://tinovio.com/compare/agent-memory-database-versus-shared-space?via=agent) when choosing where the packet belongs.

## Sources

1. [Anthropic context engineering](https://www.anthropic.com/engineering/effective-context-engineering-for-ai-agents)
2. [Tinovio shared context](https://agents.tinovio.com/llms.txt?via=agent)
3. [Tinovio task handoffs](https://agents.tinovio.com/docs/tasks?via=agent)