# Arlo

> Arlo turns a discussion into specs, epics, stories, and acceptance criteria — and marks what you must not start yet.

## The chat is not a plan

You scoped it in Claude. MCP opens a Project. Arlo finds the epics hiding in the discussion — and what you must not start yet. Claude Code builds against that, not a dumped essay.

## Four epics were sitting in that sentence

- **Structure, not a paste** — Specs, epics, stories, acceptance criteria — in the order you should do them.
- **Marks what must wait** — Rewards depends on Program. Don't start there unless you enjoy pain.
- **Done means merged** — Status comes from git. A tidy board is not done.
- **Then MCP takes it** — Cursor asks what's next. The next call that changes this is Oren's job — not a new file.

## Example: from a sentence to a project

**Arlo** — Cool. I've turned that into a project. Start with Program. Rewards is blocked.

Resulting epics:
- **Epic 01 · ready — Program** — Who can invite. Who gets paid.
- **Epic 02 · ready — Tracking** — Unique links. Attribution that isn't a vibe.
- **Epic 03 · blocked on 01 — Rewards** — Depends on Program. Don't start here.

Git status Arlo tracks: INV-12 Invite flow (merged) · ONB-4 Empty state (PR open — so: no) · ONB-9 Rewards (blocked on Program).

---
Site map: https://flares.in/sitemap.xml · Machine-readable summary: https://flares.in/llms.txt · How Cursor reads this: https://flares.in/mcp · Phase 2: https://flares.in/miro