workflow · 2026-04-20

Using GitHub as product memory

Research, plan, build, test, and ship become much easier to sustain when they are encoded as issue and PR templates.

Good repositories make product intent visible. When pricing changed, support changed, or the design direction changed, GitHub should hold that history in issues and pull requests instead of chat fragments.

For indie builders this matters because context loss is one of the fastest ways to slow down shipping.