AI for Dev Tools: Create Software Requirements with Userdoc
Summary
“So when we’re talking to GPT-4,” he said, “we’re sending up [information about] all the other relevant features of your system.” He admitted that ChatGPT could achieve the same thing, but you’d need to construct “a huge prompt” to get a similar response to Userdoc. So it connects to Jira, or Azure DevOps, [or] anywhere that creates a work item [that] goes to ‘to do’, ‘in progress’ and ‘done’; and that synchronizes all this information of what the feature is.” Rickard noted that in some situations, software developers help build the requirements as well. “But I found that I wanted to understand what was happening behind the scenes; and LangChain is amazingly powerful, but what it brings to the table […] is handy, tried and true methods of doing certain tasks — such as reading a document, breaking it into little bits, sending it over to an LLM, and asking questions. So I just wrote my own communication layer for talking to GPT-4, and it significantly helps.” So if Userdoc can, over time, become the source of documentation for a piece of software, could it also be used to power a help chatbot on the customer side (for that grocery delivery service, for example)? “The main concern is really the internal versus external knowledge, and what people want to expose.” He pointed out that Userdoc is bootstrapped at the moment, but if he was to expand the team then his dream would be “to get more into the big boring part of compliance.” So he’d rather go in that direction than do what everyone else is doing — create a chatbot for a consumer-facing website or app.