Hey Product Hunt 👋 I built Context Flow because I kept running into the same problem on projects: **the work is moving, everyone is learning things, decisions are being made — but the actual story of the project is scattered everywhere.** A requirement changes in a doc. A risk comes up in chat. A decision gets made in a meeting. Code changes. Tickets move. Individually, everyone has pieces of the picture. Very few people have the whole thing. And keeping documentation current usually depends on someone finding the time to manually collect all of that information and rewrite it. **Context Flow is an attempt to change that.** You create a project, add the sources where the work is happening, and Context Flow turns that information into a living project memory — organized documents covering things like what the project is, decisions that have been made, risks, requirements, and open questions. As those sources change, the project memory changes with them. But I think the more interesting part is what happens next. Projects are social, and the same change doesn't mean the same thing to everyone. An engineer, a PM, and a stakeholder shouldn't all have to consume the exact same stream of updates. People can subscribe to a Context Flow project, and when something changes, Context Flow can deliver the context that's relevant to *their role*. The goal isn't to replace Slack, Discord, docs, GitHub, Jira, or the other places where work happens. **It's to give all of that motion a memory.** Context Flow is still early, and that's a big reason I'm launching it here. I'd love feedback on the core idea, what sources you'd want connected first, and whether this is a problem you run into on your own projects. Thanks for checking it out 🙌

Context Flow

Context that stays current as your project changes.

Context that stays current as your project changes.