Basically everything btown said but just to add my own POV -- we do this whole PRD - eng spec - implementation dance, and then comes maintenance, oops we missed

Basically everything btown said but just to add my own POV -- we do this whole PRD - eng spec - implementation dance, and then comes maintenance, oops we missed a few things, or didn't think about this. All those things end up in separate tools and very rarely make it easy to keep it all together, esp. without a great PM. Having a better way to link documents to actionable (tickets) and back, along with conversations that happen along the way, would be incredibly powerful. There's no shortcut for organization and I doubt a tool will ever solve it all, but I think the combination of wiki+task manager+interactive chat is utterly begging for a (good) unified tool that makes it easy to document, chat, and work tickets in the same place. I imagine the end result wouldn't be automatic quality documentation, but more like an automated blog of what stuff your company is shipping. People wanting to catch up (for context, new teamates, etc) can kind of peruse recently completed features and pick up a ton of context, or search specific ones and build a good understanding of how it was implemented (and why). It seems it would lend itself naturally to a culture of documented, intentional communication, rather than the splattering of slack messages and random tickets I see so commonly. If anyone has interest in working on this, happy to join up. Its high on my list of "want to" side projects.