openspec-explore

Explores ideas and project needs interactively without changing files.

4|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/jankneumann/agentic-coding-tools --skill openspec-explore-jankneumann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/jankneumann/agentic-coding-tools/tree/main/.agents/skills/openspec-explore
Command: npx skills add https://github.com/jankneumann/agentic-coding-tools --skill openspec-explore-jankneumann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill provides an interactive thinking partner that helps users explore ideas, investigate problems, and clarify requirements without writing code or making implementation decisions.

Core Features & Use Cases

  • Curiosity‑driven conversation: Ask open‑ended questions and surface multiple directions.
  • Codebase investigation: Read files, run OpenSpec CLI commands, and ground discussions in actual code.
  • Visualization: Generate ASCII diagrams, state‑machine sketches, and comparison tables on the fly.
  • OpenSpec integration: Suggest creating or updating OpenSpec artifacts (proposals, designs, specs) while staying in explore mode.
  • Risk & unknowns surfacing: Highlight potential pitfalls, gaps, and needed spikes.

Quick Start

Invoke the skill by typing /openspec-explore to begin an exploratory conversation.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I explore ideas and clarify requirements without writing code?

You can explore ideas and clarify requirements by invoking an interactive thinking partner that asks open-ended questions, investigates your codebase, and visualizes concepts using ASCII diagrams without executing code.

What's the best way to visualize system designs and state machines during brainstorming?

The best way to visualize system designs during brainstorming is to generate ASCII diagrams, state-machine sketches, and comparison tables on the fly, ensuring visual representations stay lightweight and text-based.

Can I use OpenSpec CLI to investigate my codebase during requirement gathering?

Yes, you can use OpenSpec CLI compatibility to read artifacts, run commands, and ground your requirement gathering discussions in actual code to surface risks and unknowns.

Does this requirements exploration approach suggest creating OpenSpec artifacts?

Yes, this requirements exploration approach suggests creating or updating OpenSpec artifacts like proposals, designs, and specs while staying in an exploratory mode without making implementation decisions.

When should I not use an exploratory conversation for design discussions?

You should not use an exploratory conversation for design discussions when you need to write code, make final implementation decisions, or execute scripts, as this approach strictly enforces no code execution.