magebyte-power

> Battle-tested Claude Code Superpowers skills — engineering workflows and verification methodologies distilled from real production incidents.
---
Skills
| Skill | What it does | When to use |
|-------|-------------|-------------|
| cross-verified-feature-development | 7-phase feature workflow with 4 independent cross-verification passes | High-stakes backend features: payments, state machines, concurrency, cross-service changes |
---
What is Superpowers?
Superpowers is an MCP plugin for Claude Code that provides general-purpose skills: brainstorming, writing-plans, subagent-driven-development, systematic-debugging, code-reviewer, and more.
The skills in this repo are **domain-specific orchestrators** — they call Superpowers' general skills at the right phase with the right context, so you get the full power of the ecosystem without wiring it up yourself.
**Without Superpowers**, the skill still works — each phase has a documented fallback using Claude Code's built-in tools.
---
Prerequisites
**1. Claude Code**
**2. Superpowers plugin** (recommended)
First-time use requires an Anthropic account. Fallback mode is available without Superpowers.
---
Installation
Verify:
---
cross-verified-feature-development
A rigorous 7-phase feature development methodology that inserts **4 independent verification passes** between implementation and merge — catching the concurrency, idempotency, and cross-service contract bugs that self-review and standard code review systematically miss.
The core problem this solves
Single-perspective review has structural blind spots. Even experienced developers will:
- Default to their own design assumptions when reading their own code
- Assume "should be idempotent" operations actually are
- Miss concurrent race windows because their mental model is sequential
- Forget that other services consume their shared tables and MQ topics
**Independent perspectives produce independent signals.** Running N reviewers who don't share context produces a bug set that's close to a union, not a duplicate. This workflow operationalizes that insight:
> Design → Implement → **Multi-round cross-verification** → Fix → Carefully simplify → Sync docs
How Superpowers powers each phase
| Phase | Superpowers skill | What it adds |
|-------|------------------|-------------|
| 1. Requirements & Design | superpowers:brainstorming | Structures vague requirements into a complete spec with invariants, failure modes, and risk table |
| 2. Implementation Plan | superpowers:writing-plans | Breaks spec into independently verifiable tasks with file+line targets, TDD structure, rollout strategy |
| 3. Implementation | superpowers:subagent-driven-development | Each task runs in a fresh subagent — no accumulated bias, independent spec compliance + quality review per task |
| 4.1 Self-review | superpowers:systematic-debugging | Structured "assume there's a bug, find it" scan against the full feature |
| 4.2 Cold-context review ⭐ | superpowers:code-reviewer | Reviewer gets **no design docs** — finds design-level blind spots the author can't see |
| 4.3–4.5 (parallel) | Custom agent prompts | Behavior-preservation diff, cross-repo impact scan, business invariant matrix |