openspec-explore

To clarify requirements before changing code, use a thinking-first exploration stance that surfaces assumptions and reframes the problem without implementing features. This approach guides structured discovery and requirement clarification safely.

The best way to investigate a codebase is grounded exploration that reads and searches the repository to understand architecture. This maps integration points and identifies risks without writing code.

Yes, you can explore design tradeoffs without writing code by comparing parallel directions and mapping unknowns. This method enforces guardrails against implementation while building comparison tables for informed decision-making.

You map risks during requirement discovery by applying an exploration stance that identifies unknowns and compares options. This creates risk mapping artifacts to guide what to do next without modifying the codebase.

Yes, the exploration approach allows reading files and creating OpenSpec artifacts when requested. However, it maintains explicit guardrails against writing code or implementing features during the investigation.

You should not use structured codebase investigation when you need immediate implementation rather than discovery. It is designed for early ideation, requirement clarification, and mid-change troubleshooting, not for writing production features.