openspec-explore

Guide open-ended ideation and requirement clarification with prompts and ASCII diagrams.

1|Updated Jan 21, 2026

Search Tags:#design #codebase #requirements #guidance #OpenSpec #explore #thinking-partner

Ready to run

npx skills add https://github.com/durandom/layton --skill openspec-explore-durandom

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams explore ideas and clarify requirements by acting as a thinking partner, enabling deep analysis before committing to changes.

Core Features & Use Cases

Guided exploration: a thinking partner that surfaces questions, alternatives, and potential assumptions.
Visual thinking tools: ASCII diagrams and structured prompts to map ideas and dependencies.
Open-ended framing: supports exploration across problem space, design decisions, and requirements refinement.

Quick Start

Tell me to enter explore mode and start thinking aloud about your 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 and clarify project requirements before writing code?▼

To explore and clarify project requirements, you can use a thinking partner to surface questions, alternatives, and potential assumptions during early problem framing. This approach helps map ideas and dependencies before committing to changes.

What is the best way to map out design decisions and dependencies during early problem framing?▼

The best way to map design decisions and dependencies is by using visual thinking tools like ASCII diagrams and structured prompts. These tools help facilitate deep analysis and map ideas across the problem space during open-ended exploration.

Can I use a thinking partner to analyze assumptions without executing code?▼

Yes, you can use a thinking partner to analyze assumptions without executing code. The tool strictly supports open-ended thinking, requirements refinement, and ideation while avoiding any code execution or implementation.

How do I start an ideation session for requirement clarification?▼

You start an ideation session for requirement clarification by entering explore mode and thinking aloud about your idea. The thinking partner then guides the process by surfacing questions, alternatives, and potential assumptions.

When should I avoid using a thinking partner for software design discussions?▼

You should avoid using a thinking partner for software design discussions when you need actual code execution, implementation, or finalized answers. The tool is strictly for open-ended exploration, requirement refinement, and deep analysis before committing to changes.