Flare
Get started
Menu
WhyUse casesArloMiroKiroAgentsContextMCPPricingLog in

Use cases · one loop

Between “we talkedabout it” and “thecode reflects it.

Ideas are born in Claude. Code is written in Cursor. The gap is a markdown file that dies the moment the next conversation happens. Flare is a living Project both sides read and write. Scroll — one afternoon, six cuts.

↓ Don’t skim the labels. Watch the scene change.

01 / 06

You scoped it in Claude.

Back and forth. “No waitlist — Enterprise couldn’t.” Then the tab closes. That conversation is about to die as a paste.

01 / 06

You scoped it in Claude.

Back and forth. “No waitlist — Enterprise couldn’t.” Then the tab closes. That conversation is about to die as a paste.

You · ClaudeReferral system for customers. No waitlist. We tried that in March.
ClaudeGreat idea! Here are five ways I can help. Also I just invented a requirement you rejected in March.

02 / 06

MCP opens a Project. Arlo structures it.

Not a dumped essay. Specs, epics, stories, ACs. Two ready. Rewards must wait.

Arlo · via MCPCool. I’ve turned that into a project. Four epics. Two you should not start yet.
Epic 01 · readyProgramWho can invite. Start here.
Epic 02 · readyTrackingUnique links. Attribution.
Epic 03 · blocked on 01RewardsDepends on Program. Don’t start here.

03 / 06

Cursor builds against what’s true now.

What’s blocked? Why did we drop waitlists? Done means merged — not a tidy board.

Cursor · via MCPWhat’s blocked on Rewards? Why did we drop waitlists?
INV-12 Invite flowmerged
ONB-4 Empty statePR open — so: no
ONB-9 Rewardsblocked on Program
Waitlistsout since March

04 / 06

Tuesday would have killed the file.

Miro writes into the same Project. Priya’s decision. Sam’s maybe. The Safari bug.

Priya

Let’s ship referrals without waiting on billing.

Decision
Sam

We’re considering a waitlist — not committing.

Not a decision
Dev

Safari still drops focus on checkout.

Bug · staged

05 / 06

It shipped. Kiro is the front desk.

FAQ answered. Dead button becomes a ticket on ONB. No CS hire.

acme.app / settings / team

Shipped · no CS hire

Invite teammates

The button is dead. Kiro is on this screen.

Invite
Kiro
The Invite button doesn’t do anything.
KiroDead after click. I grabbed the screen. Opening this on ONB — same Project Cursor has open.

06 / 06

Months later: why did we build it this way?

March, Tuesday, Acme — still attached. The loop does not reset.

Decision

Waitlists are out. Enterprise couldn’t support it.

Priya

Ship without billing. Sam was only considering.

Acme

Third time this quarter. Related to Atlas auth — not a new island.

Same loop. Different front door.

What changes is the first conversation. Not the Project.

Conversation → structured work → agents execute → context stays. Always.

  1. Builder
    Starts in chat.Claude, then MCP, then Arlo. Cursor builds against the Project. The film above is this door.
  2. IT services
    Starts on the discovery call.Miro on requirements. Arlo turns the transcript into specs, epics, stories, ACs. Engineers pull work through MCP. Standups write back into the same Project.
  3. Product / SaaS
    Starts in the sprint — and stays in the product.Miro on planning and QBRs. Kiro inside the app. Bugs and asks land on the same backlog the sprint already uses.
  4. Storefront
    Starts when checkout fails — or the agency call.A vague brief becomes scoped work with ACs. Recurring ticket patterns become signal, not an inbox. (Kiro answers FAQs from connected data. It does not invent order lookup.)

The differentiator

Why a file cannot do this →