openspec-explore

Visualizing system design involves mapping architecture patterns and identifying codebase dependencies to clarify requirements. This Skill guides you through investigating complex topics and surfacing constraints using diagrams before any code is written.

Comparing design options requires brainstorming, diagramming workflows, and evaluating trade-offs to surface potential risks. This Skill facilitates decision-making by helping you investigate possibilities and clarify which approach best fits your problem.

Investigating a codebase requires mapping its architecture, identifying established patterns, and understanding internal dependencies. This Skill acts as a thinking partner to guide your exploration and surface constraints within your code repositories.

Yes, you can explore ideas and clarify requirements without immediate implementation. This Skill functions as a thinking partner that helps you think deeply, visualize complex systems, and solve problems through questions before committing to code.

You need a thinking partner when facing a complex feature or troubleshooting an architecture problem that requires visualizing workflows. It helps you map systems, investigate topics, and surface constraints to clarify your project requirements.

Exploring system design without implementation focuses on visualizing ideas and clarifying requirements but does not generate actual code. It is limited to decision-making, mapping architecture, and surfacing constraints rather than producing executable software.