openspec-explore

Requirements clarification involves using a thinking partner to prompt open-ended questions, surface hidden assumptions, and map out alternatives before implementation. This skill guides non-implementation exploration to investigate questions and structure design discussions thoughtfully.

Codebase investigation without implementing changes is supported by guiding you through reading and assessing a repository. The skill emphasizes thoughtful questioning over coding, helping you explore the codebase, surface risks, and map options using ASCII visualization.

Creating OpenSpec artifacts like proposals, designs, and tasks is supported during a guided thinking session. You can request these artifacts directly while exploring ideas and clarifying requirements, ensuring thoughtful design documentation is generated without writing implementation code.

Visualizing options and risks during design discussions is best handled through ASCII diagrams and structured exploration. This approach maps alternatives and surfaces potential issues, providing a clear visual organization to help you think aloud with a partner.

Yes, mapping out project assumptions works effectively with a curious exploration approach. The thinking partner prompts you with open-ended questions specifically designed to surface underlying assumptions and alternatives, ensuring all possibilities are considered before making changes.

You should avoid using a requirements clarification thinking partner when you need to actually implement code changes, as this is strictly a thinking-only exercise. It is designed for exploration, artifact creation, and design discussions rather than direct code modification.