Brainstorm Save and Handoff

This workflow wraps the shaping skill. Shaping owns requirements, solution shapes, fit checks, selection, spikes, and slicing decisions; do not reproduce or alter that method here.

Shape

Use the active or completed shaping result when one exists; the latest save or handoff request supplies authorization, path, and template choices rather than a new feature description. For a new topic, use the user's feature request. Ask what problem to explore only when neither the topic nor a shaping result is available.

Load and follow shaping. If the request is already specified well enough to plan or implement, continue with the user's requested outcome instead of forcing a brainstorm ceremony.

Save

Create a brainstorm file only when the user authorized a durable artifact or asked to continue through a repository workflow that requires one. Otherwise return the shaped result in the conversation.

Before saving, read references/brainstorm-artifact.md. Follow an existing repository path or template when one is defined. Otherwise use: