Skill

explore

Phase 1 of the development workflow. Explore the codebase using subagents WITHOUT making changes. Produces an exploration report. Use before planning complex changes.

Install

npx claudepluginhub artmin96/forge-studio --plugin workflow

Tool Access

This skill is limited to using the following tools:

ReadGlobGrepBash

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.8k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-help

Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Process

Given the task in $ARGUMENTS:

Find relevant code: Use Glob/Grep to locate files related to the task

Read key files: Understand the current implementation

Trace dependencies: What calls what? What depends on this?

Identify patterns: How does the codebase handle similar things?

Check tests: Do tests exist for this area? What do they cover?

Output: Exploration Report

EXPLORATION REPORT ================== Task: [what was explored] Relevant Files: - path/to/file.ext — [what it does, why it matters] - path/to/other.ext — [what it does, why it matters] Current Behavior: [How the code currently works, in 2-3 sentences] Existing Patterns: [How the codebase handles similar things — naming, structure, approach] Dependencies: [What other code depends on this, or what this depends on] Test Coverage: [Do tests exist? What do they cover? What's missing?] Gotchas: [Anything surprising, non-obvious, or risky discovered during exploration]

Keep the report under 300 tokens. The main session needs the signal, not the noise. Do NOT make any changes. Read only.

Explore: Understand Before Changing

Phase 1 of the Explore → Plan → Implement → Verify workflow. Runs in a fork context so exploration doesn't pollute the main session.

Process

Given the task in $ARGUMENTS:

Find relevant code: Use Glob/Grep to locate files related to the task
Read key files: Understand the current implementation
Trace dependencies: What calls what? What depends on this?
Identify patterns: How does the codebase handle similar things?
Check tests: Do tests exist for this area? What do they cover?

Output: Exploration Report

EXPLORATION REPORT
==================
Task: [what was explored]

Relevant Files:
- path/to/file.ext — [what it does, why it matters]
- path/to/other.ext — [what it does, why it matters]

Current Behavior:
[How the code currently works, in 2-3 sentences]

Existing Patterns:
[How the codebase handles similar things — naming, structure, approach]

Dependencies:
[What other code depends on this, or what this depends on]

Test Coverage:
[Do tests exist? What do they cover? What's missing?]

Gotchas:
[Anything surprising, non-obvious, or risky discovered during exploration]

Keep the report under 300 tokens. The main session needs the signal, not the noise. Do NOT make any changes. Read only.