openspec-explore

You can use a thinking partner to explore ideas and investigate requirements by asking clarifying questions and surfacing tradeoffs during early design conversations. This enforces a non-implementation stance to help teams map options and clarify requirements before committing to changes.

Reviewing existing specs and design notes involves reading and summarizing repository files and OpenSpec change artifacts. This approach proposes directions grounded in existing design work to help teams surface assumptions and ground conversations in repository context.

Yes, you can draft proposals and create OpenSpec artifacts without writing application code. The process enforces a non-implementation stance that permits creating design artifacts like proposals, specs, and tasks while strictly forbidding writing application code.

Yes, analyzing repository artifacts and OpenSpec changes requires the openspec CLI and repository read access. This setup enables the thinking partner to investigate codebase artifacts, summarize repository files, and ground design conversations in existing context.

Capturing decisions during early product discovery involves suggesting where insights belong, such as in proposals, designs, specs, or tasks. The tool facilitates this by offering to create OpenSpec artifacts when the user requests them to map options and clarify requirements.

Using a thinking partner prevents premature implementation by providing a focused exploration mode to think through ideas and investigate problems. This helps teams surface assumptions, map options, and clarify requirements before committing to code changes.