Write specs that reflect how your product works

Overview

Codebase analysis connects Productboard Spark to your GitHub repositories so it can answer plain-language questions about how your product works today. Every PM can look up limits, business rules, feature flags, and permission logic directly, and specs reflect what's in the code. A workspace admin sets it up once; after that it works for everyone. Available on all plans, in every workspace with Spark enabled.

Understand any part of the product

Ask Spark questions like "What are the file upload limits?" or "Which feature flags control the new onboarding flow?" and get answers sourced from your connected repositories. Spark draws on the codebase automatically whenever it's relevant — you don't need to tell it to check the code.

Write specs grounded in the implementation

While you write a spec, Spark surfaces the existing constraints, APIs, and edge cases that affect it, before engineering has to flag them. You can also ask for a feasibility assessment to check that a proposal is buildable before committing engineering resources.

Onboard to new product areas

Explore an unfamiliar domain by asking Spark how it works — billing, permissions, a legacy subsystem — and get an overview drawn from the code. New PMs get up to speed without scheduling engineering walkthroughs.

Look up implementation facts

Check feature flag status, analytics instrumentation, permission logic, rate limits, and tier-specific configuration straight from the source. Answers cite the current state of the code, so they hold up in customer calls and engineering discussions.

Setup

A workspace admin connects GitHub once; codebase analysis is then available to everyone in the workspace. The admin needs a GitHub account with access to the organization being connected, and a GitHub organization admin completes or approves the installation.

1. From the GitHub integration settings in Productboard, connect your GitHub organization and approve the installation in GitHub.
2. Choose which repositories to index. Initial indexing can take up to an hour.
3. Manage repositories any time — toggle indexing per repository, trigger a manual reindex, or synchronize newly added repositories. Everything re-indexes automatically every night.

Access is read-only: Spark reads and analyzes code but cannot create branches, open pull requests, or commit changes. GitHub is the supported host, and indexing covers TypeScript, JavaScript, Python, Ruby, Kotlin, GraphQL, and YAML.