Product tour

Connect a repo.
That's the whole setup.

Everything else — the spec, its structure, its upkeep — is inferred from the code and kept current by your normal engineering workflow.

1

Connect a repository

OAuth into GitHub, GitLab, or Bitbucket and pick a repo — or paste any public URL. SourcePRD clones read-only. Private repos stay private; access can be revoked anytime.

2

The crawl drafts your PRD

An agentic crawl reads the codebase the way a staff engineer would: it maps product domains, capabilities, and acceptance criteria — each anchored to the code that implements it, so every claim is checkable.

3

The gate reads every PR

Each pull request is diffed against the PRD. Internal-only changes auto-clear silently. Product-material changes get a plain-language review card — and can be required to pass before merge.

4

Merges grow the spec

When a PR lands, affected capabilities are reshaped and new ones are discovered and added. The PRD reflects what's actually there — nobody maintains it, because the codebase does.

Built for the PM who doesn't live in git

  • Review and approve product changes in the app — no git account
  • Decisions post back to the PR as a status + comment
  • Share by one-time link: viewer, editor, or admin roles
  • On-demand reports: what changed this week, on this branch
  • Alerts when the connection to your repo needs attention
PR #47 — checkout: gift card support needs review
PR #46 — refactor: extract http client auto-cleared
PR #45 — pricing page A/B test needs review
PR #44 — bump dependencies auto-cleared

See your product's real PRD

Questions, early access, feedback — we read everything.