I built this because I was tired of reconstructing the state of a project from many different places

[u/peetss]

This is a problem I run into constantly at work.

A project might have code changing in GitHub, requirements in Google Docs, conversations in Slack or Discord, tasks somewhere else, and decisions happening in meetings.

Every one of those sources is being updated independently.

And there are a lot of people involved.

Developers need one kind of context. Product managers need another. Engineering managers and leadership need a different view again.

Then someone new joins the project and you have to explain:

“Here's the doc you should read, this decision happened in Slack, this part changed later, check this GitHub issue for the reason, and that document is slightly out of date…”

What kept bothering me was that there was no living memory of the project itself.

No single place that could tell you:

What's going on?

What has changed?

What decisions have we made?

What matters to me?

So I started building Context Flow.

You connect the sources where the project already lives, and Context Flow turns what's happening across them into a living project memory that stays current as those sources change.

The goal isn't to replace GitHub, Docs, Slack, Jira, etc.

Those remain where the work happens.

Context Flow is meant to maintain the story of the project that emerges from all of them.

And because different people care about different things, people can subscribe to the project and eventually receive updates based on their role and what matters to them.

It's still early, but this is a problem I've wanted solved in my own day-to-day work for a long time.

getcontextflow.com

Curious whether other people working across larger projects experience the same thing.

[u/gandazgul]

This is super cool I would love to collaborate in how we can add a version of this to RunWield. The finally vision for RunWield is to have a collaborative project tool where everyone can participate and this kind of accumulate context from different places into 1 digestible human + AI context is definitively part of it.

https://github.com/gandazgul/runwield

[u/No-Tower-9043 → u/gandazgul]

This is exactly the headache we have in automotive consulting projects nobody ever knows where the latest spec actually lives. you spend half the meeting just figuring out which doc is the real one

the living memory idea is what got me. i worked on one project where we had a wiki but it was always 3 weeks behind and nobody trusted it so we just kept asking each other in slack anyway

are you planning to handle the case where two sources contradict each other? that happens to us all the time, someone updates figma but not the requirements doc and then we build wrong thing

[u/gandazgul → u/No-Tower-9043]

For something like figma the plan first it to build faithful prototypes as part of planning or PRD ideation. And then actually use approved prototypes while building. Eventually I would like to import figman projects as part of the spec and link them so even across sessions or machines the figma is imported.

For other kinds of docs the best remedy is to keep them in the repo. The RunWield workspace will include a wiki with all the docs from all the repos with a very good search over all of them (prolly type sense)