HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
obra
superpowers
Shell2025–2026
obra / superpowers

superpowers

An agentic skills framework & software development methodology that works.

64Distinct people
77Mentions
3Explicit recommenders
316.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An agentic skills framework & software development methodology that works.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

https://github.com/obra/superpowers I use Opus/Sol with for /brainstorming, deepseek (on Pi) for /subagent-driven-development I love it, the docs are easily editable and when…

cthulberg used a recommendation phrase. 3 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 11:34:28 AM UTC.

Locating the source of a mysterious beep direct repository linkDebated

The discussion centers on a project using AI and networked microphones to locate a mysterious beep, with users debating the practical efficiency of this high-tech approach versus simple manual methods like physical binary search or unpacking boxes. Participants also argue over whether the project represents genuine learning and utility or merely an unnecessary expenditure of computational resources for a trivial problem.

172 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4

Mentions over time

HN mentions by month77 dated mentions

Observed mentions: 2025-10-11 14:41:58 UTC to 2026-09-26 02:10:10 UTC.

0369122025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 commentsOct 20252025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 10 mentions; 2 submissions, 8 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 9 mentions; 3 submissions, 6 commentsMar 20262026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 12 mentions; 3 submissions, 9 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 6 mentions; 2 submissions, 4 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsSep 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC615
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC303
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC514
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC725
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC1028
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC936
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC1239
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC523
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC624
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC10010
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC202
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC202

What Hacker News says

5 sources
> It would be extremely cool to be able to write one or two lines of prompt in my harness, and have a light model iterate with me a few times writing/proposing requirements, guidelines and explanations, refining the prompt until it's ready to be sent to the actual LLM. It is cool and (IMO) necessary, and most AI-using coders I know do this using skill suites like Superpowers (see: /superpowers:brainstorming). https://github.com/obra/superpowers
In Show HN: Promptloop – create, run, and improve prompt evals from the terminal
anaq42·May 14, 2026Submission

Show HN: JDS – a Copilot skill suite for structuring AI coding behavior

A few months ago I stumbled on obra's superpowers repository https://github.com/obra/superpowers. I really liked the approach and idea that you enforce discipline for your agent through a skill-based workflow. Even though coding agents (copilot included) have become a lot better at natively handling complex tasks, they still wander off and lose track of things. I really liked how superpowers fixed this and how it enabled long-running sessions without the agent losing its "focus". So I decided to build a Copilot tailored skill suite around the core idea of superpowers. I didn't just want to port superpowers to Copilot, I took inspiration from it and improved on it. JDS enforces a strict think -> plan -> execute pipeline where nothing gets skipped. It leverages Copilot's built-in sql todo dependencies and provides a live task graph visualiz
Read the rest
er which helps visualize the agentic workflow and its parallelism. Curious whether others have tried similar approaches, and what's worked or not.
9 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.