openspec-explore

Name: openspec-explore
Availability: InStock
Author: aniwei

Explore ideas and clarify requirements without implementing code changes.

Updated Feb 3, 2026

Search Tags:#codebase #requirements #problem-solving #exploration #OpenSpec #thinking-partner

Ready to run

npx skills add https://github.com/aniwei/vitamin-code --skill openspec-explore-aniwei

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/aniwei/vitamin-code/tree/main/refs/opencode/.github/skills/openspec-explore
Command: npx skills add https://github.com/aniwei/vitamin-code --skill openspec-explore-aniwei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a thinking partner to help teams explore ideas, investigate problems, and clarify requirements without implementing changes.

Core Features & Use Cases

Guided ideation and problem framing to surface assumptions and alternative approaches.
Codebase reading, architecture visualization, and collaborative reasoning without writing or applying changes.
OpenSpec artifact guidance to capture proposals, designs, or specs when requested, ensuring thinking is documented rather than implemented.

Quick Start

Enter explore mode and begin thinking through the requirements for your project. You may ask questions, request diagrams, or propose OpenSpec artifacts, but you must not write or apply code.

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 production code?▼

To explore ideas and clarify requirements without writing production code, use a thinking partner approach for guided ideation, problem framing, and collaborative reasoning to surface assumptions and alternative directions.

What is the best way to frame problems and visualize architecture during early discovery?▼

The best way to frame problems and visualize architecture during early discovery is through collaborative reasoning sessions that read codebases and surface multiple directions, ensuring your thinking is documented rather than implemented.

Can I create OpenSpec proposals and designs without applying changes to my codebase?▼

Yes, you can create OpenSpec proposals, designs, and specs to document your thinking without applying changes, as the exploration process operates within OpenSpec contexts and requires no code execution.

Does this requirements exploration approach work without executing code?▼

Yes, this requirements exploration approach works entirely without executing code, acting strictly as a thinking partner to investigate problems, read codebases, and refine requirements while must not write or apply production changes.

When should I not use a thinking partner for codebase exploration?▼

You should not use a thinking partner for codebase exploration when you need to implement changes, write code, or apply production updates, as its sole purpose is early discovery, problem framing, and requirements refinement.

How do I start an OpenSpec requirements refinement session?▼

To start an OpenSpec requirements refinement session, enter explore mode and begin thinking through your project requirements by asking questions, requesting architecture diagrams, or proposing OpenSpec artifacts without writing code.