# Confirm Execution Readiness

> confirm-execution-readiness

- Skill: `claudiawong522/confirm-execution-readiness` (Agent Skill)
- Install (CLI): `npx skillmds@latest add claudiawong522/confirm-execution-readiness`
- Raw SKILL.md: https://api.skillmd.com/api/skills/claudiawong522/confirm-execution-readiness/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/confirm-execution-readiness

---

# confirm-execution-readiness

Verify command execution success and confirm readiness status before proceeding with further instructions.

# Confirm Execution and Readiness

Always confirm that commands have executed successfully and that your environment is in the expected state before awaiting or accepting new instructions.

## Why This Matters
- **Session State**: Ensures Claude Code knows the actual state of your environment, not an assumed one
- **Error Prevention**: Catches issues early before they cascade into subsequent operations
- **Clarity**: Makes it explicit when a task is complete and ready for the next step

## Steps
1. Execute your command or operation
2. Verify the output indicates success (exit code 0, expected files/output present, etc.)
3. Briefly confirm the current state or readiness (e.g., "Environment initialized and ready for next steps")
4. Only then proceed to await further instructions

## Example
```
I'll initialize the project structure by listing the directory contents.

[executes: ls -la]

✓ Directory listing complete. Project files are accessible and environment is ready for development.
```

## Tips
- Don't assume success—always check the actual output
- Explicitly state what you've confirmed (files created, services running, dependencies installed, etc.)
- Keep confirmations brief but specific
- This pattern is especially important after setup, initialization, or environment changes