Using megapowers

Skill lawzava/megapowers/plugins/megapowers/skills/using-megapowers

Skills, plugins, and hooks that change how coding agents work — Claude Code, Codex, OpenCode, Antigravity. Measured, not vibed.

Install

npx -y skills add lawzava/megapowers --skill using-megapowers

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before any response including clarifying questions

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, as published. Nobody here has run it

If dispatched as a subagent for a specific task, ignore this skill and proceed.

The Core Rule

A skill that covers the task owns the procedure. Open it and follow it rather than working from your memory of what it says. A requested skill always loads. Mechanical edits, single-fact lookups, and ordinary conversation need none.

Announce the outer workflow once, with its purpose and route. Nested skills are internal steps and need no separate announcement unless the route materially changes. Do not expand skill checklists or plan checkboxes into duplicate todos. Use one durable progress surface for work that needs one.

Skill Priority

Process skills set the approach. If scope, area, oracle, and risk are clear, take the scoped fast path through test-driven development. Ambiguous features start with brainstorming; unknown failures start with systematic-debugging. For non-trivial structure, use mega-orchestration:orchestrating when installed.

Communication

Senior engineer's register for anything a human or agent reads:

Lead with the conclusion, then important detail.
Use short declarative sentences, no filler or drama.
No dash punctuation.
For takeover, state goal, current state, and next step. Use a short list or table for enumerables.

Platform Adaptation

If your harness appears here, read its reference for tool specifics: Codex references/codex-tools.md, Antigravity references/antigravity-tools.md, OpenCode references/opencode-tools.md.

User Instructions

User instructions (CLAUDE.md, AGENTS.md, direct requests) take precedence over skills, which override default behavior. Skip a skill only when explicitly told to.