convert-to-structured

Converting a vibe session into a structured workflow involves invoking the transition skill during your active session to collect and classify work items while preserving existing artifacts like diagrams and documents. This enables a seamless handoff to structured execution.

During the vibe-to-structured transition, existing artifacts such as diagrams, documents, and wireframes are fully preserved. The conversion process focuses on extracting and classifying work items without deleting or altering your prior brainstorming outputs.

Extracting and classifying work items from a brainstorming session uses guided prompts to transform vibe goals into structured categories like code, bugfix, or task. This itemization occurs during the transition to formal planning.

You should transition your brainstorming phase to structured execution when your vibe session goals need formal planning and itemization. Converting to structured mode captures artifacts, updates the design document, and routes you to structured brainstorming.

Yes, converting to a structured workflow updates your session state by applying the vibe-to-structured transition. It satisfies requirements to capture artifacts, create or update a design document, and route the session via complete_skill('vibe-active').

When switching to structured mode, the primary constraint is that your session must be an active vibe session. The conversion preserves artifacts and updates the design document, but requires guided prompts to classify work items for the structured brainstorm flow.