What problem does it solve?
Jumping into software implementation without fully exploring ideas, clarifying requirements, or investigating existing code often leads to rework, missed requirements, and poor design choices. This skill eliminates that risk by providing a dedicated thinking partner for pre-development discovery and problem exploration.
Core Features & Use Cases
- Thinking Partner Stance: Acts as a curious, non-prescriptive collaborator to explore vague ideas, challenge assumptions, and reframe problems without pressure to reach a fixed conclusion.
- Grounded Codebase Investigation: Reads and maps existing code, architecture, and patterns to ground discussions in reality, surfacing hidden complexity and integration points.
- Visual Option Comparison: Uses ASCII diagrams to sketch state machines, data flows, and tradeoff tables to compare implementation approaches and surface risks.
- Use Case: If you have a vague idea to add real-time collaboration to your app, use this skill to explore the collaboration spectrum, map your current auth architecture, and compare CRDT vs. cursor-based sync tradeoffs before writing any code.
Quick Start
Use the openspec-explore skill to explore your idea for adding real-time collaboration to the app and compare the tradeoffs of different implementation approaches.
