openspec-explore

To explore and clarify requirements, you can use a conversational thinking partner to investigate problems, ask clarifying questions, and visualize concepts without writing code. This approach grounds design decisions in actual project architecture before implementation begins.

Yes, you can compare architectural options by brainstorming different approaches and visualizing trade-offs. The tool generates ASCII diagrams to map out potential architectures, helping you evaluate risks and implications of new features against existing codebase constraints.

The best way to analyze a codebase during problem solving is through targeted investigation that reads files and searches code to ground discussions. This allows you to explore relevant parts of the architecture and clarify requirements based on actual project structure.

Yes, this exploration approach integrates with the OpenSpec system to reference existing changes and capture decisions. It logs outcomes and clarifications directly into relevant artifacts like proposals and designs, ensuring explored ideas are formally documented.

To think through implications of a major feature, you engage in open-ended exploration that asks clarifying questions about the topic. It investigates relevant codebase areas and helps visualize potential architectures or risks associated with the change.