Omni Zero-to-One — Linear Project Spec (Off-the-Shelf)
Purpose: Exact project name pattern, epic names, and issue titles for creating the Omni Linear project for a new client. Use when an agent or human needs to create [Client] Omni Zero-to-One (or the three-project variant) in Linear.
Source of truth: omni-zero-to-one-implementation.md.
When to use
- New Omni zero-to-one engagement kicked off; client name is known.
- Create the standard Linear project and issues so the team tracks work from the same checklist every time.
Option A — Single project (recommended)
Project name: [Client] Omni Zero-to-One
Example: LMNT Omni Zero-to-One, Eden Tableau to Omni Migration
Initiative: Data
Labels: omni, data; add phase-0, phase-1, phase-2 on issues as needed.
Epic: Omni Foundation
- Connect Omni to warehouse
- Lock pilot domain and sources
- Set up Omni CLI sync and working branch
- [OPTIONAL] Download/organize Tableau workbooks for Cursor
Epic: Omni PoC
- Create initial Topics
- Build first 1–2 dashboards (Cursor + Blobby)
- Enable Blobby and document for users
- Validate with business owner
Epic: Omni Accelerator
- Expand domains / add Topics
- Permissions and training
- Handoff and merge to main
Option B — Three projects
Projects: [Client] Omni Foundation, [Client] Omni PoC, [Client] Omni Accelerator
Use the same issue titles as in Option A, grouped under the corresponding project.
Ticket creation
- Use linear-ticket-generation-from-transcript.md for description format when creating issues.
- For Omni zero-to-one, pull acceptance criteria and context from omni-zero-to-one-implementation.md.