القائمة
Slash command dispatcher for Superpowers skills. Detects /superpowers-skill-name syntax and loads the appropriate skill without conflicting with existing Hermes skills.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
| name | superpowers-slash-commands |
| description | Slash command dispatcher for Superpowers skills. Detects /superpowers-skill-name syntax and loads the appropriate skill without conflicting with existing Hermes skills. |
This skill detects and dispatches /superpowers-skill-name commands to load Superpowers skills with proper namespacing.
/superpowers-<skill-name>
/superpowers-brainstorming - Turn ideas into fully formed designs/superpowers-writing-plans - Create detailed implementation plans/superpowers-systematic-debugging - 4-phase root cause debugging/superpowers-test-driven-development - RED-GREEN-REFACTOR TDD cycle/superpowers-subagent-driven-development - Fast iteration with two-stage review/superpowers-requesting-code-review - Pre-review checklist/superpowers-receiving-code-review - Responding to feedback/superpowers-executing-plans - Batch execution with checkpoints/superpowers-dispatching-parallel-agents - Concurrent subagent workflows/superpowers-using-git-worktrees - Parallel development branches/superpowers-finishing-a-development-branch - Merge/PR decision workflow/superpowers-verification-before-completion - Ensure it's actually fixed/superpowers-writing-skills - Create new skills following best practices/superpowers-using-superpowers - Introduction to the skills systemWhen you use a /superpowers- command:
superpowers-<skill-name> skill/plan vs /superpowers-writing-plans)Just type the command naturally in conversation:
/superpowers-brainstorming I want to build a feature for tracking user engagement
/superpowers-debugging This test is failing intermittently
/superpowers-writing-plans Create an implementation plan for the search feature
This skill serves as a dispatcher. When a /superpowers- command is detected:
/superpowers-brainstorming → brainstorming)superpowers-{skill_name}skill_view(name="superpowers-{skill_name}")When the command /superpowers-<skill-name> is detected, use:
skill_view(name="superpowers-{skill-name}")
For example:
/superpowers-brainstorming → skill_view(name="superpowers-brainstorming")/superpowers-writing-plans → skill_view(name="superpowers-writing-plans")/superpowers-test-driven-development → skill_view(name="superpowers-test-driven-development")All Superpowers skills are prefixed with superpowers- to:
test-driven-development vs superpowers-test-driven-development)