using-superpowers

To enforce skill activation before a response, you need a mandatory skill checking mechanism that forces the assistant to review applicable workflows and prioritize the correct process before generating any output. This ensures the assistant adheres to loaded instructions first.

The best way to prioritize coding workflows is to apply process prioritization before execution, which helps identify whether brainstorming, debugging, or implementation skills are required. This prevents jumping into execution with the wrong process and producing unreliable results.

Yes, skill activation and tool mappings differ across Claude Code, Copilot CLI, Gemini CLI, and Codex. Platform-specific guidance is required to ensure the assistant invokes the correct tool conventions and handles priorities accurately on each platform.

Your assistant skips applicable workflows because it lacks mandatory pre-response skill discovery. Without strict priority handling to check for relevant skills first, the assistant answers immediately, causing missed workflows and inconsistent behavior during planning or tool-driven tasks.

You need to check for applicable skills whenever there is even a small chance a workflow applies, especially during planning, debugging, implementation, and tool-driven tasks. Checking first ensures the correct process is followed before clarifying or acting.