openspec-explore

Explores ideas and clarifies requirements through OpenSpec change artifacts and codebase investigation.

7|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/Printaga/PiLot --skill openspec-explore-printaga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/Printaga/PiLot/tree/main/.agents/skills/openspec-explore
Command: npx skills add https://github.com/Printaga/PiLot --skill openspec-explore-printaga

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 that helps you explore ideas, investigate the codebase, and clarify requirements before or during a change—without writing any implementation code. ## Core Features & Use Cases - Guided Discovery: Asks focused questions, challenges assumptions, and surfaces risks while grounding discussion in your actual codebase and existing OpenSpec artifacts. - ASCII Visualization: Draws architecture sketches, state machines, and comparison tables in plain ASCII to clarify complex thinking. - OpenSpec Integration: Reads project context via the openspec CLI, scaffolds new changes with openspec new change, and captures decisions into proposals, designs, specs, and tasks with explicit user confirmation. - Use Case: Before adding real-time collaboration to your app, enter explore mode to map the collaboration spectrum, compare CRDT versus simpler presence approaches, and capture the resulting decisions in a change proposal. ## Quick Start Ask the AI to enter explore mode and think through whether your planned feature should use SQLite or Postgres 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. The skill investigates your codebase, asks focused clarifying questions, draws ASCII diagrams of options, and only captures decisions into OpenSpec artifacts after you explicitly confirm the scope.

How to create an OpenSpec change proposal from a discussion?▼

Once exploration crystallizes, confirm the capture scope and the skill runs openspec new change to scaffold the change, then follows openspec status and instructions to create the proposal, design, specs, and tasks in dependency order.

Does openspec-explore require the openspec CLI installed?▼

Yes, the skill requires the openspec CLI for all spec and change operations such as list, status, instructions, and new change. Without it, the skill cannot read project context or scaffold change artifacts.

Can explore mode write code or implement features?▼

No, explore mode never writes code or implements features. It may only read files, run read-only commands, and create or update OpenSpec change artifacts within a scope you explicitly confirm first.

What is a store in OpenSpec and when do I need one?▼

A store is a standalone OpenSpec repository registered on your machine. If your work lives in one, the skill discovers store ids with openspec store list --json and passes --store <id> on all commands that read or write specs and changes.