openspec-explore

Explore ideas and clarify requirements through OpenSpec-guided conversational discovery.

1|Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Miftah-Fentaw/GymPulse --skill openspec-explore-miftah-fentaw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/Miftah-Fentaw/GymPulse/tree/main/.qwen/skills/openspec-explore
Command: npx skills add https://github.com/Miftah-Fentaw/GymPulse --skill openspec-explore-miftah-fentaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into implementation before fully understanding a problem, leading to rework and misaligned requirements. This Skill provides a structured thinking-partner mode for exploring ideas, investigating codebases, and clarifying requirements before or during a change, without writing any implementation code. ## Core Features & Use Cases - Guided Discovery: Acts as a curious thinking partner that asks focused questions, challenges assumptions, and surfaces risks and unknowns grounded in the actual codebase. - ASCII Visualization: Draws plain-ASCII diagrams, state machines, data flows, and comparison tables to clarify architecture and tradeoffs. - OpenSpec Integration: Reads existing changes and specs via the openspec CLI, and captures crystallized decisions into proposals, designs, specs, and tasks after explicit user confirmation. - Use Case: A developer considering real-time collaboration can explore the problem space, compare CRDT versus presence-based approaches with diagrams, then scaffold an OpenSpec change proposal once the direction is clear. ## Quick Start Ask the AI to enter explore mode and think through whether Postgres or SQLite fits your CLI tool before creating a change proposal.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I explore a feature idea before writing code?▼

Enter explore mode and describe your idea in natural language. The skill investigates the codebase, asks focused questions, draws ASCII diagrams of options, and only captures decisions into OpenSpec artifacts after you explicitly confirm.

What is OpenSpec explore mode used for?▼

Explore mode is a thinking-partner stance for clarifying requirements, comparing approaches, and investigating architecture before or during a change. It never implements code; it only reads, analyzes, and optionally captures confirmed decisions into change artifacts.

Does openspec-explore require the openspec CLI?▼

Yes, the skill requires the openspec CLI installed on the machine. It uses commands like openspec list, show, status, instructions, and new change to read project specs and scaffold change artifacts.

Can explore mode write code or implement features?▼

No, explore mode never writes code or implements features. It may create or update OpenSpec change artifacts such as proposals, designs, and specs, but only within a scope you explicitly confirm with a yes answer.

When should I exit explore mode and create a change proposal?▼

Exit explore mode when the problem and approach are clear enough to implement. The skill will offer to scaffold a change with openspec new change once insights crystallize, but the decision to formalize is always yours.