openspec-explore

Explore ideas and clarify requirements through collaborative codebase analysis.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/augentic/vectis --skill openspec-explore-augentic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/augentic/vectis/tree/main/.cursor/skills/openspec-explore
Command: npx skills add https://github.com/augentic/vectis --skill openspec-explore-augentic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as a thinking partner to help users explore ideas, investigate problems, and clarify requirements before or during a development process, without directly implementing code.

Core Features & Use Cases

  • Collaborative Thinking: Engages in open-ended discussions to brainstorm approaches and challenge assumptions.
  • Codebase Investigation: Can read files and search code to ground discussions in the existing architecture.
  • Option Comparison: Helps compare different approaches and visualize tradeoffs.
  • Use Case: A user is unsure about the best way to implement a new feature. They engage this Skill to discuss potential architectures, explore existing code patterns, and visualize the pros and cons of each option before committing to a design.

Quick Start

Use the openspec-explore skill to think through the implications of adding real-time collaboration to the application.

Frequently Asked Questions about openspec-explore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify software requirements through brainstorming before writing code?

Clarifying software requirements through brainstorming involves a collaborative thinking process to investigate problems and explore ideas before implementation. This approach acts as a conversational partner, asking targeted questions to challenge assumptions and deepen understanding of the problem space.

Can I analyze my codebase to compare architecture options for a new feature?

You can analyze your codebase to compare architecture options by reading existing files and searching code patterns. This grounds the discussion in your current architecture, allowing you to visualize tradeoffs and evaluate different approaches before committing to a specific implementation design.

What is the best way to explore design thinking for software development decisions?

Exploring design thinking for software development involves engaging in open-ended discussions to brainstorm approaches and visualize pros and cons. It supports collaborative decision-making by helping you map out implications and compare options interactively before starting the actual development.

Does this requirements clarification process generate code or implementation files?

This requirements clarification process does not generate code or implementation files. It operates strictly as a thinking partner to facilitate idea exploration, investigate problems, and clarify requirements, leaving the actual code implementation to downstream development phases.

How do I visualize tradeoffs when comparing different software design approaches?

To visualize tradeoffs when comparing software design approaches, you can engage in an interactive option comparison process. This method helps you map out the pros and cons of each potential architecture, ensuring you fully understand the implications before making a final design decision.