skills.rest
lz-freedom
lz-freedomCOMMUNITY
Explore all skills by this author →
GitHub

openspec-explore

Explore codebases and design problems to clarify requirements with ASCII diagrams.

Updated Jan 23, 2026
Search Tags:#codebase#requirements#problem-solving#visualization#explore#design-discussion
One-click install
npx skills add https://github.com/lz-freedom/polybull-stock-helper --skill openspec-explore-lz-freedom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/lz-freedom/polybull-stock-helper/tree/main/.opencode/skills/openspec-explore
Command: npx skills add https://github.com/lz-freedom/polybull-stock-helper --skill openspec-explore-lz-freedom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode to serve as a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when a user wants to think through something before or during a change.

Core Features & Use Cases

  • Open-ended thinking: Ask questions, surface assumptions, and explore multiple directions without committing to any solution.
  • Codebase and design exploration: Read files and inspect architecture to ground discussions in the actual project.
  • Visualize and document thoughts: Produce ASCII diagrams and structured notes to communicate explorations.
  • Risk and unknowns surface: Identify potential risks, ambiguities, and tradeoffs to inform next steps.
  • OpenSpec stance and boundaries: Remain a thinking partner that does not implement changes, avoiding prompt injection and gatekeeping.

Quick Start

Start exploring by describing the problem or change you want to investigate. I will read relevant files, sketch diagrams, surface risks, and suggest exploration directions. If you want to change the mode or capture decisions, you can signal with the appropriate OpenSpec commands.

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 before implementing codebase changes?▼

To clarify requirements before implementing codebase changes, this guided exploration partner reads files, maps architecture, and surfaces risks without writing any actual code.

Can I generate architecture diagrams during design discussions without coding?▼

Yes, you can generate architecture diagrams during design discussions without coding. The exploration mode reads your codebase and produces ASCII diagrams to visualize and document thoughts.

What is the best way to investigate problems and surface risks in a project?▼

The best way to investigate problems and surface risks is using a thinking partner that identifies potential risks, ambiguities, and tradeoffs through open-ended questions and codebase exploration.

Does this exploration mode write code or modify files?▼

No, this exploration mode does not write code or modify files. It remains a thinking partner focused on problem analysis and design discussions, purposefully avoiding any actual coding changes.

When do I need an open-ended thinking partner for problem analysis?▼

You need an open-ended thinking partner for problem analysis when you want to think through something before or during a change, exploring multiple directions without committing to a solution.

Related Skills

Explore More Design & Creative Skills→
svssdevasvssdeva
1

grill-with-docs

Stress-test AI-generated plans against domain models and documented decisions.

Community
Advanced
OiAnthonyOiAnthony
8

openspec-explore

Explore ideas and clarify requirements before implementation using the openspec CLI.

Community
Intermediate
davpatel605-beepdavpatel605-beep

code-wiki

Generate structured wiki documentation and Mermaid architecture diagrams from source code.

Community
Advanced
fkoschifkoschi
2

openspec-explore

Explore software problems and clarify requirements with codebase analysis.

Community
Advanced