Skip to main content

Thread Transfer

Designing Linear hand-offs your PMs will trust

We share the JSON schema, automation rules, and copy deck we use to keep AI summaries and issue queues perfectly in sync.

Jorgo Bardho

Founder, Thread Transfer

March 2, 20256 min read
product opslinearhandoffs
Blueprint-inspired illustration of connected Linear handoff cards

Product managers love context they can act on immediately. This blueprint shows how we turn Thread-Transfer bundles into Linear updates that land with zero follow-up questions and stay archived cleanly for retro review.

Start with the schema

We extend the standard bundle manifest with the fields our PMs need most:

  • Decision summary. One sentence describing the outcome and why it matters.
  • Owner + due date. Pulled from the bundle’s “decisions” block, not typed manually.
  • Dependencies. Links to related issues or documents referenced in the thread.
  • Integrity hash. A quick way to validate the bundle in case the issue gets escalated months later.

Map bundles to Linear issue types

We maintain a simple routing table driven by bundle tags:

Bundle tagLinear teamIssue template
incidentPlatformIncident follow-up
customer-feedbackProductCustomer insight
feature-requestGrowthScoped improvement

The automation applies the right template automatically so the PM sees the bundle context where they expect it.

Compose the issue body

Linear supports Markdown, so we embed the bundle like this:

### Snapshot
    {decision_summary{"}"}

    ### Key facts
    - {"{facts[0].text}"}
    - {"{facts[1].text}"}
    - {"{facts[2].text}"}

    ### Follow-ups
    - {"{follow_ups[0].owner}"} → {"{follow_ups[0].due_date}"}

    ### Provenance
    Bundle hash: {"{integrity.hash}"}
    Source thread: {"{source.url}"}

PMs can scan the top section in seconds, then click into the bundle link if they need deeper detail.

Keep Linear clean with webhooks

We subscribe to the Linear issueUpdated webhook. If an issue closes and the follow-up section still lists open items, we reopen the issue or ping the owner. We also sync back status changes so the bundle record lists who shipped the fix and when.

Report the impact

Every Friday, our automation posts a digest:

  • Number of bundles turned into Linear issues.
  • Median time from bundle creation to issue triage.
  • Any issues re-opened because follow-ups were missed.

Product leadership gets a weekly pulse on how well cross-functional hand-offs are running, and we can iterate on the bundle schema with real feedback.

Want the JSON schema and the automation script? Email info@thread-transfer.com and I'll send you the package.