Cursor can now code across Slack channels and repos. The hard part is agent coordination

On July 17, Cursor added plan-first Slack replies, named multi-repository environments, and the ability for its agent to read and post across channels. Once a coding agent can start from Slack, coordination becomes the risk surface: repository selection, context, verification, and inspectable evidence.

A safe Slack-to-code workflow needs six controls: planning, task independence, fresh context, verification, root-cause debugging, and review.

Cursor's primary changelog describes three useful changes:

1. The agent can propose a plan in Slack before execution.
2. Teams can name environments that contain multiple repositories.
3. Agents can read from and post to multiple channels during a task.

Those are coordination primitives. They do not decide how your agent should plan, split work, verify claims, or request review. That policy belongs in the skills and instructions you attach to the workflow.

I checked the live Skillselion catalog on July 18, 2026. These six operational skills from the same open-source collection follow workflow order, not install rank.

1. Start with writing-plans

writing-plans had 188,754 catalog installs on July 18, 2026.

It turns a high-level specification into an executable plan with file mappings, small tasks, tests, and documentation references. The source is available on GitHub.

This is the best first gate for a Slack-launched agent. Ask it to post the plan before it edits anything. A reviewer can catch a wrong repository, missing migration, or unsafe deployment assumption while the cost of correction is still low.

2. Parallelize only independent work

dispatching-parallel-agents had 138,691 catalog installs on July 18, 2026.

It dispatches independent tasks concurrently with isolated context. Its implementation is on GitHub.

Multi-repo access makes parallel work tempting. Independence is the constraint that matters. Two agents editing the same contract, migration, or shared type are not parallel tasks. They are a merge conflict with a longer explanation.

3. Give every subtask a fresh owner and two review stages

subagent-driven-development had 149,562 catalog installs on July 18, 2026.

It executes a plan with a fresh subagent per independent task and automated specification and quality review. The source is on GitHub.

Fresh context reduces accidental carry-over. The two review stages separate "did we build what the plan asked for?" from "is the implementation good enough?" That distinction is especially useful when Slack compresses a long task into a few status messages.

4. Make completion an evidence claim

verification-before-completion had 148,104 catalog installs on July 18, 2026.

It requires fresh command output before an agent says a task is complete. The source is on GitHub.

A green Slack reply is not a test result. A useful completion message names the commands run, their exit status, the affected repository and commit, and any test or deployment that was intentionally skipped.

5. Escalate failed verification into debugging

systematic-debugging had 191,037 catalog installs on July 18, 2026.

It forces root-cause discovery before code changes through a four-phase debugging process. The source is on GitHub.

This keeps a failed check from turning into a sequence of speculative edits across repositories. In a cross-channel workflow, post the failure evidence where the task started, then keep the detailed diagnosis in one thread.

6. Request review with a fixed contract

requesting-code-review had 171,122 catalog installs on July 18, 2026.

It dispatches a consistent reviewer that checks plan deviations and implementation quality. The source is on GitHub.

The reviewer should receive the plan, exact diff range, test evidence, and known limitations. "Please review" is not enough context for a human or an agent.

A practical Slack-to-code contract

Before you let a channel mention start a multi-repo coding task, define this contract:

• Identity: Which user, bot, and repository permissions authorized the work?
• Scope: Which repositories and directories may change?
• Plan: Where is the proposed plan, and who can approve it?
• Concurrency: Which tasks are truly independent?
• Evidence: Which tests, builds, and deploy checks prove completion?
• Provenance: Which commits, pull requests, and environments changed?
• Rollback: How will the team stop or revert the task?

Cursor's Slack improvements lower the cost of invoking an agent. The operational advantage comes from pairing easy invocation with hard boundaries and inspectable evidence.

The chat thread is becoming a control plane for code changes. It needs policy, state, verification, and audit trails.

Compare the six skill pages and review their source before installing anything.

Skillselion is an independent directory, not affiliated with Anthropic, OpenAI, or Cursor. The live catalog is refreshed daily from skills.sh, GitHub and MCP registries, ranked by real installs.