openspec-explore

You can explore architectural ideas and investigate problems by entering a conversational discovery mode that asks clarifying questions and maps tradeoffs without writing or modifying code. This approach surfaces assumptions and identifies risks before implementation begins.

Yes, design ideation can read repository files and OpenSpec artifacts to ground architectural decisions in real context. This investigation maps integration points and clarifies requirements using actual codebase structures.

The best way to visualize architectures and workflows during early discovery is by generating ASCII diagrams, state machines, and comparison tables. These visualizations help map systems and evaluate options directly within the conversation.

No, this exploration mode explicitly refuses to write or modify code during architectural review. It functions strictly as a reflective thinking partner for mapping systems, identifying risks, and comparing approaches.

To map integration points and identify risks for a complex auth system, you can reference repository files and OpenSpec artifacts to trace logic, ask clarifying questions about edge cases, and sketch potential approaches using visual diagrams.

You need conversational discovery for pre-implementation feature planning when you must clarify ambiguous requirements, challenge assumptions, and surface unknowns. It provides a structured environment to reframe problems before committing to design changes.