explore

Conducts interview-driven discovery to frame problems and evaluate solution options before specification.

Updated May 26, 2026
One-click install
npx skills add https://github.com/robot-denny/ai-sketchlab --skill explore-robot-denny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore
Source: https://github.com/robot-denny/ai-sketchlab/tree/main/.agents/skills/explore
Command: npx skills add https://github.com/robot-denny/ai-sketchlab --skill explore-robot-denny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight to building before properly framing the problem or weighing alternatives, leading to wasted effort on the wrong solution. This Skill runs a structured discovery interview that widens the option space, stress-tests candidate solutions, and captures the reasoning in a discovery document before any code is written. ## Core Features & Use Cases - Structured Discovery Interview: Asks one question at a time across framing, option generation, and second-order effect phases, withholding recommendations during framing and offering them during evaluation. - Calibrated Depth: Scales between a lightweight pass for single-feature choices and a heavyweight exploration for large feature sets or subsystems. - Discovery Summary Output: Writes a lean discovery.md document that feeds directly into the /spec step of the spec → plan → implement workflow. - Use Case: A team is unsure whether to add caching at the application or database layer. Run explore to frame the actual pain, generate both options plus alternatives, probe trade-offs and knock-on effects, and hand a decision-ready summary to /spec. ## Quick Start Ask the AI to run the explore skill on the problem or feature you want to investigate, then answer its questions one at a time.

Frequently Asked Questions about explore

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

FAQPage Schema
How do I run a discovery phase before writing a spec?

Invoke the explore skill with the problem or feature you want to investigate. It interviews you one question at a time through framing, option evaluation, and second-order effects, then writes a discovery.md summary that the /spec step reads directly.

What is the difference between explore and spec in this workflow?

Explore runs before any decision is made and widens the option space by weighing multiple candidate solutions. Spec comes after, converging on the chosen direction and defining it precisely. Explore outputs a discovery document; spec consumes it.

When should I use lightweight versus heavyweight discovery?

Use lightweight discovery when weighing a couple of implementation approaches for a single feature. Use heavyweight discovery for large feature sets or whole subsystems with many moving pieces. The skill asks one calibration question at the start to confirm the depth.

Does the explore skill write code or create branches?

No. Explore never writes code, designs implementations, or creates branches. Its only output is a discovery.md document on the current branch, which you commit before running /spec with the same slug.

Why does explore withhold recommendations during problem framing?

Withholding recommendations during framing prevents the team from rubber-stamping the AI's assumptions instead of articulating their own understanding. Recommendations are only offered later, during option evaluation, where reacting to a concrete stance sharpens thinking.