Getting Started

Introduction

Welcome to Storydough! Storydough is an AI-powered product management platform that transforms product managers into strategic context architects.

It helps you create living PRDs that preserve the 'what, why, and how' of every product decision. With features like AI-powered document analysis, real-time conflict detection, change tracking, and TARS AI assistant, Storydough eliminates context drift and miscommunication, ensuring your team always builds what everyone meant to build.

Creating a Project

When you first sign up and don't have any existing projects, you'll be automatically redirected to the project creation chat. This AI-powered agent will guide you through the process, helping you gather all the necessary information and ensuring you create a well-structured project from the start.

If you already have existing projects, you can still create new ones anytime by clicking the 'Create Project' button, which will take you to the same guided chat experience.

Adding Context to Your Project

There are different ways to add context to your project. You can connect external integrations like Jira, Notion, Confluence, and more to automatically sync your existing documentation and requirements.

Alternatively, you can manually upload documents directly to your project. Both methods help ensure your PRD has all the context it needs to stay accurate and comprehensive.

Document Context Processing

When you upload a document, Storydough triggers a background process to analyze the file. This AI-powered analysis extracts relevant information, identifies key concepts, and adds it to your project context.

The processing happens automatically in the background, so you can continue working while your documents are being analyzed. Once complete, the extracted context becomes available to enhance your PRD and inform the TARS AI assistant.

Uploading Documents

Integrations

Storydough integrates with popular tools like Jira, Notion, Confluence, and more using OAuth authorization. Simply connect your account through a secure authorization flow to grant Storydough access to your data.

Once you set up an integration, Storydough automatically triggers an initial load process in the background. This process reads all relevant data from the connected service and adds it to your project context, giving your PRD a comprehensive foundation from day one.

External Integrations

Syncing

For most external integrations, Storydough actively listens to events from the connected services. When changes occur in your integrated tools, the context is updated automatically without any manual intervention.

This real-time syncing ensures your project context stays up-to-date as your team works across different platforms, keeping your PRD aligned with the latest information.

Some integrations do not support automatic syncing. For these, you can manually trigger a sync by clicking the sync button available on the integration card after the integration has been set up.

Note: Zoom meeting summaries are generated by Zoom AI Companion and require a paid Zoom plan. On free Basic accounts, Zoom neither sends summary events nor allows reading summaries through its API, so meeting summaries will not sync at all. On paid plans, summaries of previous meetings are imported during the initial load after connecting Zoom, and new summaries arrive automatically as meetings end.

Scope Changes

Scope Changes is one of the core features of Storydough. Every time your project context is updated—whether through an initial load, a document upload, or an event from an external integration—the app analyzes the incoming data against your existing project context.

If discrepancies are detected between the incoming data and the existing context, Storydough identifies that a scope change is needed. A scope change is essentially a list of discrepancies that require your attention.

For each scope change, Storydough provides you with different options or paths to resolve the discrepancy. Each path comes with its own set of actions to help you address the issue. Currently, these actions are read-only—agentic execution to automatically apply changes is still a work in progress.

Scope Changes

Chat Interaction

Storydough includes a context-aware AI agent that allows you to interact naturally with your project PRD. Simply ask questions, request clarifications, or explore your product requirements through a conversational interface.

The chat agent has full awareness of your project context, including all uploaded documents, integrated data, and existing PRD content. This enables you to get instant answers about your product decisions, understand the reasoning behind requirements, and navigate complex documentation effortlessly.

Core Concepts

Projects

Projects are the top-level containers in Storydough. Each project represents a product or initiative and contains its own PRD, context sources, integrations, and scope changes. Projects help you organize your work and maintain separate contexts for different products.

Context

Context is the foundation of your PRD. It includes all the information Storydough uses to understand your product—uploaded documents, data from external integrations, and the knowledge extracted from these sources.

Context is automatically processed and analyzed by AI to identify key concepts, requirements, and relationships that inform your product decisions.

Integrations

Integrations connect Storydough to your existing tools like Jira, Notion, and Confluence via OAuth. They enable automatic data syncing and keep your project context aligned with your team's work across platforms.

Scope Changes

Scope Changes are detected discrepancies between incoming data and your existing project context. They highlight conflicts or updates that need your attention and provide actionable paths to resolve them.

Chat Agent

The Chat Agent (TARS) is a context-aware AI assistant that lets you interact naturally with your PRD. It understands your entire project context and can answer questions, provide insights, and help you navigate your product requirements.

Jira Webhook Setup

Overview

Jira webhooks let Storydough receive issue updates in real time. You create the webhook in your Jira settings and paste the secret into Storydough — no automatic registration is needed.

Note: Only two events are supported: Issue Created and Issue Updated. Other Jira event types will be received and ignored.

Step 1 — After project configuration

Once Jira is connected you need to follow the next steps to finish the webhook configuration

The first modal shows your unique webhook URL and a field to save your signing key. Copy the URL then you will paste it into Jira in the next step.

Storydough Auto-sync modal — webhook URL and signing key field

Step 2 — Create the webhook in Jira

Click Open Jira Webhooks button

Navigate to Jira System settings

You will see the WebHooks list. Click + Create a WebHook in the top-right corner. If you need to edit or delete an existing webhook, the Edit and Delete buttons are shown on each entry in this list.

Jira WebHooks list with Create, Edit and Delete actions

Fill in the Name and URL fields. The name can be anything you like — it is only used to identify the webhook in Jira. Paste the URL from the Storydough Auto-sync modal (open it from the Jira integration card in your project). For the secret, click the Generate secret button — Jira will create one for you. Copy it and keep it somewhere safe, you will paste it into Storydough in the next step. Jira will not show it again once the webhook is saved.

Jira webhook form — Name, URL, and Secret fields

Scroll down to Issue related events and check Issue created and Issue updated. Leave all other event types unchecked — Storydough will ignore them. For the JQL filter leave the field set to All issues; Storydough already filters events by the Jira project you connected, so you do not need a JQL filter here.

Jira webhook events — check Issue created and Issue updated only

Step 3 — Save the signing key in Storydough

Go back to the Set up Webhooks modal in Storydough. Paste the secret you generated in Jira into the signing key field and click Save.

Storydough Set up Webhooks modal — paste the signing key and save clicking Complete setup

Note: A signing key is required — Storydough will reject any webhook event that arrives without a valid secret. Once saved, the last 3 characters of the key are shown as a hint so you can confirm which secret is active. You can update it at any time by clicking Edit.

Deleting the webhook

To stop receiving Jira events, navigate back to Jira Settings → System → WebHooks (follow steps 1 and 2 above). Find the Storydough webhook in the list and click Delete.

Delete an existing webhook from the Jira WebHooks list

You can also disconnect the Jira integration from Storydough directly in the Integrations panel, which will stop all syncing.

Slack Integration

Overview

The Slack integration lets Storydough listen to messages and reactions in your Slack workspace. Once connected, any message or reaction posted in a channel where the Storydough bot is present will automatically update your project context.

Note: Storydough only receives events from channels where the bot has been explicitly invited. Messages in channels the bot has not joined are never delivered to Storydough.

Connecting Slack

Open the Integrations panel in your project and click Connect on the Slack row. You will be redirected to Slack to authorize the Storydough app for your workspace. Once authorized, you will be returned to Storydough and the integration will be active.

To start receiving events, invite the Storydough bot to any channel you want to monitor. In Slack, open the channel and type /invite @Storydough (or use the Members panel to add the bot). From that point on, messages and reactions in that channel will be synced to your project.

Channel Visibility

The bot works in both public and private channels, but only in channels it has been invited to. Adding the bot to a channel gives Storydough visibility into that channel. Removing the bot from a channel stops event delivery for that channel immediately.

Note: Each channel the bot joins automatically appears as an entry in your project's file tree under the Slack folder, with a direct link to open the channel in Slack.

Disconnecting Slack

To disconnect the Slack integration, open the Integrations panel and click Disconnect on the Slack row. This revokes the bot token and removes the bot from all channels in the workspace. Slack will stop delivering events for that workspace immediately — no further messages or reactions will be synced.

Note: Disconnecting does not remove the context already collected in your project. All data previously synced from Slack will remain available.

FAQ

How do I disconnect an integration?

Open the Integrations panel in your project and click Disconnect on the integration you want to remove.

Manage Integrations modal — Disconnect button on a connected integration

Note: Disconnecting an integration does not remove the context already collected in your project. All data previously synced will remain available. However, Storydough will no longer listen to new events from that service.