What problem does it solve?
Teams often rush into implementation before fully understanding the problem, exploring all options, or clarifying requirements, leading to costly rework and misalignment. This Skill provides a dedicated thinking space to avoid that pitfall.
Core Features & Use Cases
- Non-prescriptive thinking partner: Adapts to your line of questioning, explores multiple directions instead of following a rigid script, and grounds discussions in your actual codebase when relevant.
- Visual problem exploration: Uses ASCII diagrams to map architecture, state flows, option tradeoffs, and system relationships to make abstract ideas concrete.
- OpenSpec integration: References existing change proposals, designs, and specs when relevant, and offers to capture new insights into the appropriate OpenSpec artifact when decisions are finalized.
- Use Case: For example, if your team is considering adding real-time collaboration, this Skill helps you map the collaboration spectrum (from presence awareness to CRDT-based sync), evaluate tradeoffs for your specific use case, and ground the discussion in your existing codebase before creating a formal change proposal.
Quick Start
Use the openspec-explore skill to think through our plan to add user notification features, investigate the current notification system in the codebase, and compare push vs in-app notification options before we start building.
