openspec-explore

Explore architecture and design options by reading repository files and OpenSpec artifacts without writing code.

4|Updated Oct 10, 2025

Search Tags:#design #codebase #requirements #discovery #openspec #brainstorm #explore

Ready to run

npx skills add https://github.com/JanuaryLabs/deepagents --skill openspec-explore-januarylabs

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a dedicated exploratory thinking partner to help teams and individuals clarify requirements, surface tradeoffs, and investigate ideas before any implementation begins, preventing premature commitment to designs or code changes.

Core Features & Use Cases

Open-ended exploration: Ask questions, brainstorm alternatives, and surface hidden assumptions without following a rigid workflow.
Codebase and artifact awareness: Read repository files and OpenSpec change artifacts to ground the discussion in the actual code and existing proposals.
Decision capture guidance: Recommend where to record insights in OpenSpec artifacts (proposals, designs, tasks) without creating changes automatically.
Use Case: A product manager and engineer jointly explore real-time collaboration options, map tradeoffs, and decide whether to open a formal change.

Quick Start

Enter explore mode and help me think through architectural options for adding real-time collaboration without writing or modifying any code.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I brainstorm architecture options and clarify requirements before writing code?▼

To brainstorm architecture and clarify requirements without writing code, use an exploratory thinking partner that reads repository files and OpenSpec artifacts to surface tradeoffs and hidden assumptions before implementation begins.

Can I review OpenSpec change artifacts and investigate my codebase without modifying files?▼

Yes, you can review OpenSpec change artifacts and investigate your codebase through read-only access that enforces a strict prohibition on writing code, ensuring safe exploration of existing proposals without unintended modifications.

What is the best way to explore real-time collaboration design options with my engineering team?▼

Exploring real-time collaboration design options is best handled by mapping tradeoffs and surfacing assumptions in an open-ended discussion, then deciding whether to open a formal change rather than committing prematurely to code.

Does this requirements discovery tool automatically write insights into OpenSpec proposals?▼

No, this requirements discovery tool does not automatically write insights; it recommends where to record decisions in OpenSpec artifacts like proposals, designs, and tasks, leaving the actual creation of changes to you.

When should I not use an exploratory thinking partner for codebase investigation?▼

You should not use an exploratory thinking partner for codebase investigation when you need to perform implementations or make code changes, as it operates strictly in read-only mode and cannot write or modify files.

Do I need the OpenSpec CLI to compare architectural options and review change artifacts?▼

Awareness of the OpenSpec CLI context is required to properly compare architectural options and review change artifacts, as the exploration relies on understanding existing OpenSpec proposals and repository file structures.