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-sentence brief to a draft your team can review.

Before you start

Bring:

• One customer problem, product question, or feature idea
• A sentence describing who is affected and what is difficult today
• At least one connected source if you want Specky to ground the draft in existing evidence

You do not need a finished solution. A rough brief is useful; Specky can help you find the supporting signals and expose the questions that are still open.

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

1. From the sidebar, open PRD Editor.
2. Click New Document.
3. Enter a feature name or paste your brief.
4. Click Generate with AI.

Specky searches relevant signals from your connected integrations, drafts the document, and adds citations to the evidence it used. Depending on your workspace, those citations may point to Slack threads, Jira tickets, customer calls, research responses, or other connected sources.

What you should see

The first draft should give you a reviewable starting point, including:

• A clear problem statement and the people affected
• Goals or success measures
• Requirements and suggested scope
• Open questions and assumptions worth checking
• Links back to the signals behind important claims

The draft is not a final decision. Treat it like a well-researched first pass: keep what is useful, correct what is wrong, and remove anything the evidence does not support.

Make the draft yours

• Use the block editor to add, remove, or reorder sections.
• Click an AI-generated sentence to inspect its source evidence.
• Use the AI chat sidebar to ask for a shorter summary, a missing edge case, or a comparison with another signal.
• Rewrite the decision, scope, and success metric in language your team will actually use.

A complete example

You are improving team invites. You paste the brief above and ask Specky to focus on new workspace admins from the last 60 days. The expected result is a PRD that explains where invite setup breaks down, shows the customer evidence behind that pattern, proposes a measurable improvement, and calls out what still needs validation.

Before sharing it, check three things:

1. Does the problem describe a real user struggle rather than a preferred solution?
2. Can the team tell how success will be measured?
3. 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, export it as Markdown or PDF, or push it directly to Notion or Confluence. If the PRD is approved, use the document actions to generate delivery tickets and keep the evidence attached as the work moves into execution.