All directories
AgentEngineeringProduct

Superpowers

obra/superpowers methodology pack (20+ skills) adding a senior-consultant requirements/planning phase—interrogation, edge cases, TDD, debugging, and collaboration—before execution.

Open on GitHubBrowse more agents
01

Overview

Superpowers is a Claude agent catalogued in LimeDock Directories for teams working across engineering, product, other. It is tagged for saas, other contexts. obra/superpowers methodology pack (20+ skills) adding a senior-consultant requirements/planning phase—interrogation, edge cases, TDD, debugging, and collaboration—before execution. Use this page as the operational brief: install path, how to invoke it, copy-paste prompts, prerequisites, and concrete use cases so your team can adopt it without re-reading every roundup article.

SaaSOther

Work with LimeDock

Using this skill? LimeDock can wire it into a durable automation you own.

Agents are a starting point. LimeDock turns the workflow into production automation your SaaS team owns — not another prompt library.

We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.

Book a workflow call
02

Link

https://github.com/obra/superpowers
03

Installation guide

/plugin marketplace add obra/superpowers-marketplace
/plugin install superpowers@superpowers-marketplace
04

How to use it

Start complex work with Superpowers planning/brainstorming skills before coding; follow TDD/debug/collaboration skills through delivery.

**Suggested workflow** 1. Install and enable the agent. 2. Open the target project (or Claude.ai chat) with enough product context. 3. Invoke with a clear goal, constraints, and success criteria. 4. Review the first output against your standards; refine with follow-ups. 5. Save winning prompts / outputs into your team playbook.

If Claude does not auto-select it, mention the agent by name: “Use the Superpowers agent…”

05

Example prompts

  • “Use the Superpowers agent for this task: Requirements workshop before a feature”
  • “Walk me through how Superpowers would approach this step by step, then execute.”
  • “Review my current draft/plan and improve it using Superpowers. Call out assumptions.”
  • “Produce a checklist I can reuse whenever we run Superpowers on similar work.”
06

Use cases and examples

  • Requirements workshop before a feature
  • TDD-driven implementation
  • Subagent-driven development with reviews
  • Structured debugging sessions
  • First-week trial of Superpowers on a real engineering workflow
  • Document a reusable prompt template for Superpowers for your team
07

Prerequisites

  • Claude Code, Claude.ai (Skills enabled), or an Agent Skills–compatible host
  • Network access if the skill fetches guidelines or calls external tools
  • Project or brand context (CLAUDE.md / product notes) for better outputs
  • Permission to install third-party skills — audit SKILL.md and scripts first
  • Clear success criteria — agents run multi-step workflows and need a defined “done”
08

Tips

  • Keep descriptions/triggers tight so Superpowers fires only when relevant (avoids context tax).
  • Prefer one sharp job over a mega-skill that tries to do everything.
  • Pair with verification (tests, review, screenshots) before shipping outputs.
  • Re-audit installed skills monthly — unused skills still cost context every turn.
  • Give agents scoped tools and sandbox risky actions (filesystem, deploys, payments).
09

Sources