openspec-explore

To clarify requirements and explore design tradeoffs without writing code, use a guided exploration workflow to map integration points, surface hidden assumptions, and draft OpenSpec proposals while enforcing a strict no-implementation constraint.

The best way to investigate a codebase for a proposed change is to read repository files, search relevant code, and map architecture to identify technical complexity and integration points before drafting a scoped design artifact.

To translate vague feature ideas into a scoped proposal, reframe the problem through probing questions, brainstorm real-time tradeoffs, and capture decisions in OpenSpec artifacts like designs and tasks without moving into implementation.

Yes, you can map architecture and identify integration points before implementation by reading and searching repository files to surface technical complexity and record next steps in design artifacts while avoiding production code.

You should avoid moving into code implementation during early design when you need to think through tradeoffs, surface unknowns, and map how changes touch the codebase or system design before committing to a specific solution.