using-superpowers

Route intents to subagents via slice-agent-harness and validate SLICE-compliant outputs.

1|Updated Jan 5, 2023
One-click install
npx skills add https://github.com/riez/dots --skill using-superpowers-riez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-superpowers
Source: https://github.com/riez/dots/tree/main/.config/agentic/skills/using-superpowers
Command: npx skills add https://github.com/riez/dots --skill using-superpowers-riez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a reliable orchestration layer that ensures the correct skill is located and invoked before any user-facing response, including clarifying questions.

Core Features & Use Cases

  • Mandatory pre-dispatch: Always run the slice-agent-harness before dispatching any subagent to route to the appropriate explorer/researcher.
  • Routing table guidance: Encodes intent-to-subagent mappings (e.g., code-explorer for code questions, ux-researcher for UX questions).
  • Output validation: Enforces SLICE-compliant outputs and checks that all requested items are returned before summarizing to the user.

Quick Start

Always invoke the slice-agent-harness skill first to route tasks to the correct subagents.

Frequently Asked Questions about using-superpowers

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

FAQPage Schema
How do I route user questions to the correct subagent for code exploration or UX research?

To route intents, an orchestration layer evaluates user queries and maps them to specialized subagents, directing code questions to a code-explorer and UX questions to a ux-researcher before generating any response.

What is mandatory pre-dispatch in subagent orchestration?

Mandatory pre-dispatch is an orchestration mechanism that always invokes a routing harness to locate the correct skill before generating any user-facing response or clarifying question.

How do I validate subagent outputs before presenting results to the user?

Output validation enforces SLICE-compliant formatting and verifies that subagents return all requested items before the orchestrator summarizes and presents the final results to the user.

Can I plan implementations using a multi-agent routing table?

Yes, implementation planning is supported by encoding intent-to-subagent mappings in a routing table, allowing the orchestration layer to dispatch implementation queries to the appropriate specialized agent.

Do I need a slice-agent-harness to orchestrate workflows without dependencies?

Yes, the slice-agent-harness is required as the mandatory pre-dispatch routing layer to direct tasks to the correct subagents, functioning as the core orchestration mechanism even without external dependencies.