Spec workspace

Product thinking, grounded in your code and shared with your team

The workspace where humans and agents converge on what needs to be built. Product, design, and engineering refine requirements together, and the requirements document becomes the single source of truth.

Request an invite
A change request definition open in the Kairo spec editor, with AI-suggested edits tracked in the text and a comment thread where the Kairo assistant replies.
The four columns of Kairo's change request board, Defining, Ready, Building, and Done, with each card tagged as a feature, an improvement, or a fix.
Change requests

One flow for every change request

Everything you ship starts as a change request: a feature, an improvement, a technical fix, or a bug. Each one moves across one board, from defining to ready, building, and done, so status is visible without a standup.

  • A Kanban board with drag and drop across stages and filters on any dimension
  • Definition, plan, files, comments, and activity attached to each change
  • Assign tasks to teammates when a human needs to pick something up
Kairo's AI asking a multiple-choice question about a requirement, then recommending an answer with its reasoning when asked for best practices.
Sharpened with AI skills

From intent to requirements document, with a skill

Kairo questions the intent like a demanding reviewer: flagging ambiguity, surfacing constraints, and asking what an engineer would otherwise ask three days into implementation.

  • Ambiguities and open questions settled in dialogue, before anything is written
  • A requirements document generated from your team's own template
  • That document is the single source of truth, for your team and your agents
A contributor's view in Kairo: their suggestions, each with a type (feature, improvement, or fix), a priority, and a status, submitted or accepted, with accepted ones tracked in an existing change request.
Your users, in the loop

Feedback that arrives as a change request

Customers and stakeholders can join as Contributors. They submit features, improvements, and fixes, and follow their own suggestions, without access to the rest of your internal workspace.

  • Your team accepts or declines each suggestion
  • Overlapping requests merged into the existing change request
  • A simple status for contributors: submitted, accepted, done, or not accepted
Your practices, encoded

Skills, assistants, and chats that work your way

Kairo's AI isn't a fixed assistant. It's a set of capabilities your team shapes to match how you actually build.

Built-in templates

Pre-defined skills for recurring work: defining a change request, planning it, reviewing an implementation against its acceptance criteria, or documenting the product from code.

Custom skills & AI assistants

Create your own skills and AI assistants on the platform, tuned to your product, your standards, and your review culture, and share them across the team.

Collaborative chats

Chat with Kairo's AI or your own assistants in shared conversations. The whole team sees the same answers, so alignment happens in the open instead of in private prompts.

Built for real collaboration

Documents that feel like Google Docs, built for specs

Suggested edits, comment threads, and version history: the collaboration your team already knows from a modern document editor, in the place where specs live.

Rich content, exportable

Tables, images, code blocks, and Mermaid diagrams. Export any document to Markdown, Word, or PDF.

Real-time co-editing

Product, design, and engineering edit the same document at the same time.

Comment threads with AI

@mention a teammate or an AI assistant and get an answer in the thread.

Suggested edits

Humans and AI propose changes as suggestions you accept or reject. Nothing is silently overwritten.

Version history

Versions and snapshots keep a record of how each document evolved, so you can always go back.

Figma import

Bring design context into the document so the team and the AI work from the same screens.

Give your team one place to decide what gets built

Join the pilot and put your next feature through the Kairo workflow.

Request an invite