openspec-explore

Architecture exploration is handled by acting as a thinking partner that surfaces clarifying questions, maps tradeoffs, and visualizes options without generating code. It grounds discussions in real codebase structure to clarify requirements during early discovery.

Investigating codebase problems involves identifying uncertainties, edge cases, and dependencies while providing visual diagrams. The tool surfaces risks and clarifies requirements without implementing changes, ensuring safe discovery before development.

Design proposals and architecture sketches can be generated on request while adhering to guardrails that prevent code implementation. The tool offers artifacts like designs or proposals rather than code generation to maintain strict discovery boundaries.

Visualizing design options requires mapping multiple directions and cognitive exploration of the problem space. The tool provides visual diagrams and references real code structure to ground discussions, helping clarify requirements before any implementation begins.

The thinking partner works entirely without external dependencies or libraries, operating as a standalone exploration tool. It requires no setup beyond the conversation itself to investigate problems and articulate the problem space within a project.

You should not use this exploration approach when you need actual code implementation, prompt hijacking, or direct codebase changes. It is strictly limited to discovery, risk identification, and surfacing questions rather than producing functional code.