workflow-aware-brainstorming

Context-aware brainstorming anchors design proposals to parent workflow outputs, ensuring generated ideas reflect Step 1A/1B artifacts and dependencies. It integrates prior workflow context before generating ideas to prevent missing constraints.

Context-aware brainstorming preserves orchestration discipline by communicating required guardrails and transitions, then stopping for the orchestrator to continue. This ensures proposals respect established workflow boundaries and transitions.

Design proposals miss dependencies because brainstorming often lacks context from prior workflow artifacts. Context-aware brainstorming solves this by grounding idea generation in parent workflow outputs to maintain alignment.

Yes, context-aware brainstorming supports standalone behavior while preserving design-proposal discipline. When invoked outside a workflow, it still maintains the structural guardrails expected during design proposal generation.

Provide a design prompt that explicitly references Step 1A/1B outputs to guarantee the orchestration stays within the established workflow. This ensures generated proposals align with prior artifacts and orchestrator expectations.

Context-aware brainstorming stops after communicating required guardrails and transitions, signaling when to move to implementation steps. This transition signaling allows the orchestrator to resume control over the workflow.