using-superpowers

Mandatory pre-response skill checks ensure the correct skill is activated before debugging or planning. This workflow-control mechanism requires identifying applicable skills and loading them before processing any query to prevent workflow omissions.

Cross-platform tool mapping provides the best way to map tools across different coding assistants like Gemini CLI and Copilot CLI. It establishes tool correspondence relationships to reduce migration costs and ensure consistent workflow control across environments.

Yes, this workflow control method supports building MCP tools and writing technical documentation. It applies mandatory pre-response skill checks across planning, debugging, documentation, code review, and MCP building tasks to ensure correct domain-specific skills are loaded.

You need to check for applicable skills before starting a code review to avoid the "act first, think later" problem. Pre-response skill discovery ensures instruction-priority handling and prevents ignoring platform differences or misusing tools during the review process.

Yes, you can use this skill activation workflow with Hermes, Qoder, and Pi platforms. The cross-platform tool mapping explicitly supports Claude Code, Copilot CLI, Hermes, Gemini CLI, Qoder, and Pi for consistent workflow control.

To handle overlapping domain-specific skills when entering plan mode, the workflow processes skills by priority. It distinguishes between workflow skills and implementation skills, activating them in the correct sequence to prevent conflicts during complex development flows.