exploration-phase

Clarify goals and analyze codebases before implementation.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/nesihaver-IL/MyFirstRepo --skill exploration-phase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exploration-phase
Source: https://github.com/nesihaver-IL/MyFirstRepo/tree/main/.claude/skills/exploration-phase
Command: npx skills add https://github.com/nesihaver-IL/MyFirstRepo --skill exploration-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps AI clarify goals and understand a task before starting implementation.

Core Features & Use Cases

  • Requirement Clarification: Elicits goals, success criteria, and scope to prevent scope creep.
  • Codebase Analysis: Examines the repository structure and relevant files to map dependencies.
  • Technical Discovery & Question Generation: Identifies constraints, risks, and necessary questions to guide planning.
  • Use Case: When starting a feature or refactoring in unfamiliar code, use this phase to reduce ambiguity and plan effectively.

Quick Start

Invoke the exploration phase: /exploration-phase Or describe what you need to explore: "I need to add user authentication, but first let me understand the current setup"

Frequently Asked Questions about exploration-phase

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

FAQPage Schema
How do I clarify requirements before coding a new feature?

To clarify requirements before coding, you must elicit goals, success criteria, and scope to prevent scope creep. This structured requirement gathering process reduces ambiguity and maps dependencies for effective feature planning.

What is the best way to analyze an unfamiliar codebase before refactoring?

The best way to analyze an unfamiliar codebase is by examining repository structure and relevant files to map dependencies. This technical discovery process identifies constraints and risks to guide your refactoring plan.

How do I plan architecture when project context is unclear?

To plan architecture with unclear context, use technical discovery and question generation to identify constraints and risks. This structured requirement gathering maps dependencies and guides plan creation effectively.

When should I use an exploration phase for software development?

Use an exploration phase when starting new features, debugging unfamiliar code, or planning architecture with unclear context. It reduces ambiguity by mapping dependencies and generating technical questions before implementation.

Does requirement gathering help prevent scope creep in codebase analysis?

Requirement gathering prevents scope creep by eliciting clear goals, success criteria, and scope early. When combined with codebase analysis, it ensures technical discovery and planning stay within defined project boundaries.

Related Skills