Without Superpowers, Claude acts like an eager new hire. You ask for something and it jumps in, guesses what you meant, and says "done!" before checking its work. With it, Claude works like an experienced contractor: it asks questions first, writes a plan, builds one piece at a time, checks each piece, and only says "done" once it has shown that it works.
Superpowers is a free, open-source plugin. It gives Claude a set of built-in habits, called skills, that switch on by themselves, so you don't have to remember to ask. This guide covers the install, the habits, five real jobs for a service business, and the prompts to copy.
Want it set up for you?
On a free 30-minute call, Megan will name your biggest time leak and give you an honest answer on whether Clockwise is the right fit. The rest of this guide is the do-it-yourself path.
One thing to know first
Superpowers was built mainly for building software. You'll get the most out of it when you're making something with Claude, such as a website, a tool, an automation or a dashboard. It plugs into Claude Code (and a handful of similar coding tools, listed in Part 1), not the regular chat window. For quick questions or a single email, it mostly stays out of the way.
Install Superpowers
Pick the tool you use. The commands below change to match. The project is on GitHub at github.com/obra/superpowers, and that page always has the latest install steps.
Which tool are you using?
Run the install command
Open Claude Code and type this in the message box. It installs from Anthropic's official plugin marketplace.
Install command: Claude Code
Type it into Claude Code, then press Enter
/plugin install superpowers@claude-plugins-official
Prefer the plugin author's own marketplace? Use the two commands in the "Alternative" box below instead.
Alternative: the Superpowers marketplace
Run both, one after the other
/plugin marketplace add obra/superpowers-marketplace /plugin install superpowers@superpowers-marketplace
In Cursor's agent chat, type this command.
Install command: Cursor
Type it into the agent chat
/add-plugin superpowers
In the Codex app, open Plugins in the sidebar, find Superpowers in the Coding section and click +. In the Codex command line, type this, search for superpowers and choose Install Plugin.
Install command: Codex CLI
Then search for "superpowers"
/plugins
Run this in your terminal.
Install command: Gemini CLI
Run in your terminal
gemini extensions install https://github.com/obra/superpowers
Run both commands in your terminal, one after the other.
Install commands: GitHub Copilot CLI
Run in your terminal
copilot plugin marketplace add obra/superpowers-marketplace copilot plugin install superpowers@superpowers-marketplace
Using something else, like OpenCode, Pi or Qwen Code? The GitHub page lists the install line for each.
Start a fresh session
Close your current conversation and open a new one, so the plugin loads from the start. If you're in Claude Code, you can also restart it.
Check it's switched on
Paste this into the new session. Claude should list skills such as brainstorming, writing plans and systematic debugging. If it doesn't, repeat the install and start a fresh session again.
Prompt: check Superpowers is installed
Paste into Claude
Do you have the Superpowers skills available in this session? List the ones you can see, with a one-line plain-English description of each.
The five habits, in plain English
You don't switch these on. They start by themselves when the job calls for them. Tap a habit to see what it means for you.
Instead of guessing, Claude asks who the thing is for, what good looks like and what you'll do with the result. It then offers a couple of options with a recommendation.
You'll hear: "Before I build this, who fills it out, and where should the answers go?"
You get a short plan in ordinary language before anything is built. You can change it, cut it or approve it. Nothing happens until you say so.
You'll hear: "Here's the plan in five steps. Want me to change anything before I start?"
Each step is built and checked on its own, so a problem in step three doesn't quietly break step one. Often a helper builds the step and a second pair of eyes reviews it.
You'll hear: "Step 2 is done and reviewed. Moving to step 3."
Claude reproduces the problem first, works out why it happens, then fixes that one thing. You stop getting three changes at once and no idea which one worked.
You'll hear: "I can reproduce it. The cause is an expired email connection. I'm fixing only that."
"Done" now comes with evidence: a test that passed, a figure that matches your source, a message that arrived. If it can't prove it, it tells you so.
You'll hear: "I sent a test submission and it reached your inbox. Here's the result."
Five jobs for a service business
Pick a job to see the before and after, then copy the prompt. Flip the switch to compare. Fill in the box first and the prompts use your wording.
Personalise the prompts
Booking or intake form on your website
You say "make me a client intake form." You get a generic form in 30 seconds. Later you notice it doesn't ask about budget, doesn't send you an email, and looks wrong on a phone.
Claude first asks: who fills it out? What do you need to know before a discovery call? Where should the answers go? Should the client get a confirmation? It shows you a short plan, then builds and tests it. You end up with a form that fits how you actually work.
Prompt: client intake form
Paste into Claude with Superpowers on
Help me build a client intake form for my website. My business is a service business. Use your brainstorming habit first. Ask me one question at a time about who fills it out, what I need to know before a discovery call, where the answers should go (my business email to start), and whether the client should get a confirmation. Then show me a short plan in plain English and wait for my approval. Build it step by step, and test it on a phone-sized screen before you tell me it's finished. Show me proof that a test submission arrives.
Automating client onboarding
"Automate my onboarding" turns into one big, tangled setup. When the welcome email doesn't send, Claude changes three things at once, and now something else breaks.
The plan has clear steps: contract signed, welcome email, intake form, kickoff call booked. Each step is built and tested on its own. If something fails, Claude traces the actual cause, such as a wrong trigger or a missing field, and fixes just that.
Prompt: client onboarding automation
Paste into Claude with Superpowers on
Help me automate client onboarding for a service business. Today the steps are: contract signed, welcome email, intake form, kickoff call booked. Use your brainstorming habit first and ask me what tools I use for each step, what should happen if a step fails, and who should be told. Then write a plan with each step as its own piece. Build and test one step at a time, and don't move on until the current step is proven to work. If something breaks, find the real cause before changing anything. Alert me at my business email if a step fails.
Proposal or quote generator
Claude builds a pricing calculator, and the math is quietly wrong for package add-ons. You find out when a client points it out.
Claude writes down the expected results first (for example, "Package B plus rush fee should equal $X") and checks the tool against them before handing it over.
Prompt: quote and proposal generator
Paste into Claude with Superpowers on
Help me build a quote generator for a service business.
Use your brainstorming habit first. Ask me about my packages, add-ons, rush fees, discounts and GST.
Before you write any code, write down a list of worked examples with the exact total each one should come to (for example, "Package B plus rush fee = $X"). Ask me to confirm those numbers. Then build the tool and check it against every example. Show me the results table before you say it's finished.
The confirmed examples are the key. You approve the maths in plain numbers, and Claude has to hit them.
Client dashboard or monthly report
You get a nice-looking dashboard, but nobody confirmed the numbers match your real data.
Claude agrees with you on what each number means, builds the dashboard, then compares its figures against your source data before saying it's finished.
Prompt: dashboard or monthly report
Paste into Claude with Superpowers on
Help me build a monthly client report for a service business.
Use your brainstorming habit first. For each number on the report, ask me what it means, where the source data lives and how it's worked out. Write those definitions down and get my approval.
Then build the report. Before you say it's finished, compare every figure against the source data I give you and show me a side-by-side check. Flag any number you couldn't verify.
Fixing something on your site
"My contact form stopped sending leads." Claude makes a few guesses, and you can't tell if any of them fixed it.
Claude reproduces the problem, finds the cause (for example, an expired email connection), fixes that one thing, and sends a test to prove leads are coming through again.
Prompt: fix a broken form or workflow
Describe the problem in the first line
Something is broken: [describe it, e.g. "my contact form stopped sending leads to my business email"]. It last worked [when].
Use your debugging habit. Don't guess and don't change anything yet. First reproduce the problem, then explain the real cause in plain English. Then fix only that cause, and prove the fix by sending a test through and showing me the result.
If you can't reproduce it, tell me what you'd need from me.
Edit the square-bracket parts before you paste.
Your first build
Not sure where to start? Describe what you want built and let the brainstorming habit take over. Type it in the box and the prompt writes itself.
What do you want to build?
Say what you want, and nothing more
You don't need to say "use brainstorming". Just describe the job. Claude should start by asking you questions. Answer them one at a time, in your own words.
Prompt: start a build
Paste into Claude with Superpowers on
Help me build a client onboarding checklist tool.
Short on purpose. The habit should start on its own and ask you questions first.
Read the plan, then approve or change it
When Claude shows the plan, check it against what you actually want. Does each step make sense to you? Is anything missing? Reply in plain language.
Prompt: tighten the plan
Use when the plan is nearly right
Before you start, explain this plan to me like I'm not technical. For each step tell me: what it does, how you'll check it works, and what I'll be able to see when it's done. Cut anything that isn't needed for the first version.
Ask for proof at the end
Superpowers already checks before it says "done". This prompt makes the evidence easy for you to read.
Prompt: show me it works
Paste before you accept the result
Before I accept this, show me proof it works. List what you checked, what the result was, and anything you couldn't check. Then tell me the first thing most likely to go wrong when a real client uses it.
Tips and troubleshooting
Quick jobs
For a single email or a quick question, Superpowers mostly stays out of the way. You don't need to turn anything off.
Answer one question at a time
Short, honest answers beat long ones. "I don't know" is a fine answer, and Claude will suggest options.
The trade
A few extra minutes of questions and planning up front, for much less redoing, fewer hidden mistakes and fewer "I thought this was finished" surprises.
If Claude jumps straight in without asking questions
Prompt: nudge it back to planning
Paste when Claude skips the questions
Stop. Use your brainstorming skill first. Ask me questions one at a time before you build anything, then show me a plan and wait for my approval.
Good to know
- Superpowers is a third-party open-source project, not made by Clockwise or Anthropic. Read its GitHub page and decide whether you're comfortable installing it, as you would with any plugin.
- Install commands and supported tools change over time. If a command here doesn't work, the GitHub page has the current version.
- Claude can still make mistakes. The habits make them rarer and easier to catch, but you remain the final check on anything your clients will see.
Want these tools built and running in your business?
Forms, onboarding, quotes and reports are where a small team gets hours back. On a free 30-minute call, Megan will:
- name your biggest time leak
- give you an honest answer on whether working with Clockwise is the right fit
Google Meet, 30 minutes, no cost. Rather write first? Start a conversation.
