skills.rest
fjpulidop
fjpulidopCOMMUNITY
Explore all skills by this author →
GitHub

openspec-explore

Explore ideas and clarify requirements with ASCII diagrams without implementing code.

9|2|Updated Mar 12, 2026
Search Tags:#requirements#discovery#open-spec#explore#clarify#thinking-partner#ascii-diagrams
One-click install
npx skills add https://github.com/fjpulidop/specrails-core --skill openspec-explore-fjpulidop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/fjpulidop/specrails-core/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/fjpulidop/specrails-core --skill openspec-explore-fjpulidop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode to provide a thinking partner that helps you think through ideas, investigate problems, and clarify requirements before making changes, without writing or implementing code.

IMPORTANT: Explore mode is for thinking, not implementing. You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features.

Core Features & Use Cases

  • Thinking partner for exploration: asks clarifying questions, surfaces multiple directions, and frames problems.
  • Codebase awareness and visualization: reads the repository, visualizes relationships with ASCII diagrams, and tracks risks and unknowns.
  • OpenSpec-guided discovery: references existing artifacts, prompts decisions, and suggests next steps without producing executable changes.

Quick Start

Enter explore mode by asking clarifying questions, visualizing options with ASCII diagrams, and outlining potential directions.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I clarify project requirements without writing any code?▼

You can explore ideas and clarify requirements during early discovery by using a thinking partner that asks questions, frames problems, and visualizes codebase relationships with ASCII diagrams instead of executing code.

What is the best way to investigate problems in a codebase before implementation?▼

The best way to investigate problems before implementation is to use explore mode, which allows you to read files and search code safely while providing prompts and visualizations to track risks without producing executable changes.

Can I use ASCII diagrams to visualize codebase relationships during discovery?▼

Yes, you can generate ASCII diagrams during discovery to visualize codebase relationships. The explore mode reads repository files and maps structural connections to help you investigate problems without writing code.

Does OpenSpec discovery require writing executable code to frame problems?▼

No, OpenSpec-guided discovery explicitly enforces non-implementation. It references existing artifacts and prompts decisions to frame problems without writing executable code or producing functional changes.

What are the limitations of using a thinking partner for requirements discovery?▼

The primary limitation is that explore mode strictly enforces non-implementation, meaning it will never write code or implement features. It is constrained to reading files, searching code, and providing prompts to frame problems safely.

Related Skills

Explore More Product & Management Skills→
linenoizelinenoize
1

recon

Map codebase structure, dependencies, and conventions for downstream agent tasks.

Community
Advanced
open-platform-modelopen-platform-model

openspec-explore

Guide problem exploration and requirement clarification with clarifying questions and ASCII diagrams.

Official
Intermediate
arestivoarestivo

openspec-explore

Explore codebases and clarify requirements without implementing changes.

Community
Advanced
mendixmendix
40

openspec-explore

Guide design discussions by clarifying problems and mapping exploration directions.

Official
Advanced