openspec-explore

Guide early-stage idea exploration and requirement framing without executing code.

4|Updated Feb 2, 2026

Search Tags:#codebase #requirements #visualization #OpenSpec #brainstorm #explore #thinking-partner

Ready to run

npx skills add https://github.com/jaxxstorm/landlord --skill openspec-explore-jaxxstorm

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a guided thinking partner to help users explore ideas, investigate problems, and clarify requirements before implementing changes.

Core Features & Use Cases

Exploratory thinking: Facilitate problem-space exploration, question surfacing, and requirement framing.
Non-implementation stance: Remain a thinking partner, not a coder or executor, and avoid writing or running code.
OpenSpec artifact support: When asked, it can propose OpenSpec artifacts (proposals, designs, specs) to capture reasoning and decisions.

Quick Start

Start an exploration session by invoking the openspec-explore stance and begin brainstorming. You may read files and examine the codebase to inform thinking, but you must not implement features or write code.

Frequently Asked Questions about openspec-explore

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

FAQPage Schema

How do I clarify requirements before starting codebase implementation?▼

To clarify requirements before implementation, you can use a guided thinking partner to explore the problem space, surface questions, and frame specifications without writing code. This approach helps structure early-stage requirement iteration and brainstorming.

What is the best way to brainstorm and explore problem-space ideas for a new feature?▼

Brainstorming problem-space ideas is best done with a non-implementation thinking partner that investigates problems and frames requirements. This allows you to map out decisions and iterate on concepts before any actual development begins.

Can I generate OpenSpec artifacts during early-stage requirement planning?▼

Yes, you can generate OpenSpec artifacts during requirement planning. When explicitly requested, the exploration session can propose designs, specs, and proposals to capture the reasoning and decisions derived from your brainstorming.

Does this requirements exploration approach require any dependencies or installation?▼

No dependencies or installation are required for this requirements exploration approach. It functions purely as a guided thinking partner that reads files to inform thinking but strictly avoids executing code or implementing features.

Why use a thinking partner instead of directly coding an initial solution?▼

Using a thinking partner instead of directly coding ensures thorough problem-space exploration before commitment. It maintains a non-implementation stance to help frame requirements clearly, preventing premature development and capturing design rationale.

When should I not use an exploratory thinking partner for my project?▼

You should not use an exploratory thinking partner when your project requires immediate code execution or feature implementation. It strictly avoids writing or running code, focusing solely on requirement framing and early-stage idea exploration.