-
Notifications
You must be signed in to change notification settings - Fork 2
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
Scrum spike: Research prompt engineering techniques #160
Comments
@tubamos , Just an idea for research tasks can we create a notebook and submit them in sprint-dilevriables so that can be stored there and in next sprint we dont need to remove or fix them. |
yes, let's do this. We actually discussed this option in the past but we did not conclude on whether we do it that way or not because we wanted to check what options exist in github to make such tasks trackable for formal reasons. The option to commit any documents in the project folder as you suggest has been one option. I am fine with that if the devs agree. |
Different Prompt engineering techniques have been added to the code and have been pushed into the main branch. The current problem with prompt engineering is that all the scraped data is in a different format like each scraper has a different JSON structure due to which chunking is quite problematic. We need to create different classes for chunking different scraped data into the Vector Database. |
@manikg08 Let us disucss this during the sprint meeting today. |
Domain
data pipeline optimisation
Description
The focus of this scrum spike is to help the team familiarize with prompt engineering techniques that we will use to improve the interaction with the LLM(s). Popular techniques such as Chain-of-Thought (CoT) prompting and ReACT (integration of reasoning with actionable prompts) should be expored along with other techniques. The developers should engage in hands-on testing and and rank their proposals in relation to our use case.
Example documentaion:
https://www.promptingguide.ai/techniques
User Story
Acceptance Criteria
The text was updated successfully, but these errors were encountered: