Orchestration prompts
--- name: dispatching-parallel-agents description: Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies --- # Dispatching Parallel Agents ## Overview You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure theySKILL.md
Parallel Agents Skill
Dispatch one subagent per independent failure domain with precisely crafted context (never your session history) and let them work concurrently.
--- name: subagent-driven-development description: Use when executing implementation plans with independent tasks in the current session --- # Subagent-Driven Development Execute plan by dispatching a fresh implementer subagent per task, a task review (spec compliance + code quality) after each, and a broad whole-branch review at the enSKILL.md
Subagent-Driven Development Skill
Execute a plan by dispatching a fresh implementer subagent per task, reviewing each for spec compliance and quality, then a whole-branch final review.
--- name: using-superpowers description: Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions --- <SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific task, ignore this skill. </SUBAGENT-STOP> <EXTREMELY-IMPORTANT>SKILL.md
Using Superpowers Skill
The bootstrap skill that forces skill usage: invoke relevant skills before ANY response, with a red-flags table that closes every rationalization loophole.
--- name: verification-before-completion description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always --- # Verification Before Completion ## Overview **Core pSKILL.md
Verification Before Completion Skill
The gate that forbids 'tests pass', 'fixed', or even 'Done!' without fresh command output proving it: claim-to-evidence table and rationalization counters.
--- name: handoff description: Compact the current conversation into a handoff document for another agent to pick up. argument-hint: "What will the next session be used for?" disable-model-invocation: true --- Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary direcSKILL.md
Handoff Skill
Compact the current conversation into a redacted handoff document a fresh agent can pick up: the bridge between context windows, in either direction.