openspec-explore

Explore ideas and clarify requirements during change discussions.

2|2|Updated Sep 20, 2023

Search Tags:#codebase #requirements #guidance #openspec #explore #think-aloud #problem-framing

Ready to run

npx skills add https://github.com/zabiny/klabis --skill openspec-explore-zabiny

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured thinking partner to help teams explore ideas, clarify requirements, and surface assumptions before committing to changes.

Core Features & Use Cases

Non-implementation exploration: think aloud without writing code or executing changes.
Codebase context reading: review existing code and design documents to ground discussion.
Visual reasoning: generate ASCII diagrams and architecture sketches to clarify complex problems.
Risk surfacing: surface uncertainties, known unknowns, and potential pitfalls early.
OpenSpec artifact support: propose design thoughts and coaching prompts if requested.

Quick Start

Tell me what you want to explore and I will help you think through it step by step.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

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

To clarify requirements, use a structured thinking partner to think aloud, surface assumptions, and frame problems before committing to implementation changes.

Can I review existing codebase context to ground design discussions?▼

Yes, you can read existing codebase context and design documents to ground exploration sessions and ensure architectural discussions align with current system constraints.

What's the best way to visualize architecture during problem framing?▼

The best way to visualize architecture during problem framing is generating ASCII diagrams and visual sketches to clarify complex problems and map out system interactions.

How do I surface risks and unknowns early in a change discussion?▼

Surface risks early by exploring uncertainties and potential pitfalls in a structured think-aloud session, identifying known unknowns before they impact implementation.

Does this approach support generating OpenSpec artifacts during exploration?▼

Yes, it supports optional OpenSpec artifact generation, proposing design thoughts and coaching prompts to capture structured outputs during non-implementation exploration sessions.

When should I not use a think-aloud exploration approach?▼

Avoid think-aloud exploration when implementation is already well-defined and only execution remains, as this approach focuses on problem framing rather than writing code.