Back to Documentation
Architect Chat & Briefs
Understanding Specs
Learn how to read product and technical specs generated in Architect Chat, and how to use them in your development workflow.
Spec types
- Product Spec — problem framing, user stories, success criteria, and product requirements.
- Technical Spec — architecture, APIs, data flow, and implementation guidance grounded in your repos.
- Mockup / Diagram — visual companions that clarify UX or system shape.
How to read them
Open a brief in Architect to browse artifacts. Look for concrete file paths, existing modules, and integration points — those citations are how QEEK stays honest to your codebase instead of inventing a greenfield design.
- Skim the product overview and success criteria with stakeholders first.
- Use the tech spec’s architecture and API sections as an implementation checklist.
- Treat citations as starting points — verify critical paths in the repo before coding.
Using specs in your workflow
- Refine in Architect, then share the brief link with your team.
- Export to Jira or Linear when you need a tracker issue with specs attached.
- Keep iterating in Chat if requirements change — re-export to update the linked issue.