Back to Documentation
Architect Chat & Briefs
Best Practices for Briefs
Get sharper briefs from Architect Chat — clearer prompts, better specs, and a clean handoff to engineering and your issue tracker.
When to use a brief
- You need a codebase-aware answer before scheduling eng time.
- You’re shaping a feature and want product + tech alignment in one place.
- You want a durable artifact (brief) you can export to Jira or Linear later.
Prefer a quick Chat exploration first if you’re only asking a question. Promote to a brief when you generate specs or mockups worth keeping.
Prompting tips
- Lead with the user outcome, then constraints.
- Name the repos or surfaces involved when you know them.
- Ask for risks, open questions, and dependencies explicitly.
- Iterate: one focused follow-up often beats a huge first prompt.
Handoff to the team
- Review specs in Architect before exporting — fix gaps in Chat first.
- Export once stakeholders agree; use re-export to sync description and attachments.
- Keep the QEEK brief as the source of truth for narrative; let Jira/Linear own status and assignment.