brainstorm

To clarify sponsor intent into testable requirements, you state the initial intent and select an exploration mode to surface directions, trade-offs, and structured decision artifacts for delivery planning. This process shapes vague requests into observable journeys with acceptance signals.

Pressure-test requirements by reading repository artifacts like code and docs alongside reference lenses to inform mode-driven questions or proposals. This evidence-grounded optioning validates assumptions and generates structured decision artifacts for later review.

Shape vague product requests by initiating open exploration to surface tensions and analogies, then switching to mode-driven shaping for concrete candidates. This produces structured outputs recording sponsor intent, observable journeys, and open questions.

Yes, you can use Mode 2 proposals to explore multiple directions during delivery planning, providing concrete candidates and recommended defaults. This mode-driven exploration supports evidence-grounded optioning when the sponsor is ready to evaluate specific paths.

Existing repo artifacts are not strictly required to start, as an open exploration stance can surface live directions without them. However, grounding in evidence from code, docs, and prior tasks significantly improves the quality of mode-driven questions and proposals.