openspec-explore

Explore problems and clarify requirements with ASCII diagrams.

57|17|Updated May 5, 2025
One-click install
npx skills add https://github.com/jerome-benoit/freqai-strategies --skill openspec-explore-jerome-benoit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/jerome-benoit/freqai-strategies/tree/main/.opencode/skills/openspec-explore
Command: npx skills add https://github.com/jerome-benoit/freqai-strategies --skill openspec-explore-jerome-benoit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a thinking-partner mode that helps users think through problems, explore ideas, and clarify requirements without moving to implementation.

Core Features & Use Cases

  • Non-prescriptive thinking: Surface multiple directions, ask clarifying questions, and visualize ideas with ASCII diagrams.
  • Context-grounded exploration: Ground discussions by referencing relevant files and code context while avoiding changes to the codebase.
  • Use Case: Ideal when you want to scope a problem, frame requirements, and decide on next steps before coding or building.

Quick Start

Enter explore mode and think deeply, visualize freely, and follow the conversation where it leads.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I frame requirements and explore ideas before writing code?

This approach helps you scope problems by grounding discussions in relevant files and code context, visualizing ideas with ASCII diagrams, and surfacing open questions while actively avoiding changes to the codebase.

Can I use this to brainstorm and scope project changes without modifying my codebase?

It acts strictly as a non-prescriptive thinking partner, offering clarifying questions and ASCII visualizations to help you understand the impact of changes before acting.

What is the best way to visualize problem framing during requirement exploration?

These text-based visualizations help ground your context and clarify requirements without needing external diagramming tools.

Does this exploration approach work for decision-making during project changes?

It applies directly to brainstorming and problem framing when you need to decide on next steps during project changes.

When should I avoid using a thinking partner for requirement clarification?

It is designed exclusively for exploration, scoping, and understanding context rather than producing functional code or modifying files.