discuss

Structured feature ideation uses a divergent brainstorming workflow to explore intent and scope, generating one question per turn until a drop, park, or promote outcome is recommended and recorded into the log.

Resuming parked feature discussions requires loading prior handoff context and logs via the feature slug, continuing the brainstorming session, and updating the feature folder with the new outcome.

Acceptance testing alignment surfaces charter signals and decomposition flags throughout the ideation process, ensuring the recommended outcome respects architecture governance before any feature promotion.

Yes, feature promotion requires explicit user confirmation after the brainstorming session surfaces decomposition flags, ensuring architecture governance is applied before initializing the feature folder.

Dropping or parking a feature is recommended when divergent exploration reveals scope or intent limitations, logging the result as a handoff summary without auto-executing user confirmation.

Yes, spec-driven workflows emit handoff summaries for parked or promoted features, recording the session results into a discussions log to maintain continuity for future resumption.