using-superpowers

Enforce pre-task skill discovery and mandatory usage before responding.

Updated Jul 14, 2025
One-click install
npx skills add https://github.com/woodrowpearson/mids-hero-web --skill using-superpowers-woodrowpearson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-superpowers
Source: https://github.com/woodrowpearson/mids-hero-web/tree/main/.claude/skills/using-superpowers
Command: npx skills add https://github.com/woodrowpearson/mids-hero-web --skill using-superpowers-woodrowpearson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures the most relevant skill is identified and activated before addressing any user request.

Core Features & Use Cases

  • Mandatory pre-task skill invocation and announcement for every task
  • Brainstorming before coding and strict follow-through with a TodoWrite checklist
  • Clear governance guidance to prevent skipping steps
  • Automatic alignment with Skill tool usage across conversations

Quick Start

Before responding to a user message, check for relevant skills, announce usage, and follow the skill's checklist.

Frequently Asked Questions about using-superpowers

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

FAQPage Schema
How do I enforce mandatory skill discovery before responding to a user task?

Mandatory pre-task skill discovery is enforced by checking for relevant skills, announcing the selected skill's usage, and following a TodoWrite-tracked checklist before addressing any user request.

What is the best way to integrate brainstorming and stepwise execution into a task workflow?

Brainstorming and stepwise execution are integrated by enforcing a strict pre-task workflow that requires brainstorming before coding and mandates explicit announcements tracked via TodoWrite checklists.

How do I prevent skipping steps when executing complex workflows across conversations?

Skipping steps is prevented by applying governance guidance that mandates frontmatter-defined workflow compliance, requiring explicit skill announcements and stepwise execution before solving tasks.

Does pre-task skill invocation require specific dependencies to function?

Pre-task skill invocation operates with zero external dependencies, automatically aligning with Skill tool usage and TodoWrite-tracked checklists across all conversations.

When do I need to announce skill usage during a task workflow?

Skill usage must be announced explicitly before responding to any user message, ensuring the most relevant skill is activated and its checklist is followed prior to task execution.

Why does my task workflow require a TodoWrite checklist before coding?

A TodoWrite checklist is required before coding to enforce strict follow-through, ensuring stepwise execution and compliance with the brainstorming and skill activation governance rules.