Your First Brief
Turn an idea into a codebase-grounded brief — product and tech specs you can refine in Architect and optionally send to Jira or Linear.
What is a brief?
A brief is an Architect Chat session that produces implementation-ready artifacts — typically product specs, tech specs, mockups, or diagrams. Briefs live in Library → My briefs.
Tickets in Jira or Linear are an export of a brief, not the primary artifact. Shape the work in Chat first, then send it to your tracker when you're ready.
Start in Chat
- 1Open Chat from the header (or Chat with code after indexing).
- 2Describe what you want to build, or pick a starter: Explore an auth flow, Explore a dashboard, or Explore an API.
- 3Keep the conversation going until QEEK generates specs. The input placeholder is “Describe what you want to build...”.
Open Architect when specs appear
Use the view toggle to switch from Chat view to Architect view. Architect stays disabled until at least one spec exists (“Generate specs in chat to enable”).
In Architect you can review and refine Product Spec and Technical Spec artifacts side by side with mockups and diagrams.
Find it in Library — export when ready
Sessions with specs show under Library → My briefs. Chat-only sessions stay under All chats.
To create a tracker issue, connect Jira or Linear in Settings → Integrations, then use Send to Jira or Send to Linear from the session. See Send Briefs to Jira & Linear.