task-direction-approval

Require explicit user approval before changing technical direction or implementation strategy.

16|1|Updated Jan 20, 2026

Search Tags:#decision making #change management #risk mitigation #approval #guardrails #task direction

Ready to run

npx skills add https://github.com/kasuken/github-copilot-superpowers --skill task-direction-approval-kasuken

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task-direction-approval
Source: https://github.com/kasuken/github-copilot-superpowers/tree/main/.github/skills/task-direction-approval
Command: npx skills add https://github.com/kasuken/github-copilot-superpowers --skill task-direction-approval-kasuken

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unauthorized or unvetted changes to the original task direction by requiring explicit user approval for significant deviations.

Core Features & Use Cases

Change Control: Ensures that decisions like switching libraries, altering architecture, or opting for manual workarounds are reviewed and approved.
Risk Mitigation: Reduces the risk of unintended consequences from unapproved changes.
Use Case: If the AI suggests replacing a core library due to an error, this skill will pause execution, explain the issue and alternatives, and wait for your go-ahead.

Quick Start

Use the task-direction-approval skill when the AI proposes to switch to a different library.

Frequently Asked Questions about task-direction-approval

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce explicit user consent before the AI alters an original task's technical direction?▼

To enforce explicit user consent for task direction changes, you need a guardrail mechanism that pauses execution to present root causes, alternative options, and trade-offs, waiting for explicit confirmation before proceeding with architectural modifications or library changes.

What is the best way to manage risk mitigation when an AI proposes switching core libraries mid-task?▼

Risk mitigation for library changes requires an approval workflow that intercepts the AI's proposal, clearly articulates the root cause of the error, presents alternative options with trade-offs, and blocks implementation until explicit user approval is granted.

Can I require manual approval before the AI adopts manual workarounds or modifies software architecture?▼

Yes, you can require manual approval for manual workarounds and architectural modifications by using a change control process that forces the AI to explain the deviation and wait for your explicit go-ahead before altering the implementation strategy.

How does change management work when an AI suggests deviating from the original implementation strategy?▼

Change management for implementation strategy deviations works by intercepting the AI's suggestion, halting the current process, displaying the root cause and alternatives with trade-offs, and resuming only after receiving explicit user confirmation.

When do I need an approval guardrail for AI-driven architectural modifications?▼

You need an approval guardrail for architectural modifications whenever an AI attempts to switch libraries, alter core architecture, or adopt manual workarounds, ensuring these significant technical direction changes are vetted to reduce unintended consequences.