openspec-explore

To explore codebase requirements without writing code, you investigate files and reason through user needs during early discovery. This thinking partner approach surfaces ambiguities and evaluates options based on actual codebase context before implementation begins.

Non-implementation thinking is best for evaluating options without code execution. It enforces a strict non-implementation stance, allowing you to read code and reason through ideas while preventing premature feature implementation.

Yes, you can generate OpenSpec artifacts like proposals and designs without writing code. The tool captures your requirement analysis and design thinking into formal specs while maintaining a strict non-implementation stance throughout the process.

This approach applies to both early discovery and existing codebases. It supports exploring user needs and evaluating options before implementation, while also reading and investigating actual code to ground contextual discussions during changes.

A thinking partner surfaces questions and directions before implementation, preventing costly rework. It keeps exploration open-ended and flexible, ensuring you clarify requirements and evaluate multiple directions rather than committing to premature code.