Back to Documentation
Architect Chat & Briefs
Creating Briefs in Chat
Use Architect Chat to explore your codebase and shape ideas into briefs — specs and mockups grounded in real file paths and architecture.
The workflow
- 1Make sure your project repos are indexed so Chat has code context.
- 2Open Chat and describe a problem, feature, or rough concept in plain language.
- 3Iterate: ask follow-ups, clarify constraints, and request product or tech specs when ready.
- 4Switch to Architect to review artifacts, then save the session as a brief in Library.
Writing effective prompts
- State the user problem and success criteria, not only the implementation idea.
- Name constraints: repos, frameworks, auth model, deadlines, non-goals.
- Ask Chat to ground answers in your codebase (paths, existing patterns, integration points).
- Request a product spec first when stakeholders need alignment; add a tech spec when engineering is ready to build.
Spec Contract
Chat includes a Contract control (on by default). When enabled, QEEK applies length budgets, required sections, and citation rules so generated specs stay structured and reviewable.
Where briefs live
- My briefs — sessions with at least one spec, mockup, or diagram.
- All chats — every active session, including chat-only.
- In Jira — briefs you have exported to Jira.
- Archive — archived sessions.