Catch the thought before the review moves on.

You are reviewing a PR when you notice it: the validation logic in this component is duplicated three times and would collapse into one shared hook. It has nothing to do with the change in front of you, and flagging it as a review comment would either derail the PR or get lost in a thread nobody revisits. So you keep reading, tell yourself you will remember, and by the time you are back at your own desk the specific shape of the refactor — which files, which pattern, why now — has gone soft.

Later that afternoon a test flakes in CI for the second time this week. You do not have a block of time to chase it right now, but you noticed something: it only fails on the slower runner, and the assertion that fails is always the one checking a timestamp. That detail is the whole value of the observation, and it is exactly the kind of thing that evaporates by the time you finally get an hour to debug it properly.

In standup someone floats a feature idea that would need a spike before anyone can scope it. It sounds worth exploring, but you are mid-sprint on something else, and the meeting moves on to the next person in about eleven seconds. Nothing about that idea gets written down unless you stop the meeting to do it, which nobody does. Vaps exists for exactly this shape of interruption: an idea that has to be written down without pulling you out of the thing you are already doing.

The Developer profile relabels Vaps around the categories you already sort work into: Feature for the enhancement idea, Bug for the thing that is broken, App for a build worth its own space, and Thought for everything else that does not fit yet. Picking Developer in Settings changes this wording throughout the app; picking a different profile does not touch the ideas you already captured.

The status flow is short by design: Fresh, Exploring, In Progress, Shipped. A refactor idea from a review starts Fresh. If you decide it is worth a spike, move it to Exploring. Once you are actually doing the work, In Progress. Ship it, and the status change marks it done. You cycle the status inline on the idea card; you do not have to open the idea to update it.

None of this replaces your issue tracker or your CI dashboard. What it gives you is a place to keep the idea specific — the pattern you saw, the failing assertion, the spike someone floated — until you have the attention to move it into whatever your team actually works from. Nest a bug under the app or feature it affects, tag it by repo or area, and search for it later instead of trying to reconstruct it from memory.

Related

• Fast capture
• No account
• For founders
• For professionals