openspec-explore

Explore software architecture and problem spaces with structured thinking frameworks.

3|2|Updated Aug 1, 2025
One-click install
npx skills add https://github.com/ClearMeasureLabs/bootcamp-palermo-workorders --skill openspec-explore-clearmeasurelabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/ClearMeasureLabs/bootcamp-palermo-workorders/tree/main/.cursor/skills/openspec-explore
Command: npx skills add https://github.com/ClearMeasureLabs/bootcamp-palermo-workorders --skill openspec-explore-clearmeasurelabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured environment for deep thinking, architectural exploration, and problem investigation, preventing premature implementation and ensuring well-considered design decisions.

Core Features & Use Cases

  • Exploratory Stance: Facilitates brainstorming, assumption challenging, and problem reframing without the pressure to write code.
  • Visual Mapping: Generates ASCII diagrams to clarify system states, data flows, and architectural dependencies.
  • Contextual Integration: Connects with OpenSpec artifacts to track design decisions, requirements, and scope changes throughout the development lifecycle.

Quick Start

Activate the explore mode to begin a deep-dive analysis of the current codebase architecture and identify potential integration risks.

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 starting development?

Visualize system flows and architectural dependencies using tools that generate ASCII diagrams, helping you investigate codebase patterns and evaluate technical tradeoffs without writing implementation code.

Can I document design decisions and track scope changes within an OpenSpec ecosystem?

The skill integrates with OpenSpec artifacts to track design decisions, requirements, and scope changes throughout the development lifecycle. This ensures well-considered design decisions are documented within the ecosystem.

What is the best way to investigate codebase patterns and identify integration risks?

Activate the explore mode to begin a deep-dive analysis of your current codebase architecture. This investigation helps identify potential integration risks by evaluating technical tradeoffs.

How do I visualize system states and data flows during technical analysis?

Generate ASCII diagrams to clarify system states, data flows, and architectural dependencies. This visual mapping helps you evaluate technical tradeoffs and document design decisions.