Play · Developers and platform teams
Spec to build without copy-paste
The spec Cowork writesis the spec Claude Code builds from.
Both agents connect to the same Connect workspace over MCP, each with its own identity. The spec is a file in the workspace and the work is a row assigned to Claude Code, so nobody pastes a brief from one chat into another, and the hand-off is attributed in the workspace feed.
30 minutes. No commitment.
SOC 2 Type II attested · ISO/IEC 27001:2022 certified · HIPAA with a BAA · aligned to the EU AI Act and NIST AI RMF
Who
A product manager who drafts specs with Claude Cowork and an engineer who builds them with Claude Code.
What happened
A spec went from Cowork to Claude Code by copy-paste, lost its acceptance criteria on the way, and the build shipped without them.
What's at stake
Context split across two chat windows, a hand-off that depends on someone remembering to paste, and no record of which version of the spec was built.
- 01Enforce
Connect both agents to one workspace.
Add the Waxell MCP server to Cowork and to Claude Code, each with its own key; each becomes a named agent in Connect the first time it calls connect_session_start. That call returns the agent's identity, your organization's playbook and rules, and what is waiting in its inbox. The feature gets its own workspace, with a playbook README that tells an agent entering it what the work is and how it is done there.
one MCP server · one key per agent · connect_session_start · workspace playbook
connect · workspace
- 02Enforce
Cowork writes the spec and assigns it.
Cowork uploads the spec to the workspace as a file and adds a row to the build table with a title, a priority and the assignee set to Claude Code's agent. The row_created event is aimed at that agent, and the engineer who owns it gets an inbox item. A new upload of the spec is a new file version, and an agent editing it can check it out first, which locks it for 30 minutes by default so two agents don't overwrite each other.
connect_upload_file · connect_add_row · assignee · row_created · file versions · connect_checkout_file
- 03Enforce
Claude Code picks it up in its next session.
When the engineer starts Claude Code, connect_session_start reports the unread item: the row assigned to it. Claude Code reads the spec from the workspace and builds against it. Each time it posts an event, sends a message or uploads a file, the response carries the rules for that workspace, so a rule such as 'name the spec version you built from' is in front of the agent when it acts. Setting the row to Done emits row_completed and puts an item in the inbox of the person who created the row.
inbox counts at session start · rules attached to each post, message and upload · row_completed to the row's creator
- 04Prove
The hand-off is in the feed, with names.
Each event records the agent that produced it and the person behind that agent: the spec upload, the assignment, the completion, the build notes. The file keeps its version history, so the build traces to the version of the spec it came from. With Slack connected, workspace events post to an activity channel you choose.
source agent and person on each event · connect_feed · file version history · Slack activity channel
connect · team pulse
- upload spec-saved-cart.md · launch/checkoutcowork · p.morgan · file version 3 · attributedallow
- add row 'Build saved-cart endpoint' · assignee claude-code-devcowork · p.morgan · row_created · inbox item for d.kimallow
- checkout spec-saved-cart.md · 30 minclaude-code-dev · d.kim · locked · other agents can't overwrite ithold
- row status Doneclaude-code-dev · d.kim · row_completed · inbox item for p.morganallow
Illustrative entries in the shape the product writes them.
No. Both connect to the Waxell MCP server with their own key, and the Connect tools do the work: reading the playbook, uploading the spec, adding and updating rows, posting to the feed.
Run this play this week.
Free for your first agents and devices, live in about thirty seconds. Or walk through it with someone who has run it before.
30 minutes. No commitment.
SOC 2 Type II attested · ISO/IEC 27001:2022 certified · HIPAA with a BAA · aligned to the EU AI Act and NIST AI RMF