using-superpowers

To stop premature replies, enforce a mandatory pre-response skill invocation workflow that checks for skill relevance before generating any answer. This workflow requires the assistant to invoke the Skill tool first, ensuring structured guidance applies to planning, brainstorming, or debugging tasks.

Workflow guardrails for prompt governance are structured rules that define instruction priority between user inputs, skills, and system prompts. They provide red-flag rationalization patterns to stop and re-check skill applicability, preventing the assistant from bypassing mandatory pre-response checks.

Yes, this mandatory skill invocation approach provides platform-agnostic guidance. It explains how to invoke skills across Claude Code, Copilot CLI, and Gemini CLI using platform-specific tool mapping while maintaining consistent instruction priority and workflow guardrails.

You need to enforce a pre-response skill check on any conversation turn where there is even a 1% chance a skill should guide the interaction. This applies to planning, brainstorming, debugging, or implementation approach tasks to prevent rationalization and ensure proper assistant orchestration.

To map tool invocations correctly, follow the platform-specific tool mapping defined in the workflow guardrails. This ensures the Skill tool is invoked before any response or action across Claude Code, Copilot CLI, and Gemini CLI according to established priority rules and instruction overrides.