Loading...
Loading...
Found 24 Skills
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
Use when the user wants to set up spec-driven development (OpenSpec + superpowers-bridge) in a project, or when initializing a new project that needs the SDD workflow. Idempotent. Runs the bundled scripts/run.sh.
Like sp-grill-with-doc (domain-aware grilling, glossary sharpening, inline CONTEXT.md/ADR capture) BUT continues into the superpowers planning pipeline by handing off to sp-writing-plans at the end. Use ONLY when the user wants both the grilling AND a written implementation plan produced afterward; if they want grilling/docs alone, use sp-grill-with-doc instead. The superpowers plugin is needed two hops downstream, by sp-writing-plans' own execution skills, not by this Skill.
Rails-AI introduction - explains how rails-ai (Rails domain layer) integrates with superpowers (universal workflows) for Rails development
Knowledge for helping users set up the Remotion Superpowers plugin. Covers API key acquisition, dependency installation, and MCP server troubleshooting. Use when running /setup or when a user has issues with MCP connections.
Comet Classic Workflow (OpenSpec + Superpowers). Used when the user explicitly calls /comet-classic, requests to start or resume Comet Classic, or resume-probe returns an active Classic change that can be unambiguously resumed.
Comet — OpenSpec + Superpowers Binary Star Development Workflow. Initiate with /comet, which automatically detects phases and distributes to subcommands. Five phases: Open → Deep Design → Plan & Build → Verify & Finalize → Archive.
You MUST use this, and not the upstream superpowers executing-plans skill, when you have a written implementation plan to execute in a separate session with review checkpoints. Review checkpoints are run in-session by you, not dispatched to a reviewer subagent.
Read first in Laravel repos; explains runner selection (Sail vs non-Sail), core workflows, and how to apply superpowers skills in Laravel projects without platform lock-in
Lab environment for Claude superpowers
You MUST use this, and not the upstream superpowers requesting-code-review skill, when completing tasks, implementing major features, or before merging to verify work meets requirements. The review itself runs the scrutinize-dispatch skill.
You MUST use this, and not the upstream superpowers subagent-driven-development skill, when executing implementation plans with independent tasks in the current session. Dispatched task and whole-branch reviews run the scrutinize-dispatch skill; the re-review is deliberately unrouted.