Not the parent poster but: Imagine you have an elaborate user flow diagram for a complex workflow. Every state/page a user could find themselves in, the outboun

Not the parent poster but: Imagine you have an elaborate user flow diagram for a complex workflow. Every state/page a user could find themselves in, the outbound transitions perfectly match all cases of what someone might want to do. Now, these transitions end up quickly becoming stories: "A user in state X should be able to do Y." And you can bundle those together like "A user should be able to cancel and return to the project screen from any step of the wizard." Alternately, you can separate things by teams like "An API exists to cancel the reservation in progress, releasing the underlying inventory" vs. "A user can cancel the reservation in progress using the API" vs. "Factor out cancel buttons into a UI abstraction" if you want people to be able to pick those up and show progress independently. But fundamentally all this stems from an underlying plan, that flow chart from which all these stories flow. That plan is the epic. But that plan can't just be a frozen flow chart; it needs to be a living central repository of documentation, ideas, and mockups. Ideally, you have few enough of these epics that you can maintain things in the tools they're meant to be in: a Clubhouse epic, for instance, could simply link to the top-level Notion table of contents for the planning process for that epic. But if you're pulled in a billion different directions and have a massive feature surface, having this all in one place, alongside the chat related to that feature, with live references to the ongoing action items, would be incredible. Whether Kitemaker solves it or someone else, there's amazing work still ahead here.