Context Sharing

Context Handoff

Goal

Create one concise but complete /tmp/*.md handoff that lets another capable agent continue the overall objective without rediscovering the project.

Build an operating context rather than a generic recap: objective, current state, source files, systems, access requirements, risks, and next actions.

Workflow

1. Identify the overall objective and write it as the first section.
2. Inventory the relevant source systems:
   • local repositories and important paths
   • docs, spreadsheets, and briefs
   • live dashboards or accounts
   • deployed URLs and deployment paths
   • analytics, ad platforms, CRM/forms, and conversion plumbing
   • current artifacts already created
3. Read source files before summarizing when they are available locally.
4. Verify drift-prone status live when cheap and non-mutating. If not verified now, label it as inherited or unverified.
5. Write a single Markdown file under /tmp named like /tmp/<project>-context-YYYY-MM-DD.md.
6. Include exact file paths, URLs, IDs, account names, campaign names, and dates whenever known.
7. Separate confirmed facts from assumptions, guesses, stale context, and open questions.
8. Keep raw detail dense but readable. Prefer tables for inventories and short bullets for decisions.

Secret Handling

Never write raw secrets, passwords, API keys, cookies, private keys, recovery phrases, OAuth tokens, or payment details into /tmp.

For credentials and access, document:

• system name
• account or identity used
• whether access appears available
• where the credential is expected to live
• who can provide it
• what permission is needed

Use REDACTED for any sensitive value accidentally encountered. /tmp is an insecure location for credentials.

Required Sections

Use these sections unless the task clearly needs a tighter structure:

1. Objective
2. Current Status
3. Key Entities
4. Repositories And Local Paths
5. Docs, Spreadsheets, And Source Artifacts
6. Live Systems And Accounts
7. Deployment And Runtime
8. Analytics, Attribution, And Conversions
9. Campaigns, Experiments, Or Workstreams
10. Assets, Copy, And Creative
11. Access And Credentials
12. Known Decisions
13. Risks And Constraints
14. Open Questions
15. Next Actions
16. Source Notes

Quality Bar

• Make the file useful to a fresh agent with no prior chat history.
• Include "what matters" and "where to look next"; avoid pasting long source content unless it is the canonical artifact.
• Preserve user preferences that affect execution, such as "do not launch", "read-only", budget caps, or exact scope.
• Include live-state caveats for ads, analytics, deployments, billing, search volume, or account verification because these change quickly.
• If external systems are involved, state whether the handoff is read-only or whether mutations have already happened.
• End with a short "Fast Start" checklist of the next 3 to 7 steps.

Writing Discipline

• Cut every word that fails to do work.
• Apply the "so what?" test: after every sentence, ask "so what?" and make the answer obvious.
• Read awkward passages back and rewrite them.
• Match the tone to the receiving agent: dense, factual, and free of marketing language.

After Writing

Report the exact /tmp path and any major gaps in the handoff. Do not claim live verification unless it was performed in the current turn.