skills.rest
Valynt
ValyntOFFICIAL
Explore all skills by this author →
GitHub

openspec-explore

Guide teams through exploration and requirement clarification without writing code.

Updated Nov 17, 2025
Search Tags:#codebase#requirements#visualization#exploration#diagrams#open-spec#thinking-partner
One-click install
npx skills add https://github.com/Valynt/ValueOS --skill openspec-explore-valynt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/Valynt/ValueOS/tree/main/.windsurf/skills/openspec-explore
Command: npx skills add https://github.com/Valynt/ValueOS --skill openspec-explore-valynt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode to create a thinking partner for exploring ideas, investigating problems, and clarifying requirements. You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If asked to implement something, exit explore mode first and consider creating a change proposal. You MAY create OpenSpec artifacts (proposals, designs, specs) if asked—capturing thinking, not implementing.

Core Features & Use Cases

  • Guided thinking partner that surfaces multiple directions and clarifies requirements.
  • Visualizes ideas with ASCII diagrams and maps to codebase reality.
  • Surface risks, unknowns, and open questions to inform decision-making.
  • Surface artifacts for later capture (proposals, designs) without executing changes.

Quick Start

Say 'start explore' to enter guided exploration mode and begin thinking aloud.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema
How do I clarify software requirements before writing any code?▼

Yes, you can visualize ideas and map them to your codebase using ASCII diagrams during early-stage ideation. The exploration mode enables these visualizations to help teams think through problems and clarify requirements before any implementation begins.

What is the best way to explore a codebase without modifying files?▼

Start guided exploration by typing 'start explore' to enter a thinking partner mode. This initiates a workflow where you can read files, search code, and investigate the codebase to clarify requirements and surface risks without writing code.

Can I generate OpenSpec proposals during the requirements clarification process?▼

Yes, you can optionally generate OpenSpec proposals, designs, and specs during the requirements clarification process. This captures your thinking as artifacts for later reference while the system maintains boundaries against actual feature implementation.

Does this requirements exploration mode allow writing code or implementing features?▼

No, this requirements exploration mode strictly prohibits writing code or implementing features. If you need to implement something, you must exit explore mode first and consider creating a change proposal to transition from ideation to execution.

Related Skills

Explore More Software Engineering Skills→
brandon-setegnbrandon-setegn

openspec-explore

Explore requirements, tradeoffs, and codebase context before implementation.

Community
Intermediate
huangjia2019huangjia2019
114

openspec-apply-change

Automates OpenSpec change application by guiding selection, status checks, and task execution.

Community
Advanced
erichowenserichowens
181

diagramming-expert

Create text-based diagrams using ASCII/Unicode box-drawing characters.

Community
Advanced
marpmemarpme
1

openspec-explore

Explore software ideas and compare options without implementing code.

Community
Intermediate