Product Requirements Document
Mission
We want to allow users to bring their own API's for Retrieval Augmented Generation, i.e. "chat with your API."
Background
Chatting with documents using GPT has resulted in much better accuracy and usefulness (source 1, source 2, source 3, source 4, just to name a few).
Targeted Personas
- Knowledge worker – the knowledge worker has heard of ChatGPT and has thought about using in their day to day, or uses multiple times per day. They is a working professional, working as a software engineer, a marketer, a salesperson, or another white collar job.
- They will be able to utilize their company's various APIs (after their engineering team develops around the data contract)
Current Behavior
Today we do not allow for any plugin APIs to be utilized as part of Enterprise Chat. The only context given to a prompt is coming straight from the chat context itself. This would be a generalized version of "chat with your data." By extending this to any API that abides by a clearly defined contract, we expand away from just chatting with a document/chatting with a collection of files in Sharepoint. This becomes more open for any API that can provide document access.
Outcomes / Goals
- Provide desired end product/workflow.
Phased Release
- Phase 1: single document capability
- Phase 2: multi document capability
- Phase 3: bring any API capability
User Stories
Name/Descr
- story
Use cases
Case group name
- Case / user name
- Primary Actor:
- Description:
- Preconditions:
- Postconditions:
- Flow:
- Steps...
- Outcome
Requirements
Functional
- List of functional description of the feature
Non-functional requirements
- List of NFRs to focus on
Out of Scope
- Funtionality and cases out of scope for planned feature
- Might be treated as future updates that not yet planned and refined
Dependencies & Constraints
- Any kind of dependency
Assumptions
Risks
Timeline and Milestones
Phase I
- Release #.##
- Components, other deliverables