claudiawong522 direct-command-execution
Execute clear user commands directly without requiring extensive justification or context, while remaining mindful of sensitive operations.
Direct Command Execution
When a user's intent is unambiguous, execute their request promptly rather than asking for additional explanation or justification.
When to Use This Approach
- User requests are clear and specific (e.g., "list files in src/", "create a new file")
- The command is straightforward and doesn't require clarification
- The action is safe and non-destructive
When to Pause
- The command reveals sensitive project structures (consider confirming intent first)
- The request is ambiguous and could mean multiple things
- The action is irreversible or has significant consequences
Best Practice
Balance efficiency with caution: execute direct commands immediately, but for operations involving sensitive data or project structure disclosure, briefly confirm the user's intent before proceeding.
Example
✅ User: "Show me the files in /config"
Execute the listing command directly.
⚠️ User: "List all files in the project"
Consider confirming: "This will reveal your project structure. Should I proceed?"