Verify Prerequisites

verify-prerequisites

Verify all task prerequisites are met and clarify scope boundaries before starting implementation.

Verify Prerequisites Before Implementation

This skill helps you avoid incomplete deliverables by confirming prerequisites and scope upfront.

When to Use This Skill

• Before starting any implementation task
• When requirements seem ambiguous or incomplete
• When a task might depend on other work or external factors
• At the beginning of configuration, code changes, or deployments

Steps

1. List all prerequisites - Identify what must be true or available before you can complete the task:

   • Required tools, libraries, or systems
   • Dependent tasks that must complete first
   • Access permissions or credentials needed
   • Existing code or configurations to build upon

2. Verify each prerequisite - Confirm with the user or check yourself:

   • Do these tools/systems exist and are accessible?
   • Are dependent tasks actually complete?
   • Are all permissions granted?
   • Is the foundation in place?

3. Clarify scope boundaries - Explicitly ask about what's included and excluded:

   • Does this task include testing? Deployment? Documentation?
   • What happens after implementation is done?
   • Are there environment-specific considerations (dev, staging, prod)?
   • What's the success criteria?

4. Document agreements - Summarize your understanding back to the user before proceeding

5. Proceed only when confirmed - Start implementation only after prerequisites are verified and scope is clear

Tips

• Frame prerequisite checks as clarification questions, not obstacles
• Ask "What happens next?" to uncover hidden scope items
• Always explicitly confirm testing/deployment scope for technical changes
• Document decisions to prevent scope creep during implementation