openspec-explore

To clarify requirements and investigate a codebase before implementation, use a thinking-first explore mode that enforces safety guardrails against writing code while mapping integration points and comparing approaches.

Exploring software architecture without writing code involves using an exploration mode that prompts you to read existing artifacts, map integration points, and draft OpenSpec proposals while explicitly preventing any feature implementation.

Yes, you can draft OpenSpec proposals and specs during codebase investigation; the exploration mode supports optional artifact creation while maintaining guardrails that forbid actual code implementation.

Planning an AI workflow change through grounded discovery requires reading existing codebase artifacts, mapping integration points, and comparing options while operating in a strict no-implementation stance.

You should not use implementation-focused tools for ambiguous requirements because they encourage premature coding; an exploration mode with safety guardrails prevents implementation while supporting deep ideation and grounded discovery.

Yes, openspec-explore enforces a strict stance that prevents code implementation while facilitating workflow planning, requirements clarification, and the optional drafting of OpenSpec thinking artifacts.