explore

Explore project context, ask clarifying questions, and propose approaches with trade-offs.

5|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/jstoup111/ai-conductor --skill explore-jstoup111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore
Source: https://github.com/jstoup111/ai-conductor/tree/main/skills/explore
Command: npx skills add https://github.com/jstoup111/ai-conductor --skill explore-jstoup111

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill assists in the initial phase of feature development by exploring the context, asking clarifying questions, proposing approaches with trade-offs, and deciding whether the work should be classified as product or technical.

Core Features & Use Cases

  • Exploration and Contextual Analysis: Gathers and analyzes project context to understand the scope and requirements.
  • Question-Driven Insight: Asks clarifying questions one at a time to refine understanding and ensure comprehensive coverage.
  • Approach Proposal: Proposes 2-3 approaches with clear trade-offs and makes a recommendation for the user to decide.
  • Work Track Decision: Classifies the work as product or technical, with the operator's confirmation to gate PRD creation.
  • Persistence of Decision: Stores the chosen approach and rationale for its selection for future reference.

Quick Start

To begin the exploration process, initiate the 'explore' skill.

Frequently Asked Questions about explore

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

FAQPage Schema
How do I decide whether a new feature should be tracked as product or technical work?

Feature track decisions are made by exploring project context, asking clarifying questions, and classifying the work as product or technical with operator confirmation to gate PRD creation.

What's the best way to evaluate approaches and trade-offs during project planning?

Evaluating approaches during project planning involves gathering context, asking clarifying questions one at a time, and proposing 2-3 approaches with clear trade-offs and a recommendation for the user to decide.

When do I need context analysis for feature development?

Context analysis for feature development is needed at the initial phase to understand scope and requirements, ensuring the correct work track and development approach are chosen before proceeding.

How do I start the exploration process for a new feature?

Start the exploration process by initiating the skill, which then gathers project context, asks clarifying questions sequentially, and proposes approaches with trade-offs for your decision.

Can I store the chosen development approach and rationale for future reference?

Yes, the chosen approach and the rationale for its selection are persisted as part of the decision-making process, storing the work track classification and approach details for future reference.