flow-wisp

To prototype a feature without an audit trail, you can use an ephemeral exploration flow. It allows you to rapidly test proof-of-concept ideas and discard them entirely without leaving a persistent record of the exploration.

The best way to manage temporary research spikes with low ceremony is by creating a wisp flow. This minimizes process requirements during exploration and provides a structured directory for notes and findings.

To promote a temporary exploration task to a formal flow, you use the resolve options provided by the wisp. After exploring your prototype, you can promote the temporary task to a formal flow or discard it entirely.

Yes, you need the 'br' dependency to manage ephemeral exploration flows. The Skill utilizes 'br' commands for underlying task management when creating, updating, and resolving temporary exploration tasks.

You should avoid using ephemeral flows for prototyping when you need a permanent audit trail of your research process. This approach is designed for discarding or promoting, retaining no persistent record of the exploration itself.