Linear
How ShipFoundry exports one generated brief into one Linear issue without broad sync.
Linear is an optional delivery export: one generated ShipFoundry brief can create one Linear issue when a user explicitly asks for it.
When To Use This
Use Linear when a team wants a ShipFoundry brief to become downstream delivery work in an existing Linear project.
Do not connect Linear just to get value from ShipFoundry. MCP and the dashboard work without Linear.
How It Works
ShipFoundry uses a narrow Linear OAuth connection and project export target. A user generates or opens a brief, then explicitly clicks to create a Linear issue.
Exports are never automatic at match time.
Step-By-Step
- Connect Linear from
/dashboard/settings/integrations. - Choose the Linear workspace.
- Configure a project export target.
- Select a team, and optionally choose project, cycle, labels, assignee, and priority.
- Open a relevant update and generate or open a brief.
- Confirm the brief is ready for downstream delivery.
- Click
Create Linear issue. - Review the exported issue URL and stored export state.
What ShipFoundry Does
- Uses OAuth, not personal API keys, for the product path.
- Stores Linear access tokens encrypted server-side.
- Creates issues only from explicit user action.
- Stores export attempts and returned Linear issue identity.
- Uses duplicate-prevention keys so the same brief is not exported repeatedly by accident.
What ShipFoundry Does Not Do
- It does not broadly sync Linear workspaces.
- It does not import Linear issues.
- It does not automatically export every match.
- It does not sync Linear issue status back into ShipFoundry in the current implementation.
- It does not replace ShipFoundry outcome recording.
Export Lanes
| Lane | Use When |
|---|---|
| Research Brief | A human needs to evaluate the product or technical opportunity. |
| Engineering Spike | An agent or engineer should investigate with cited evidence and proof expectations. |
| Workflow Brief | The opportunity changes an operating process and needs a workflow decision. |
| Strategy Brief | The opportunity changes product or commercial direction and needs a decision memo. |
| Hand To Agent | Repo evidence and synthesis are strong enough for direct implementation handoff. |
Updates in the No Packet lane cannot be exported as useful delivery work until the missing evidence or context is resolved.
Troubleshooting
If Linear export fails, confirm the account has an active Linear connection and the project has an enabled Linear target.
If the wrong team or project receives issues, update the project export target before creating another issue.
If an issue already exists, use the stored export state instead of creating a duplicate.
If the team does not use Linear, use MCP task packets and ShipFoundry outcome recording instead.
Related Pages
- Core artifact: Investigation Briefs
- Example artifact: Sample Engineering Spike
- Agent workflow: MCP
- Choosing the right brief: Agent Workflows
- Safety model: Trust And Readiness
- Product CTA: Start 7-Day Trial
Was This Page Useful?
Send a short note if this page is unclear, overclaims a capability, or is missing the proof you expected.
Send Docs Feedback for Linear