openspec-explore

Name: openspec-explore
Availability: InStock
Author: Artagon

Explore ideas and clarify requirements without implementing code changes.

Updated Nov 12, 2025

Search Tags:#design thinking #requirements #exploration #OpenSpec #codebase investigation #tradeoff analysis #non-implementation

Ready to run

npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-explore-artagon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/artagon/artagon-vscode-profiles/tree/main/agents/skills/openspec-explore
Command: npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-explore-artagon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you think through complex software and product decisions before committing to implementation, reducing rework and unclear requirements.

Core Features & Use Cases

Clarify requirements through inquiry: ask emergent clarifying questions, challenge assumptions, and reframe the problem space.
Investigate the codebase for grounded answers: map architecture, find integration points and patterns, and identify hidden complexity.
Compare options and surface tradeoffs: generate structured comparisons, outline risks/unknowns, and recommend directions when asked.
Support safe progression to formal work: flow into a proposal or artifact updates when insights crystallize, without writing application code.

Quick Start

Ask the AI to enter OpenSpec explore mode to investigate the current codebase and clarify requirements for your proposed change.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I explore software design ideas and clarify requirements before writing code?▼

To explore design ideas and clarify requirements before writing code, use a structured thinking partnership to ask emergent clarifying questions, challenge assumptions, and reframe the problem space without implementing changes.

Can I investigate my codebase to map architecture and find integration points without making changes?▼

Yes, you can investigate your codebase to map architecture and find integration points safely. The process grounds your exploration by identifying hidden complexity and patterns while enforcing strict non-implementation guardrails.

What is the best way to compare options and surface tradeoffs for a proposed software change?▼

The best way to compare options and surface tradeoffs is generating structured comparisons that outline risks, unknowns, and open questions, then recommending clear directions only when explicitly requested during your exploration.

How do I create OpenSpec proposals or design artifacts after exploring requirements?▼

You can create OpenSpec proposals or design artifacts after exploring requirements by explicitly requesting them. This supports safe progression to formal work by flowing insights into proposals without writing any application code.

When should I not use a non-implementation approach for codebase investigation?▼

You should not use a non-implementation approach for codebase investigation when you need to directly write or modify application code, as this process strictly enforces guardrails against implementation and focuses only on exploration.

Does OpenSpec explore mode work for mid-change uncertainty and ambiguous ideation?▼

Yes, OpenSpec explore mode works for mid-change uncertainty and ambiguous ideation. It applies structured thinking to surface options, risks, and open questions exactly when you are facing unclear requirements or complex decisions.