Introducing Slate

Project context for agentic teams

Keep the purpose, decisions, and open questions readable for people and agents, in one context bundle.

Browse a context bundle

01 / 04

.slate / Product Launch / Ticket #42

brief.md

Launch brief

Onboarding Flow

Ship the new signup path without losing the purpose, decisions, or open questions.

Purpose

  • Reduce time-to-first-workspace for invited members.

Decisions

  • Magic link first; password as fallback.

Open questions

  • What is the mobile empty-state line?

Linked sources

MeetingThreadNotesBoard
Readable by people and scoped agents
  • Decisions, tasks, chats, and notes stay together
  • Meet, Chat, Board, Notepad, and Whiteboard feed one context bundle
  • `.slate` keeps readable context on disk

Requirements stay close to the work that changed them.

Slate turns each workspace into context bundles of purpose, decisions, owners, status, open questions, and related work.

01

Launch brief

Purpose, owner, current status, and related surfaces in one context bundle.

02

Decision log

Meet notes, Chat replies, and Board changes keep the reason with the outcome.

03

Build handoff

Open questions and related work stay visible before code starts.

Start with a workspace. Hand off the context bundle when build work begins.

Feed, Meet, Chat, Board, Calendar, Time, Whiteboard, Notepad, Integrations, and Agents keep the same context boundary.