openspec-explore

To clarify requirements and explore design ideas before writing code, use a collaborative thinking partner that surfaces questions, maps multiple directions, and frames problems without implementing changes.

Framing architecture decisions requires grounding discussions in actual repository content. A thinking partner reads your codebase to keep design exploration realistic, identifies trade-offs, and visualizes concepts using ASCII diagrams.

Risk analysis during early feature discovery involves surfacing unknowns, trade-offs, and next steps. A problem-framing thinking partner helps map this space collaboratively while keeping changes to the codebase out of scope.

Yes, you can use problem-framing exploration without modifying your repository. This approach strictly reads repository content to ground discussions and explicitly keeps codebase changes out of scope during early design tasks.

Codebase exploration supports visualizing architecture by encouraging structured sketches and ASCII diagrams. This helps communicate ideas and map requirements collaboratively before any concrete implementation begins.

You should not use a thinking partner for problem framing when concrete code changes are required. It is designed strictly for early discovery, architecture decisions, and requirement clarification without implementing code.