✕
Chat.
We'll never replace Slack or Teams. Comments live on the canvas; conversation lives in your chat tool. We do real two-way sync of @-mentions and comment threads, and stop there.
Live · 3 on this pageSaraDanielMira
Product · four canvas types
Four artifacts. One file.
The full breakdown of what lives in a Cohere file — and why putting them all in one document is the single change that makes teams ship faster.
Section 01 · specSara
01
Spec
The doc that holds direction.
Long-form prose with embedded designs, comments, and acceptance criteria. Native rich text + slash-menu blocks. Comments resolve into change-history. Decisions are captured inline; nothing only lives in Slack.
- 01Block editor — text, headings, embeds, inline frames
- 02Slash-menu for fast block insert
- 03Inline @-mentions tied to your team
- 04Comment threads resolve to changelog entries
- 05Version history with named saves
Example · spec block
Goal: Reduce time to first sticky-note from 90s to 30s.
Acceptance: 80% of new users place a node in 30s, p50.
Owner: @sara · @daniel
Acceptance: 80% of new users place a node in 30s, p50.
Owner: @sara · @daniel
Section 02 · designDaniel
02
Design
The frames the team is building.
Native vector design surface with components, variables, prototyping links, and dev-mode handoff. Same file as the spec — context never falls between tools.
- 01Vector frames, components, variables
- 02Auto-layout + responsive constraints
- 03Prototyping with smart-animate transitions
- 04Dev-mode with code generation (TS / Swift / Kotlin)
- 05Plugins via the open Cohere Plugin API
Example · design block
✦ Frame · OnboardingHero · 1440 × 720
↳ Auto-layout, vertical, gap 24
↳ Logo lockup
↳ Headline (h1, $hero-display)
↳ CTA primary
↳ Auto-layout, vertical, gap 24
↳ Logo lockup
↳ Headline (h1, $hero-display)
↳ CTA primary
Section 03 · ticketsMira
03
Tickets
The work, broken down.
Tickets nest inside the spec. Drag a frame in to attach the design. Tickets sync into your engineering board (Linear, Jira, GitHub) with full context attached and stay in sync both ways.
- 01Tickets nested under specs and designs
- 02Two-way sync with Linear, Jira, GitHub Projects
- 03Drag a frame onto a ticket to attach it
- 04Status, owner, due date, estimate fields
- 05Bulk-create from spec checklists
Example · tickets block
ENG-1024 · 3d est.
Build starter-file cold-start path.
↳ Frame attached: OnboardingHero v3
↳ Owner: @mira · Status: in progress
Build starter-file cold-start path.
↳ Frame attached: OnboardingHero v3
↳ Owner: @mira · Status: in progress
Section 04 · retroJamal
04
Retro
What we'd do differently.
After ship: the retro lives in the same file as the spec it shipped. Reading the next quarter's spec means reading what the last quarter learned — automatically.
- 01Retro template attached to every spec on ship date
- 02Anonymous and attributed retro modes
- 03Action items roll forward into the next spec
- 04Search retros by tag, contributor, or quarter
- 05Export as Markdown or PDF for QBR decks
Example · retro block
✓ Shipped Wed Apr 22, 6 days early.
What worked: daily 15-min canvas sync.
What didn't: spec rev 2 → rev 3 took 4 days unnecessarily.
Forward action: set v-cap on revs in next spec.
What worked: daily 15-min canvas sync.
What didn't: spec rev 2 → rev 3 took 4 days unnecessarily.
Forward action: set v-cap on revs in next spec.
Section 06 · annex · what cohere is notDaniel
Three things on every other collab tool. Not on Cohere.
✕
An issue tracker (alone).
Tickets nest inside the spec; we sync them into Linear / Jira / GitHub Projects. We don't try to replace those tools. The engineering board you have is the engineering board you keep.
✕
A wiki.
Cohere is for the work, not the institutional knowledge. Use Notion, Confluence, or your wiki for the everlasting docs. Cohere is the file that holds one feature, end-to-end.
