Sabaki Guide

Agent Source Workflow In Sabaki

How to ask Agent grounded workspace questions, inspect sources, and turn source-backed answers into next actions.

An Agent source workflow is the process of asking Sabaki Agent a bounded question, checking the sources behind the answer, and turning the result into a tracked workspace action only after review. It keeps AI-assisted work tied to evidence instead of generic advice.

Key Takeaways

How To Use Agent With Sources

  1. Ask a specific questionUse a concrete prompt such as asking what PostHog-backed KPI values changed this month or which Data Room files answer an investor question.
  2. Check source coverageConfirm the answer references the expected workspace sources and flags missing context when evidence is unavailable.
  3. Open the evidenceReview the cited document, KPI row, room comment, or workspace record before acting on the answer.
  4. Refine the requestAsk Agent to narrow the answer, compare sources, or list unresolved questions when the first answer is too broad.
  5. Create the next actionTurn the reviewed answer into a workflow item, Data Room request, page comment, investor update draft, or internal note.

Quick Comparison

Question TypeGood PromptExpected Review
KPI statusWhich connected sources updated Product KPIs this month?Open KPI provenance and sync status
Data Room Q&AWhich document answers this investor question?Open the cited document or page comment
Investor updateDraft bullets from current KPIs and recent milestonesVerify every metric and claim before sending
Diligence gapWhat evidence is missing for this claim?Decide whether to upload a source or create a request
Next actionCreate a follow-up from this answerReview the target, owner, and due date before relying on it

Frequently Asked Questions

What makes an Agent question source-backed?

A source-backed question asks Agent to answer from permitted workspace material such as documents, KPIs, Data Rooms, comments, or workflow records.

Should I trust an Agent answer without opening sources?

No. Source-backed answers are meant to be inspectable. Open the cited sources before sending investor-facing material or making a material decision.

What if Agent says evidence is missing?

Treat that as useful signal. Upload the missing document, sync the relevant app, record the KPI, or create a diligence request so the gap is tracked.

How do I keep Agent work from disappearing into chat?

Convert reviewed answers into durable Sabaki objects such as workflow items, comments, requests, updates, or source-backed notes.

Back to Sabaki