Feature plans generated by agents are often transient documents that fall away once the plan is executed. Ideally, that artifact would be preserved alongside the implementation.
My experience is that Cursor's reliance on VS Code's clunky panel-based UI and jack-of-all-trades harness is holding it back. Likewise, Claude Code shoe-horning a GUI into a TUI and perma-binding to a single model family is not the ideal end-state.
The VC play here? The git context CLI thing is a foundational step that lays the groundwork for a full IDE/workflow tool, I guess.
Why do you want to preserve that artifact?
If you don't have a record of questions asked/answered and rationale for decisions taken, I've noticed it's easy for subsequent feature plans to clash. Maintaining a line of consistency across each feature plan is a good thing.