explore

To clarify requirements before coding, use a structured exploration process to frame questions, surface assumptions, and align stakeholders before committing to changes. This approach reduces wasted effort by ensuring teams understand the problem space early.

The best way to brainstorm ideas and read a codebase is to enter a dedicated exploration mode that facilitates deep thinking without writing code. This structured space allows you to safely analyze the codebase and identify requirements before design.

Structure design thinking conversations by outlining the scope of exploration, suggested activities, and guardrails for safe thinking. This approach provides guidance on structuring discussions and ideating artifacts to align stakeholders before implementation.

You should transition from exploring requirements to designing concrete tasks once you have thoroughly read the codebase, surfaced assumptions, and clarified the scope. The process provides explicit guidance on when to move from exploration to design.

Yes, you can use exploration techniques to identify assumptions without writing code by following established guardrails for safe thinking. This mode supports collaborative ideation and reading the codebase specifically before making any changes.

Structured exploration helps with framing questions for stakeholder alignment by providing a dedicated space to think through problems and ideate artifacts. This ensures stakeholders are aligned on requirements before proceeding to design or changes.