task-direction-approval
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)
More from faulkdev/github-copilot-superpowers
minimalist-surgical-development
Use when editing an existing codebase and the goal is minimal, standard, and non-invasive changes - prioritizes simplest solution, standard libraries first, and surgical modification without unsolicited refactors
34uncertainty-verification
Use when providing exact commands, flags, config keys, file paths, API details, standards, or version-specific behavior - enforces verification via official docs (Context7/web fetch), explicit citations, and bans assumption-based specifics
20investigation-mode
DEPRECATED: See systematic-debugging for current implementation.
14verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
14root-cause-tracing
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
13systematic-debugging
Use when errors are unclear, flaky, or regressions occur; apply a disciplined debugging loop in VS Code Copilot Agent mode.
3