Back to Documentation
Getting Started

Your First Brief

Turn an idea into a codebase-grounded brief: product and tech specs you refine in Architect, then send to Jira or Linear if you want.

What is a brief?

A brief is an Architect Chat session that produces implementation-ready artifacts: product specs, tech specs, mockups, diagrams. Briefs live in Library → My briefs.

Jira and Linear tickets are an export of the brief, not the main event. Shape the work in Chat first. Send it to your tracker when it's ready.

Start in Chat

  1. 1Open Chat from the header (or Chat with code after indexing).
  2. 2Describe what you want to build, or pick a starter: Explore an auth flow, Explore a dashboard, or Explore an API.
  3. 3Keep going until QEEK generates specs. The input placeholder is “Describe what you want to build...”.

Open Architect when specs appear

Toggle from Chat view to Architect view. Architect stays disabled until you've got at least one spec (“Generate specs in chat to enable”).

In Architect, 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.

Need help?

Can't find what you need? Contact support or browse the blog for deeper walkthroughs.