# Explore Before Acting

> explore-before-acting

- Skill: `claudiawong522/explore-before-acting` (Agent Skill)
- Install (CLI): `npx skillmds@latest add claudiawong522/explore-before-acting`
- Raw SKILL.md: https://api.skillmd.com/api/skills/claudiawong522/explore-before-acting/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: claudiawong522 (https://skillmd.com/u/claudiawong522)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/claudiawong522/explore-before-acting

---

# explore-before-acting

Systematically explore and document your target environment's structure and documentation before executing commands or awaiting further instructions.

## Overview
Before diving into tasks or executing commands in an unfamiliar environment, invest time in understanding the system architecture, available tools, and project structure. This upfront exploration enables better decision-making and prevents missteps.

## Steps

1. **Navigate to the root or main project directory**
   - Identify the entry point of the environment you're working with

2. **Search for and read documentation files**
   - Look for: `README.md`, `CLAUDE.md`, `ARCHITECTURE.md`, `.md` files, or similar
   - These files typically explain the system's purpose, structure, and available tools

3. **Explore the directory structure**
   - List subdirectories and their contents
   - Identify key folders: source code, documentation, config, tests, etc.
   - Understand the organizational hierarchy

4. **Document your findings**
   - Note the system's purpose and main components
   - List available tools, commands, or APIs
   - Identify any setup requirements or dependencies
   - Record the location of important files

5. **Await or plan your next steps**
   - You now have informed context for decision-making
   - Follow instructions with better understanding, or proactively suggest approaches based on the architecture you've discovered

## Tips
- Many projects include hidden gems in documentation files—don't skip this step
- Use `ls -la` or file tree commands to see all contents including hidden files
- Pay special attention to any files named after the project or system (they often contain crucial information)
- This exploration typically takes 2-5 minutes but saves significantly more time later