openspec-explore

To explore architectural impact before a refactor, map integration points and visualize proposed structures using ASCII diagrams to discuss tradeoffs. This approach grounds your architectural investigation in the existing codebase to surface risks before implementation.

The best way to compare technical approaches is through collaborative brainstorming that sketches tradeoffs and surfaces risks for each option. Comparing options visually helps challenge assumptions and clarifies which architectural pattern fits your requirements.

Yes, you can use a thinking partner to clarify requirements for complex software problems through natural language interaction. It facilitates deep exploration by challenging assumptions and grounding the discussion in codebase artifacts without pushing for immediate implementation.

Map architecture and find integration patterns by investigating the codebase to identify structural connections and recurring designs. Codebase investigation visually maps these components, helping you understand system relationships and locate where new features should connect.

You should not use exploratory brainstorming when you need immediate code implementation or prescriptive solutions. This exploration process is non-prescriptive and focuses on architectural mapping and option comparison rather than directly writing or generating final code.