Start with one real question and leave with a next step.
Start with the question in front of you, then use the guide to make the next decision easier.
Try saying
“I am trying to make this decision. What should I look at first?”
Start with context
Bring the smallest useful example.
Look for the signal
Separate what is known from what is assumed.
Take one step
Choose an action you can review.
PRD Editor
What it does
The PRD Editor is a block-based document editor purpose-built for product requirements. Unlike a general-purpose editor like Notion or Google Docs, the PRD Editor understands product document structure and can generate, cite, and update content using your connected signals.
Key capabilities:
- AI generation — draft entire sections or individual blocks from a prompt, grounded in your real signals
- Evidence citations — every AI-generated sentence links to the source signal (Slack thread, Jira ticket, Gong call) that supports it
- Real-time collaboration — multiple teammates can edit simultaneously with live cursors
- Version history — every save creates a version you can restore
- Export — push to Jira/Linear, export as Markdown or PDF, or share a public link
When to use it
- Writing new feature requirements — from a rough idea to a structured PRD with acceptance criteria
- Updating existing specs — when new signals change the requirements
- Collaborating with engineering and design — share a live document with comments and suggestions
- Generating tickets — use the Execution Bridge to push requirements directly to your backlog
- Creating decision records — document the "why" behind requirements alongside the "what"
How to use it
- Open PRD Editor from the sidebar
- Click New Document and enter a feature name or paste a brief description
- Click Generate with AI to draft the full PRD structure automatically
- Review each section — click any AI-generated text to see its source citations
- Edit blocks directly using the rich text toolbar, or type "/" for the block menu
- Use slash commands: /generate, /summarize, /acceptance-criteria, /risks
- Click Share to invite collaborators or generate a public read-only link
- When ready, click Push to Jira (or Linear/GitHub) to create tickets from requirements
Example
You're writing a PRD for a new notification system. You type "Notification preferences and delivery settings" as the document title and click Generate with AI.
Specky drafts:
- A goals section citing 3 Slack threads where users complained about notification overload
- A requirements section with 8 acceptance criteria
- A risks section flagging a dependency on the email service provider
You edit the requirements, add a mockup block, and share the link with your engineering lead — all in under 20 minutes.
Ready to apply this?
Start with your own product and keep the first read grounded. You can create an account after you see the result.