sp-commands

name	sp-commands
description	Use when you need to trigger brainstorm, write-plan, or execute-plan workflows via short command shortcuts. These are thin dispatchers that invoke the corresponding sp- skills.
tags	["commands","workflow","shortcuts","dispatchers"]
version	1.0.0
risk	safe
triggers	["/brainstorm","/write-plan","/execute-plan","brainstorm command","write plan command","execute plan command","run brainstorm","run write-plan","run execute-plan"]
requirements	{"cli":[],"env":[]}
upstream_ref	commands/brainstorm.md
author	AlphaComposite
license	MIT
dependencies	["sp-brainstorming","sp-writing-plans","sp-executing-plans"]

Commands (Thin Dispatchers)

Overview

These are thin command wrappers — shortcuts that invoke their corresponding superpowers skills exactly. They contain no logic of their own; they delegate entirely to the target skill.

Core principle: A command is just a named entry point. All behavior lives in the skill.

OpenClaw limitation note: The upstream commands use disable-model-invocation: true, which prevents the agent from generating a response and forces direct skill delegation. OpenClaw has no direct equivalent. Instead, treat each command below as a trigger phrase — when matched, immediately invoke the corresponding skill with no additional output.

Commands

/brainstorm

Upstream: commands/brainstorm.md Invokes: sp-brainstorming

You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores requirements and design before implementation.

Behavior when triggered: Invoke the sp-brainstorming skill and follow it exactly as presented.

---

/write-plan

Upstream: commands/write-plan.md Invokes: sp-writing-plans

Create a detailed implementation plan with bite-sized tasks.

Behavior when triggered: Invoke the sp-writing-plans skill and follow it exactly as presented.

---

/execute-plan

Upstream: commands/execute-plan.md Invokes: sp-executing-plans

Execute the plan in batches with review checkpoints.

Behavior when triggered: Invoke the sp-executing-plans skill and follow it exactly as presented.

---

Usage Pattern

When any of these command triggers is detected:

1. Do not generate a conversational response — act immediately
2. Load the corresponding skill listed above
3. Follow that skill exactly — the command adds nothing beyond delegation

Skill Map

Command	Skill	Purpose
/brainstorm	sp-brainstorming	Explore design before implementation
/write-plan	sp-writing-plans	Create bite-sized implementation plan
/execute-plan	sp-executing-plans	Execute plan in batches with checkpoints

Common Mistakes

• Generating a response before invoking the skill: Don't acknowledge the command — just invoke the skill
• Modifying behavior: These are pass-throughs; add no logic here
• Skipping the skill: The command is meaningless without the skill; always delegate fully