explore

Orchestrate iterative research, brainstorming, and prototyping across project scopes.

Updated Aug 27, 2026

Search Tags:#workflow #research #exploration #prototype #scope #brainstorm #epic

Ready to run

npx skills add https://github.com/ian97531/goodplan --skill explore-ian97531

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: explore
Source: https://github.com/ian97531/goodplan/tree/main/skills/explore
Command: npx skills add https://github.com/ian97531/goodplan --skill explore-ian97531

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterative exploration is often needed to clarify unknowns, compare options, and validate approaches before committing to a plan or architecture. The Explore skill provides a structured loop that captures insights across epic, slice, side-quest, and project scopes.

Core Features & Use Cases

Facilitates an open-ended loop of Research, Brainstorm, and Prototype to surface options, trade-offs, and decisions.
Works across Epic, Project, Slice, and Side-Quest scopes, loading appropriate context, determining scope, and recording outcomes.
Supports skip and complete flows, and writes explore-complete.md to preserve a durable record.

Quick Start

Start an exploration with /explore to begin research, brainstorming, or prototyping for the current scope.

Frequently Asked Questions about explore

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

FAQPage Schema

How do I run iterative research and prototyping to clarify project scope and unknowns?▼

Iterative research and prototyping for clarity is orchestrated through a structured loop of brainstorming and validation. This process loads context, determines scope across epic or slice levels, and captures outcomes to compare options before committing to a plan.

What is the best way to brainstorm and compare architectural options before committing to a plan?▼

The best way to compare options is an iterative exploration loop that surfaces trade-offs through research and prototyping. It captures decisions using a structured format, ensuring unknowns are resolved before architecture or planning commitments are made.

How do I document exploration outcomes for an epic or side-quest scope?▼

To document exploration outcomes, the workflow writes durable records like explore-complete.md or explore-skipped.md. This captures brainstorming results and decisions across epic, project, slice, and side-quest scopes for future reference.

Can I use this workflow to determine scope for a specific project slice?▼

Yes, you can determine scope for a project slice by loading the appropriate context. The exploration loop applies across epic, project, slice, and side-quest scopes to clarify unknowns and capture relevant outcomes.

When should I skip an exploration phase during workflow planning?▼

You should skip an exploration phase when unknowns are already resolved and no prototyping is needed. The workflow supports a skip flow that writes an explore-skipped.md file to durable records, documenting the decision to bypass the loop.