Task Direction Approval

Overview

This skill prevents unauthorized direction changes by forcing explicit user consent before deviating from the original requirements.

Use when...

• Switching from the original tech/library to alternatives

• Replacing an automated approach with a manual workaround

• Changing architecture or design patterns

• Delivering different results than requested

Symptoms / keywords

• “can’t use X”, “let’s switch to Y”, “workaround”, “manual”, “different approach”, “alternative library”, “rewrite”, “change architecture”

Communication protocol (template)

❌ Wrong Response:

"GraphQL Codegen failed, so I'll define types manually instead."

✅ Correct Response:

"GraphQL Codegen failed due to authentication error. Options available:

• Add authentication headers

• Try different endpoint

• Download schema file directly Which approach would you prefer?"

Minimal workflow

• Explain the failure root cause clearly (what failed, why it failed, evidence).

• Present 2-3 viable options with trade-offs (speed, risk, maintenance, correctness).

• Ask for explicit user choice.

• Only proceed after approval.

Notes

• Use investigation-mode when there are repeated failures or the situation is unclear.