lawzava/megapowers

Plan, test, debug, and ship with more care in Claude Code and Codex.
One plugin, 15 skills, and safety hooks. About 1.4k tokens per session.
Install ·
What changes ·
Why megapowers ·
Skills ·
Docs
Coding agents are fast, but they can skip steps: edit before they know the
cause, say "done" without re-running the tests, or push and deploy without a
second look. megapowers gives Claude Code and Codex a skill (a short
playbook) for each of those moments. When your request matches one, the agent
is reminded to load it and follow it. Before the first commit or deploy in a
session, a hook pauses once and names the skill to load first.
It is exactly one plugin for Claude Code and Codex. It uses each tool's own
agents, permissions, worktrees, and memory, and ships no daemon, scheduler,
model router, formatter, or status line.
## What changes when it is installed
| You ask | What the agent does |
| "Why is this test flaky?" | systematic-debugging: finds the root cause before editing anything |
| "Add rate limiting to the API" | test-first-implementation: writes a failing test, sees it fail, then makes it pass |
| "Commit this and open a PR" | The first commit in the session pauses once and points the agent to verify-and-finish, which has it re-run your checks and report what actually passed |
| "Deploy to production" | safe-effects: confirms the exact target with you, then reads the result back |
| "Get a second opinion on this auth change" | independent-review: shows you what it will send, then asks a model from a different provider to review it |
| Agent runs rm -rf ~ or mkfs.ext4 /dev/sda1 | Blocked before it runs |
mermaid
flowchart TD
ask([You ask for something]) --> skill[Matching skill loads: plan, test first, debug, ...]
skill --> work[Agent works]
work --> gate{First commit, push, or deploy this session?}
gate -- yes --> check[Hook pauses once and names verify-and-finish or safe-effects]
check --> retry([Agent retries; command runs])
gate -- no --> run([Command runs])
work -. catastrophic command .-> blocked([Blocked])
Skills guide the agent; they do not force it (how often they load).
Only the pause and the command block are enforced, by the hook. Your
repository's own instructions and tools always come first.
## Install
Claude Code
bash
claude plugin marketplace add lawzava/megapowers@release
claude plugin install megapowers@megapowers
Codex
bash
codex plugin marketplace add lawzava/megapowers --ref release
codex plugin add megapowers@megapowers
Then start a fresh session. You need Go 1.25 or newer on PATH; the hooks
compile once into a local cache. Codex asks you to review and trust the hooks
before it runs them, and asks again whenever a release changes them.
Try it: ask "check my megapowers setup". The doctor reports the plugin
version, whether the hooks are registered, and whether the output style is
active.
Both installs track the release branch, which only moves to signed release
tags, so you never get unreleased main. Pinning, install scopes, and
uninstall are in docs/install.md.
## Why megapowers
Same behavior on Claude Code and Codex. One plugin, the same skills, and
the same Go hook code on both.
Checks before you ship. A hook pauses the first commit, push, PR, or