openspec-explore

Name: openspec-explore
Availability: InStock
Author: lbrlabs

Explore software architecture through iterative questioning and OpenSpec artifact generation.

1|1|Updated Sep 30, 2022

Search Tags:#design #architecture #thinking #problem-solving #exploration #openspec

Ready to run

npx skills add https://github.com/lbrlabs/pulumi-tailscale-bastion --skill openspec-explore-lbrlabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/lbrlabs/pulumi-tailscale-bastion/tree/main/.opencode/skills/openspec-explore
Command: npx skills add https://github.com/lbrlabs/pulumi-tailscale-bastion --skill openspec-explore-lbrlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured yet flexible environment for deep thinking, problem investigation, and requirement clarification, preventing premature implementation and ensuring well-reasoned solutions.

Core Features & Use Cases

Exploratory Thinking: Facilitates brainstorming, assumption challenging, and problem reframing without the pressure to write code.
Codebase Investigation: Maps architecture, identifies patterns, and surfaces complexity by grounding discussions in the actual codebase.
Artifact Generation: Captures design decisions, requirements, and tasks into OpenSpec artifacts when the user is ready to formalize their thoughts.

Quick Start

Invoke the explore mode to begin a collaborative thinking session regarding the current architecture by typing start explore mode.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I explore software architecture and clarify requirements before writing code?▼

To explore software architecture and clarify requirements, you can use a conceptual exploration environment that facilitates iterative questioning and visualization. This approach prevents premature implementation by mapping design decisions and grounding discussions in the actual codebase context.

What is the best way to brainstorm and challenge assumptions about a complex codebase?▼

The best way to brainstorm and challenge assumptions about a complex codebase is through structured exploratory thinking. This process surfaces complexity and identifies architectural patterns without the immediate pressure to write implementation code.

How do I capture design decisions and formalize architectural analysis into documentation artifacts?▼

You can capture design decisions and formalize architectural analysis by generating project documentation artifacts once your conceptual exploration is complete. This bridges the gap between abstract problem-solving and concrete implementation planning.

Do I need the OpenSpec CLI to map project architecture and investigate my codebase?▼

Yes, you need the OpenSpec CLI to map project architecture and investigate your codebase. Integration with the CLI is required to access codebase context and manage the generated project documentation artifacts.

Can I use conceptual exploration to reframe problems without generating implementation tasks?▼

Yes, you can use conceptual exploration to reframe problems independently of implementation. The environment supports assumption challenging and requirement clarification, only capturing tasks into artifacts when you are explicitly ready to formalize thoughts.

What are the limitations of using a thinking partner for software design exploration?▼

The limitation of using a thinking partner for software design exploration is its dependency on the OpenSpec CLI ecosystem. It requires integration with the CLI to access codebase context, meaning it cannot operate as a standalone reasoning tool.