I want this but for projects and retros.<p>A sort of way to explain what lead to the current state of things.<p>For instance maybe times when we first get a task ie. "build this feature that calculates these obscure taxes" we start by doing tons of leg work and asking specialists and trying to pin point decision makers and making them make decisions. Then we draw on the board and come up with even more questions and the process starts anew.<p>Normally questions and decisions would be recorded in jira as comments to epics or stories and their solutions but it kinda sucks to look through if you're trying to find what the hell lead to the current state of things (for some definition of thing).<p>Something like this could be a cool way to record paths of the project took and how we got there. Because the format makes sense - I want to do X -> I asked Y -> he told me to do Z -> technical limitations make Z not possible -> we are now doing Z` which is ugleir but works.
I went to the site, couldn't figure out what it does, and left. That's not a "please explain it to me here," that's a "I think your site would be more effective if you explained what you built and why a visitor would care."
Interesting idea. I think this is actually the natural way of writing for most people, at least for me. Some improvements can be done in the UX to make the navigation easier. Also, I didn't get how the final text is being generated.