openspec-explore

Guide design discussions by clarifying problems and mapping exploration directions.

40|84|Updated Oct 4, 2022
One-click install
npx skills add https://github.com/mendix/web-widgets --skill openspec-explore-mendix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-explore
Source: https://github.com/mendix/web-widgets/tree/main/.agents/skills/openspec-explore
Command: npx skills add https://github.com/mendix/web-widgets --skill openspec-explore-mendix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill provides a thinking partner to help users think through ideas, clarify requirements, and explore problems without implementing code.

Core Features & Use Cases

  • Guided exploration prompts and stance variety to stimulate thinking.
  • Codebase-oriented reasoning: read files, search context, and map problem spaces.
  • OpenSpec artifact facilitation: surface risks, identify questions, and visualize options for decision making.

Quick Start

Begin an exploration by outlining your problem and inviting the user to choose a direction for deeper thinking.

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 and frame problems before writing code?

A guided exploration partner helps clarify requirements by surfacing assumptions and mapping exploration directions during early-stage problem framing. It applies codebase analysis and design-thinking to visualize options without writing implementation code.

What is the best way to visualize brainstorming options for design decisions?

Visual brainstorming for design decisions is facilitated through OpenSpec artifact creation that surfaces risks, identifies questions, and maps problem spaces. Guided exploration prompts stimulate thinking and visualize options without writing code.

Can I investigate a codebase and map problem spaces without implementing code?

Yes, codebase investigation is supported through codebase-oriented reasoning that reads files, searches context, and maps problem spaces. This maintains a thinking-only stance to explore problems without writing any implementation code.

Does guided exploration help with early-stage requirement discovery and risk identification?

Guided exploration directly supports early-stage requirement discovery by surfacing assumptions and identifying questions to clarify problems. It applies stance variety to stimulate thinking and facilitates OpenSpec artifacts to surface risks for decision making.

How do I start an exploration session for problem framing and design discussions?

Start an exploration session by outlining your problem and inviting the guided partner to choose a direction for deeper thinking. This initiates a thinking-only process that applies design-thinking to explore requirements and visualize options.

When should I avoid using a thinking-only stance for requirement discovery?

A thinking-only stance should be avoided when your design discussions require actual code implementation, as this exploration partner focuses on problem framing, OpenSpec artifact creation, and visual brainstorming without writing code.