Vibe Memo
A flight recorder for your product decisions. Vibe Memo keeps why your product was built the way it was, not just what changed.
What it is
Vibe Memo records the reasoning behind each decision. It captures the constraint that forced the call, the options you weighed, and the pivots when something changed. It lives alongside your work as a running decision trail.
Why we built it
Vibe Memo started as one skill inside the Skills Library. We use it on every project now. Code shows what was built. Git shows when. Neither keeps the why, and the why is the first thing lost when a project changes hands or a session ends. Vibe Memo keeps it.
How it works
It captures decisions as you make them, not in a doc you forget to update. Each entry carries the decision, the reason, the alternatives, and what would make you revisit it. The next person, or the next session, picks up the full context instead of guessing.