openspec-explore

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

13|3|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/gqcn/lina --skill openspec-explore-gqcn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/gqcn/lina/tree/main/.agents/skills/openspec-explore
Command: npx skills add https://github.com/gqcn/lina --skill openspec-explore-gqcn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into implementation before fully understanding a problem, leading to rework and misaligned designs. This Skill provides a structured thinking partner that helps you explore ideas, investigate the codebase, compare options, and clarify requirements before committing to a change. ## Core Features & Use Cases - Exploration Stance: Acts as a curious thinking partner that asks clarifying questions, challenges assumptions, and surfaces risks without following a rigid script. - Codebase Investigation: Reads files, maps architecture, finds integration points, and grounds discussions in the actual code rather than theory. - OpenSpec Integration: Detects active changes via the openspec CLI, reads existing proposals and designs, and offers to capture decisions in the right artifacts (proposal.md, design.md, tasks.md, specs). - Use Case: Before adding real-time collaboration to your app, use this Skill to map the collaboration spectrum, compare CRDT versus presence-based approaches with ASCII diagrams, and crystallize the decision into an OpenSpec change proposal. ## Quick Start Ask the AI to enter explore mode and think through your idea or problem, for example by describing a vague feature idea or a pain point in your codebase.

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 acts as a thinking partner that asks clarifying questions, investigates your codebase, draws ASCII diagrams, and helps compare approaches before you commit to implementation.

What is OpenSpec explore mode used for?▼

Explore mode is a thinking stance for investigating problems and clarifying requirements without implementing anything. It can read code and OpenSpec artifacts, and may create proposals or specs when asked, but never writes application code.

Can explore mode implement features or write code?▼

No. Explore mode explicitly forbids writing code or implementing features. If you ask for implementation, it will remind you to exit explore mode and create a change proposal first, keeping thinking separate from building.

Does openspec-explore work with existing OpenSpec changes?▼

Yes. It runs openspec list to detect active changes, then reads proposal.md, design.md, tasks.md, and specs for context. When decisions emerge during discussion, it offers to capture them in the appropriate artifact.

When should I use explore mode versus creating a change proposal directly?▼

Use explore mode when the problem is vague, options are unclear, or you are stuck mid-implementation. Create a proposal directly once the approach is crystallized. Explore mode can transition into a proposal when thinking solidifies.