openspec-explore

Conduct conversational requirements discovery to reframe problems, surface hidden assumptions, and articulate tradeoffs. This guided exploration reads repository files to help you scope changes and produce design artifacts without committing to premature implementation code.

Use a conversational thinking partner to map architecture, identify integration points, and highlight technical debt. This codebase investigation approach reads repository files to outline state flows and list unknowns, capturing proposals and specs for early-stage design.

Yes, capturing OpenSpec artifacts like proposals, designs, and specs without implementation code is the core function. The conversational environment explicitly enforces a rule against producing code changes, focusing solely on requirements discovery and planning artifacts.

Visualize risks and unknowns by drawing ASCII diagrams and outlining state flows during the exploration process. This approach surfaces alternative approaches, lists technical debt relevant to a proposal, and suggests spikes needed to clarify requirements before implementation.

Yes, you need repository file access and the openspec CLI context to perform conversational requirements discovery. This environment provides the necessary codebase investigation capabilities to analyze ideas, map architecture, and produce OpenSpec artifacts.

Avoid using this conversational thinking partner when you need actual implementation code or direct file changes. It is strictly designed for early-stage planning, requirements discovery, and producing design artifacts, not for executing or writing implementation code.