Establish Baseline Context

establish-baseline-context

Discover available resources and confirm readiness before proceeding with vague or open-ended instructions.

Establish Baseline Context

When given vague instructions or asked to "await further instructions," don't sit idle. Instead, proactively establish baseline context by understanding what you're working with.

Steps

1. Explore the codebase structure - Map out the project layout, key files, and existing code patterns
2. Identify available resources - Document tools, libraries, APIs, and dependencies at your disposal
3. Confirm readiness - Verify you have what you need and understand the current state
4. Document findings - Summarize what you've discovered for future reference

Tips

• This approach works especially well when instructions are vague, incomplete, or explicitly tell you to wait
• By establishing context first, you'll be ready to act immediately when more specific directions arrive
• Your exploration also helps clarify ambiguous requirements and surface potential blockers early
• Share your findings with the user—they may refine instructions based on what you've discovered

Example Scenario

Instead of waiting passively when told "we'll provide more instructions later," you might:

• Review the project's README and architecture docs
• Examine the existing codebase structure and naming conventions
• List available tools and libraries
• Identify any missing dependencies or setup requirements
• Provide a summary of findings and ask clarifying questions

This positions you to move quickly once you receive specific tasking.