aif-explore

To clarify requirements and explore architecture tradeoffs before coding, use a dedicated thinking space to investigate your codebase, challenge assumptions, and map out risks. This approach ensures technical decisions are grounded in existing patterns before implementation begins.

Codebase analysis for risk assessment involves reading the actual project code to map relevant architecture, find existing patterns, and surface hidden complexity. This identifies potential risks and unknowns to inform better decision-making before modifying application code.

Yes, you can compare multiple implementation approaches for a vague feature concept without modifying code by brainstorming options and building tradeoff comparisons. This clarifies requirements and captures decisions while keeping the application codebase untouched.

Finding the root cause of a complex bug requires structured problem investigation using a thinking partner to ask clarifying questions and reframe the issue. This method relies on codebase-grounded discussion to trace the origin without writing fixes.

You need to perform an architecture review before planning software changes when facing vague feature concepts, evaluating tradeoffs, or refining existing plans. It satisfies the need for risk identification and decision capture prior to any implementation work.