openspec-explore-ai-kit

To investigate design tradeoffs before implementation, use a structured exploration stance that maps architecture, finds integration points, and keeps multiple solution options open without writing code. This clarifies ambiguous goals and surfaces major unknowns early.

The best way to explore requirements is through codebase-grounded investigation that reframes problems and asks emergent questions. This approach identifies existing patterns and integration points while maintaining an OpenSpec-aware thinking stance to avoid premature implementation.

Yes, you can analyze your codebase safely because this approach enforces strict guardrails to avoid writing code. It focuses entirely on requirement discovery and design space investigation, explicitly preventing implementation while guiding you to create OpenSpec proposals.

You may need the openspec CLI installed to verify its availability when creating proposals or design spec artifacts. The exploration process focuses on clarifying goals and investigating the codebase, but checking the CLI is required for OpenSpec-aware thinking.

You should avoid using codebase analysis for requirement discovery when you are ready to write code or need immediate implementation. This approach is designed for early change planning and ongoing discussions, explicitly maintaining strict guardrails to prevent implementation.