sp-commands

Dispatch trigger phrases to sp-skills for brainstorming, planning, and execution tasks.

4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/AlphaComposite/openclaw-superpowers-port --skill sp-commands
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sp-commands
Source: https://github.com/AlphaComposite/openclaw-superpowers-port/tree/main/skills/sp-commands
Command: npx skills add https://github.com/AlphaComposite/openclaw-superpowers-port --skill sp-commands

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thin command wrappers that delegate to their corresponding sp- skills, enabling quick, deterministic access to complex workflows without adding logic of their own.

Core Features & Use Cases

  • Thin dispatchers that invoke target skills exactly as defined upstream.
  • Trigger phrases like /brainstorm, /write-plan, /execute-plan instantly route to sp-brainstorming, sp-writing-plans, and sp-executing-plans.
  • Use Case: Orchestrate prompt-engineering sessions by chaining brainstorming, planning, and execution with a single command.

Quick Start

Invoke the corresponding sp-brainstorming, sp-writing-plans, or sp-executing-plans skill immediately when a trigger is detected such as /brainstorm, /write-plan, or /execute-plan.

Frequently Asked Questions about sp-commands

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

FAQPage Schema
How do I quickly trigger brainstorm and planning workflows during prompt engineering?

You can trigger brainstorm and planning workflows instantly using short command dispatchers like /brainstorm or /write-plan, which directly route your prompt to the corresponding target skills without intermediate reasoning.

Can I use shortcuts to chain brainstorming, planning, and execution tasks together?

Yes, you can orchestrate prompt engineering sessions by chaining workflows together, using trigger phrases like /brainstorm, /write-plan, and /execute-plan to sequentially invoke the corresponding target skills.

What is the best way to invoke execution plans without adding intermediate logic?

The best way to invoke execution plans without intermediate logic is using thin command wrappers, such as the /execute-plan trigger, which deterministically delegates to the exact upstream execution skill.

Do I need any specific dependencies or components to use these command dispatchers?

No specific dependencies or components are required, as these are thin command wrappers that simply map trigger phrases to their corresponding target skills and perform no internal processing themselves.

Why do these shortcuts not process any logic internally during prompt engineering?

These shortcuts do not process logic internally because they act as thin dispatchers designed to delegate exactly as defined upstream, ensuring quick and deterministic access to complex workflows without adding their own logic.