skills.rest
RyanCallahan312
RyanCallahan312COMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-explore

Guide structured exploratory thinking to clarify complex requirements.

Updated Mar 1, 2026
Search Tags:#codebase#requirements#openspec#explore#design-decisions#problem-framing#thinking-partner
One-click install
npx skills add https://github.com/RyanCallahan312/crayon --skill openspec-explore-ryancallahan312
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/RyanCallahan312/crayon/tree/main/.opencode/skills/openspec-explore
Command: npx skills add https://github.com/RyanCallahan312/crayon --skill openspec-explore-ryancallahan312

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify complex requirements by guiding structured exploratory thinking.

Core Features & Use Cases

  • Non-prescriptive exploration prompts that surface multiple directions and trade-offs.
  • Visual thinking aid with ASCII diagrams to map concepts, systems, and data flows.
  • OpenSpec-aware workflow: surface questions, decisions, and potential artifacts to capture.

Quick Start

Begin explore mode by outlining the problem you want to clarify and asking clarifying questions to surface requirements.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I clarify complex software requirements before writing code?▼

To clarify complex software requirements, you can use structured exploratory thinking to frame problems, evaluate trade-offs, and refine design decisions before implementation begins.

What is the best way to map system architecture and data flows during early design?▼

Mapping system architecture and data flows during early design is best handled by generating visual reasoning aids, such as ASCII diagrams, to outline concepts and system structures.

How do I evaluate trade-offs when framing a technical problem?▼

Evaluating trade-offs when framing a technical problem involves applying non-prescriptive exploration prompts that surface multiple directions and potential design decisions.

Can I use exploratory thinking to capture OpenSpec design decisions and artifacts?▼

Yes, exploratory thinking supports OpenSpec-aware interactions by surfacing relevant questions, decisions, and potential artifacts to capture during your design conversations.

Does structured problem framing work without enforcing a specific solution?▼

Structured problem framing works as a non-prescriptive thinking partner, guiding exploration to surface options rather than enforcing a specific technical solution.

What are the limitations of using exploratory thinking for requirement refinement?▼

Exploratory thinking for requirement refinement is limited to problem framing and trade-off evaluation, utilizing guardrails for safe thinking rather than generating executable code.

Related Skills

Explore More Software Engineering Skills→
yu13130122297yu13130122297

scout

Identify uncertainties in research framing, datasets, metrics, and baselines.

Community
Intermediate
DektoraDektora

prototype

Create disposable prototypes for exploring API shapes and state models.

Official
Intermediate
mrclrchtrmrclrchtr
54

openspec-explore

Facilitates exploratory thinking and requirements discovery for proposed OpenSpec changes.

Community
Intermediate
AndurilCodeAndurilCode
7

architecture-evaluation

Evaluate software architectures by scoring quality attribute trade-offs and outputting an ADR.

Official
Advanced