Linear in Practice — Anish Bharadwaj

1

The Evangelism

I've been inspired by a lot of what Linear has put out about product and design over the last five years. I've shared my love for Linear and what I've learned from them with a lot of people along the way. Here's some proof — Steven actually posted about it.

linkedin.com/in/shows

Steven Shows LinkedIn post about Linear MVP blog, thanking Anish Bharadwaj

View LinkedIn post →

2

The Solo Build

When I took on my first solo build project, I had to use Linear as my AI-operated project management system — over 400 tickets. I got to test out multiple agents working within Linear, including Cyrus. I felt like the future of how products get built — from idea to shipping to learning in the real world — is all going to be trackable on Linear. Just humans and agents working on the same surface.

linear.app/experteaze

EXP-375

In Progress

Agent

Infra

P1

LanceDB Knowledge Migration

Cycle 8 · Jarvis Founder OS

C

Cyrus

AI Coding Agent

Problem: Current knowledge system uses flat markdown files. Cross-agent search requires loading full context into every session, wasting tokens.

Approach: Migrate 1,200+ documents to LanceDB vector store. Implement semantic search with hybrid BM25 + embedding retrieval. Each agent gets scoped access to relevant knowledge slices.

Acceptance: Sub-200ms retrieval, <5% relevance regression vs. full-context baseline, zero data loss during migration.

Blocked By

EXP-371 · Embedding Pipeline Setup

Blocks

EXP-382 · Agent Memory v2 Rollout

EXP-390 · Cross-Agent Knowledge Sharing

Activity

C

Cyrus pushed branch feat/lancedb-migration · 14 files changed
2 hours ago

C

Cyrus moved status to In Progress
5 hours ago

AB

Anish updated description with acceptance criteria
Yesterday

3

The AI Project Manager

At KiwiQ, I built an AI project manager that would sit on top of our Linear tickets and provide updates to the entire team every two days, with deep context about the product and our goals. Honestly, it did a much better job than a lot of PMs and TPMs I've worked with.

kiwiq-ops-hub.pages.dev

ContentQ v2 — Sprint Tracker

Today: Mon Dec 16

Demo: Fri Dec 27

Days to Demo

10

Active Blockers

3

Overall

68%

Risks

CRIT / HIGH / MED

Frontend

Infra

Workflows

Integration

WorkstreamStatus% M16T17W18T19F20 M23T24W25T26F27 M30T31

Frontend Wave 1 AshishENG-480..485

F1.1 Chat UI Core

DONE

100

F1.1

F1.2 Streaming

DONE

100

F1.2

F1.3 Agent Hub

IP

75

F1.3

F1.4 Module Registry

DONE

100

F1.4

F1.5 Preview Panel

IP

60

F1.5

Frontend Wave 2 AshishENG-490..494

F2.1 Workflow Canvas

TODO

0

F2.1

F2.2 HITL Templates

TODO

0

F2.2

F2.3 Dashboard

TODO

0

F2.3

F2.4 Polish & A11y

TODO

0

F2.4

Infra RaunakENG-486..488

I1.1 API Schema

REV

80

I1.1

I1.2 Deploy Pipeline

IP

50

I1.2

I1.3 Monitoring

TODO

0

I1.3

Workflows GauravENG-500..502

W1.1 Oscar Specs

REV

70

W1.1

W1.2 12 Content Flows

TODO

0

W1.2

Integration AllENG-510..512

X1.1 E2E Wiring

TODO

0

X1.1

X1.2 Demo Prep

TODO

0

X1.2

Status Update · Dec 17, 2025

Frontend on track — Chat UI streaming complete, agent hub pages done, Module Registry shipped. Backend risk: API schema alignment (ENG-486) at 80% — blocks all frontend integration. Raunak targeting Wed deploy. Workflow specs in review — need finalization before 12 Content Studio workflows can begin. Critical path: API deploy Wed → integration sprint Thu-Mon → testing Tue → demo Fri. Team bandwidth yellow flag: Ashish carrying 12 items solo.

View live tracker →

Not just a user — a builder on top of Linear.