openspec-explore

Explores ideas, investigates codebases, and clarifies requirements before creating change proposals.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill openspec-explore-beliciobcardoso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/beliciobcardoso/mcp-postgres/tree/main/.qwen/skills/openspec-explore
Command: npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill openspec-explore-beliciobcardoso

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 any code is written. ## Core Features & Use Cases - Explore Mode Stance: Acts as a curious thinking partner that asks questions, challenges assumptions, and surfaces multiple directions without forcing a fixed workflow. - Codebase Investigation: Reads files, maps architecture, finds integration points, and visualizes systems with ASCII diagrams while never writing implementation code. - OpenSpec Integration: Detects active changes via the openspec CLI, reads existing proposals and designs, and offers to capture decisions in the right artifacts (specs, design.md, tasks.md). - Use Case: A developer is unsure whether to use Postgres or SQLite for a CLI tool. In explore mode, the assistant maps constraints, builds a comparison table, recommends a path, and offers to capture the decision in design.md. ## Quick Start Ask the assistant to enter explore mode and think through your idea or problem 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 software idea before writing code?▼

Enter explore mode and describe your idea or problem. The assistant asks clarifying questions, investigates the codebase, draws ASCII diagrams, and compares options without writing any implementation code.

What is OpenSpec explore mode used for?▼

Explore mode is a thinking stance for clarifying requirements and investigating problems before or during a change. It can read code and OpenSpec artifacts but never implements features, keeping exploration separate from execution.

Can explore mode create OpenSpec proposals or specs?▼

Yes, it may create OpenSpec artifacts such as proposals, designs, and specs when you ask, since that captures thinking rather than implementing. It offers to capture decisions but never does so automatically.

Does openspec-explore require any external tools?▼

It requires the openspec CLI to check for active changes using commands like openspec list --json and to read change artifacts such as proposal.md, design.md, and tasks.md.

When should I not use explore mode?▼

Avoid explore mode when you already know what to build and want implementation. Explore mode explicitly refuses to write application code, so exit it and create a change proposal when ready to implement.