Skip to content

talk query enhancement #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
davidguttman opened this issue May 6, 2025 · 0 comments · May be fixed by #2
Open

talk query enhancement #1

davidguttman opened this issue May 6, 2025 · 0 comments · May be fixed by #2

Comments

@davidguttman
Copy link
Contributor

davidguttman commented May 6, 2025

We want to enhance the AI in Action bot to enable users to query information about previous talks. The bot should be able to respond to questions like "@bot has there been a talk about A2A before?" or "@bot what talks have been about agents?". Response should follow same format as responses to questions about upcoming speakers.

This will require planning the architecture and implementation. Please use a modular approach to facilitate independent testing of components.

Design the high-level architecture for this feature, considering how to store and retrieve information about past talks.
Break down the implementation into smaller, manageable steps.
Specify which files need to be updated or added, including mongo db for storing talk information and for handling user queries.
Outline how the modular design will support independent testing of each component.
this is a low usage app, don’t need to rely on the db for querying specific talks, just pull all and let LLM evaluate matches

Before making any changes, please provide a planning doc detailing the architecture, steps, and file modifications.

PR to close this issue should contain:

  1. Planning doc docs/plans/03-talk-history.md that specifies the required tests and implementation
  2. New tests from planning doc
  3. New implementation changes from planning doc
@ts-superstruct ts-superstruct linked a pull request May 6, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant