Keeping Cursor from losing deferred build tasks
When building with Cursor, there is a need for one command or workflow that lays out the next s. Optional improvements that are pushed to later can disappear from both the developer's memory and Cursor's . The goal is to keep one main roadmap, epics, and todo list so future work does not get scattered across chats or memory.
Key points
- The needed workflow is a single Cursor command or routine for next s.
- Deferred optional improvements are the main things getting lost.
- The list should act as the one official roadmap, epics, and todo source.
- The practical concern is between the human maker and Cursor.