Inspiration
In enterprises, when employees leave or move to different teams, knowledge is lost. New team members may not know the basis for past decisions or what architectural choices were considered and abandoned. Which design decisions caused production issues.
What it does
Our solution scours specific channels where conversations on design decisions happened, architecture documents were shared and production issues were dealt with to educate the current team so they may not repeat the past mistakes. It also provides them contacts of key people they can reach out to for guidance and learning from past experiences
How we built it
We used Slack MCP server to retrieve the relevant channels and messages. We prototyped 2 approaches. One i which we pass the messages to LLM and a second one which uses Claude MCP connector to let Claude query the MCP server on our behalf
Challenges we ran into
We had to do some trial and error in terms of which tokens were needed. We did not want to publicly host our solution, hence went with the websocket approach which took a little bit time to get right.
Accomplishments that we're proud of
We set up a Slack sandbox and were able to get the end to end code and testing done in a few days.
What we learned
We learnt to use Claude Code to do research and brainstorming. We learnt effective way of understanding the large amount of Slack documentation
What's next for Lore
We want to connect it to Confluence so we can get some of the architecture documents and documented design decisions
Log in or sign up for Devpost to join the conversation.