ultrapowers

Use when fixing bugs, debugging failures, or proactively reviewing code for hidden bugs. Reactive mode: fix known bugs. Proactive mode: hunt for bugs in code. Enforces confirmed root cause before any fix.

Toolkit for creating and validating skills and subagents. Use when: creating a new skill (fast or full mode), validating an existing skill, deciding Skills vs Subagents, migrating docs to skills, estimating token cost, or running a security scan. Triggers: "create skill", "build skill", "validate skill", "new subagent", "skills vs subagents", "estimate tokens", "security scan".

Fast iteration workflow with mandatory subagent plan review. Use when implementing small-to-medium changes quickly. Trigger on "quick fix", "small change", "just update X", or any change where full superpowers ceremony is overkill but accuracy still matters. Enforces brief-plan + subagent-review gates before any implementation.

Use when rigorous adversarial critique is needed for any artifact — code, APIs, plans, architectures, UX flows, data schemas, infrastructure configs, or documents. Triggers on: "adversarial review", "stress test this", "validate this hard", "find weaknesses", "critique this plan/code/design/architecture".

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. For novel/uncertain tasks (domain shifts, unknown algorithms, complex translations), generates testable hypotheses that feed into planning.

Automate the full release workflow: version bumping (major/minor/patch), changelog generation, git tagging, pushing, and GitHub release creation. Handles semver across Node.js, Python, Rust, Go, and generic projects. Enforces mandatory confirmations before irreversible actions (push, release). USE WHEN: user says "release", "bump version", "cut a release", "tag and release", "/releasing", or asks to prepare a new version of their project.

Validate implementation plans against DRY, YAGNI, TDD principles and best practices. Use when reviewing development plans created by writing-plans or similar planning workflows to identify gaps, anti-patterns, and improvement opportunities before execution.

Use when you have a spec or requirements for a multi-step task, before touching code