openspec-explore

To clarify requirements, you can use exploratory thinking to investigate the codebase and map out the problem space before implementation. This Skill acts as a visual thinking partner to help brainstorm options and understand potential complexities without writing code.

Investigating codebase implications involves reading files and analyzing context to understand the impact of a proposed change. This Skill helps you explore the problem space and capture insights as formal proposals or specifications without implementing the solution.

Yes, exploratory thinking allows you to compare architectural options and map out the problem space without writing implementation code. This Skill serves as an adaptive thinking partner to help you evaluate concepts and challenges before committing to a specific design.

Yes, the requirements clarification process integrates with the OpenSpec system to capture insights. As you explore ideas and solve problems, the Skill records your decisions and findings as formal proposals, designs, or specifications within the system.

You should not use exploratory problem-solving when you need to implement the solution, as this Skill explicitly focuses on investigation and clarification without writing code. It is designed for mapping out the problem space and capturing insights, not for generating the final implementation.