Shared product context for teams and their agents
Decide the product. Let agents build it.
ProductPlot turns your meetings, threads and documents into decisions, architecture and a backlog that knows what blocks what. One space for every product in your initiative: your team reads it, and Claude builds from it.
Dana · customerOur admins give up before they invite anyone.
Sam · productThen inviting has to happen inside setup, not after it.
Lee · engineeringThe setup step needs the invite API first.
Teammates are invited during setup, not after it.
From the customer call at 14:32Confirmed by Sam- Ready to build: Bulk invite endpointrepository api
- Waiting: Invite step in setupafter apirepository web
- Ready to build: Reminders for pending invitesrepository worker
- Blocked: Who can invite admins?decisionrepository web
2 ready · 1 waiting · 1 blocked by a decision
How it works
Every product answers the same four questions.
A space holds your initiative and every product in it, each with its repositories. You don’t have to design a knowledge base: each product gets the same structure on day one, and Claude keeps it current as the work changes.
Onboarding initiativeProductsSetup flowAdmin consoleMobile app
- What
Backlog
Epics broken into stories, kept in your GitHub Issues. ProductPlot reads them and adds what GitHub cannot hold.
- When
Pipeline
Every story moves from shaping to shipped. You see what holds each one, and blocked work stays out of the build.
- Why
Decisions
Who decided what, when, and the conversation it came from.
- How
Architecture
Every repository and its architecture records. Coding agents read them before they write a line.
Meetings, threads and documents feed every product. Add them yourself or ask Claude to bring them in. The originals stay one click away from everything they shaped.
The pipeline
Nothing blocked gets built.
Dependencies, found for you.
Your issues already say what waits for what, in prose nobody can query. Claude reads your issues, meetings and plans and proposes each dependency with its evidence. A person confirms or dismisses it in one click.
A gate in front of the build.
A story is ready to build only when it is defined, nothing holds it and what it needs has shipped. A detection nobody has checked holds it too. Coding agents only pick up what passes, so they work in parallel without stepping on each other.
Runs on your GitHub Issues.
ProductPlot reads GitHub; it doesn’t replace it. It keeps what GitHub cannot: how stories relate, what is blocked and why, and the gate. When something should change in GitHub, Claude can do it on your team’s behalf.
The blocker that matters, first.
Every decision, question or missing access shows how much work it holds. Clear the one that releases the most and watch the stories move.
Dashed: proposed by an agentSolid: confirmed by a person
An epic in the pipeline Illustrative example
Invite during setup
Now · rank 1#412Wave 1No dependencies · 3 in parallel
- Shipped: Invite tokens
- Ready to build: Bulk invite endpoint
- Ready to build: Reminders for pending invites
Wave 2After wave 1 · 2 in parallel
- Waiting: Invite step in setup
- Blocked: Admin invites
Wave 3After wave 2 · 1 in parallel
- Shaping: Setup completion metric
Dependency to checkFound by Claude
“Invite step in setup” needs “Bulk invite endpoint”
“The setup step needs the invite API first.”
Customer call · Tuesday · 14:41
With Claude
No setup. One button.
Connect Claude once.
After that, every meeting, epic and question has a button that hands the work to Claude with the right context already attached. In Claude Code, the Claude app or Cowork.
Coding agents start with the why.
When an agent picks up a story, it loads the acceptance criteria, the decisions behind it and the architecture records it must respect, from any repository in the product.
People stay in charge.
The web app is your team’s window: find what you need quickly, confirm what agents propose and make the decisions. Anything an agent wrote stays marked until a person confirms it.
Where the work is Illustrative example
Process this meeting with Claude
Claude reads the call, compares it with your decisions and backlog, and sends proposals back for you to confirm.
› build story “Bulk invite endpoint”
✓ gate: ready to build, nothing holds it
✓ 3 acceptance criteria
✓ decision: invite during setup (Sam, Tue)
✓ ADR 0012 invite tokens (api)
› opening a pull request in api…
Start with one product and one meeting.
Free during the alpha. Connect the Claude you already use.