Get one useful thing working before you configure everything.
Start with one real product question. Specky helps you turn it into something you can review.
Try saying
“Here is what we are hearing from customers. What is the clearest problem to solve first?”
Bring one thing
A product URL, note, or customer quote.
Ask clearly
Say what you are trying to decide.
Review together
Check the evidence before you act.
Generating Your First PRD
A PRD is easier to write when you start with a real problem, not a blank page. This guide takes you from a one-line idea to a draft your team can review.
Before you start
Bring:
- One customer problem, product question, or feature idea
- A sentence on who is affected and what is hard for them today
- Some evidence in your workspace, such as connected tools, interviews, or customer feedback, if you want the draft to cite it
You do not need a finished solution. If Specky finds no evidence, the draft marks those sections "⚠️ Needs Evidence" instead of making support up. Each generation counts toward your plan's monthly AI limit.
Give Specky a useful starting point
The best input is specific enough to guide the search but open enough to let the evidence change your mind.
Useful input:
Teams need a faster way to invite everyone from their directory. New admins are dropping out before they finish setup.
Too vague:
Improve invitations.
If you already know the audience, time window, or success metric, include it. If you do not, leave it as an open question rather than inventing an answer.
Create the draft
- Open Documents in the sidebar and click New.
- Choose Generate with AI. The One-Click PRD Generator opens.
- Type your idea, or click one of the suggestions next to Try:.
- Click Generate PRD or press Enter.
Specky first searches your product data, then writes the PRD while you watch. When it finishes, it shows how many evidence records were available.
What you should see
The draft follows a fixed outline:
- Problem Statement
- User Stories
- Requirements (functional and technical)
- Success Metrics
- Timeline & Priority
Claims backed by evidence carry small citation numbers that link to the evidence list at the end. A badge such as "Grounded in 4 customer sources" tells you how many sources were cited.
The draft is not a decision. Treat it as a first pass: keep what is useful, fix what is wrong, and cut anything the evidence does not support.
Check it and save it
- Analyze Gaps runs a Spec Gap Analysis with a completeness score and a suggested fix for each gap. Ask AI to fix this sends a gap to the chat.
- Copy and Export .md take the text with you.
- Save to Documents saves the PRD as a draft and opens it in the editor.
In the editor, rewrite the decision, scope, and success metric in your team's own words. Type @ to cite more evidence.
A complete example
You are improving team invites (a made-up example). You paste the brief above and click Generate PRD. The draft explains where invite setup breaks down, cites the customer quotes behind that pattern, and proposes a measurable improvement. Analyze Gaps flags that the success metric has no target, so you add one before saving.
Before sharing it, check three things:
- Does the problem describe a real user struggle rather than a preferred solution?
- Can the team tell how success will be measured?
- Can every important claim be traced to evidence or clearly marked as an assumption?
Share it or turn it into work
When the draft is ready, use Share to invite teammates or Send to Notion to publish it. Ask a teammate to review it, or click Approve for execution if you work alone. Once it is approved, Send to Execution turns it into tickets. See Specs & documents and Turn plans into tickets.
Ready to apply this?
Start with your own product and keep the first read grounded. You'll create an account before the guided result so it can be saved to your workspace.