openspec-explore

Explore concepts and clarify requirements using OpenSpec CLI artifacts.

Updated Apr 22, 2026

Search Tags:#requirements #exploration #system architecture #change management #OpenSpec

Ready to run

npx skills add https://github.com/aditrioka/nearyou-id --skill openspec-explore-aditrioka

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/aditrioka/nearyou-id/tree/main/.claude/skills/openspec-explore
Command: npx skills add https://github.com/aditrioka/nearyou-id --skill openspec-explore-aditrioka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill aids in exploring ideas, investigating problems, and clarifying requirements without implementation. It serves as a thinking partner for conceptualizing changes and understanding system architectures.

Core Features & Use Cases

Exploration Mode: Think deeply and visualize concepts without implementing code.
Codebase Investigation: Map architecture, find integration points, and surface hidden complexity.
Options Comparison: Create tradeoff tables and recommend paths based on constraints.
Risk Identification: Surface potential risks and unknowns for better planning.

Quick Start

Enter explore mode with the command: "explore my new feature idea"

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I explore system architecture and clarify requirements before writing code?▼

Requirements exploration before implementation is handled by acting as a thinking partner to conceptualize changes and map system architecture. You can visualize concepts, investigate codebases, and surface hidden complexity without committing to actual code implementation.

What's the best way to compare architectural options and identify risks during system design?▼

Comparing architectural options during system design is done by generating tradeoff tables and recommending paths based on your project constraints. This process simultaneously surfaces potential risks and unknowns, providing better planning context before you begin building.

Do I need the OpenSpec CLI to generate visual diagrams and artifacts for conceptual exploration?▼

Yes, the OpenSpec CLI is required to create and manipulate OpenSpec artifacts. The exploration process relies on this dependency to generate the visual diagrams and structured outputs needed for deep conceptual analysis.

Can I use this approach to map integration points across an existing codebase?▼

Mapping integration points across an existing codebase is a core function of this exploration approach. It investigates your current architecture to find connection points and surface hidden complexity, helping you understand the system before making changes.

When should I not use requirements exploration and ideation tools?▼

Requirements exploration tools should not be used when you are ready to write or deploy actual code, as this process is strictly designed for pre-implementation ideation. It focuses entirely on conceptualizing changes and understanding systems rather than executing implementation tasks.