# A good discussion. A plan you can use.

Source: https://corespeed.io/integrations/slack-linear

Turn a Slack discussion into a plan grounded in Linear, in one request. Through CoreSpeed, your agent reads the thread and the issues your team already tracks, then drafts next steps that reuse existing work and flag the decisions nobody owns yet. It proposes a plan in your agent and creates or changes no issue.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Slack and Linear after setup. Each account needs its own authorization. Create an account: https://app.corespeed.io/sign-up

## Keep the decisions. Make the next step clear

Compare what the team discussed with the work already recorded. Draft a plan that respects the context and flags what is not decided.

You ask your agent: "Read the launch discussion in Slack and the related Linear issues. Draft a plan that accounts for existing work and flags unassigned decisions. Do not create or change issues."

It calls CoreSpeed:

- `slack__conversations_history`: ok, 447 ms
- `linear__list_issues`: ok, 433 ms

It reads from: Slack, Linear.

### Working plan: From discussion to direction.

Keep the landing-page draft moving and schedule the messaging review. Agree on the first test’s success measure before launch.

**Proposed next steps**

- Use the existing landing-page issue instead of duplicating the work.
- Complete a messaging review around the customer use case.

**Decision needed**

- Choose a success measure for the first test.
- Confirm owners rather than assuming them.

_Illustrative result from fictional sources · Nothing sent or changed_

Slack on its own: https://corespeed.io/integrations/slack

## Give the conversation a grounded next step

Requests you can make once Slack and Linear are connected. The data is fictional.

### Team discussion

Slack · launch thread · Slack

- Agreed: Lead with the customer use case
- Still open: How the first test is measured
- Illustrative source · Fictional data

### Existing work

Linear · launch issues · Linear

- In progress: Landing-page draft
- Not started: Messaging review
- Illustrative source · Fictional data

### One result to review

Working plan · Draft in your agent

- Proposed next steps: Use the existing landing-page issue instead of duplicating the work.
- Decision needed: Choose a success measure for the first test.
- Nothing sent or changed

## Keep your agent. Bring the context

One CoreSpeed account, across compatible agents.

1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in.
2. **Connect Slack and Linear**: Authorize each account and the content this task needs.
3. **Ask for a working plan**: Name the project or conversation, then review the result.

Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Will this create tasks automatically?

No. The result is a proposed plan in your agent, not committed work. Creating issues or editing pages is a separate tool call.

### Do I need both connections?

Yes. This example combines Slack and Linear. Connect both, or start from one app: an agent cannot use data it cannot access.

### Does this send or change anything on its own?

No. These examples read context and draft a result. Sending or changing a record is a separate tool call, which approvals can hold for a person. How approvals work: https://corespeed.io/docs/approvals

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

Every tool and price: https://corespeed.io/catalog/slack

Every tool and price: https://corespeed.io/catalog/linear

## Related pages

- [Linear for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/linear): Bring Linear issues and project context into your agent. See what is moving and what needs attention.
- [Discussion to plan with Slack and Notion](https://corespeed.io/integrations/slack-notion): Turn a Slack discussion into a proposed plan, grounded in the goals and constraints recorded in Notion.
- [Slack for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/slack): Bring the Slack conversation into your agent. Find the decisions, the open questions, and what happens next.

## Sources

- Connectors: https://corespeed.io/docs/connectors

Reviewed 2026-11-07.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)