superpowers

Enforce RED-GREEN-REFACTOR and two-stage code reviews across development phases.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Lingjie-chen/MT5 --skill superpowers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers
Source: https://github.com/Lingjie-chen/MT5/tree/main/.trae/skills/superpowers
Command: npx skills add https://github.com/Lingjie-chen/MT5 --skill superpowers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the entire software development lifecycle by enforcing a structured RED-GREEN-REFACTOR methodology and a two-stage code review process, ensuring higher quality code and efficient development.

Core Features & Use Cases

  • Workflow Automation: Integrates with various stages of development, from brainstorming and design to implementation, testing, and review.
  • Structured Development: Enforces methodologies like RED-GREEN-REFACTOR and YAGNI (You Ain't Gonna Need It).
  • Code Quality: Implements a two-stage code review process with configurable severity thresholds to block or flag critical issues.
  • Use Case: When starting a new feature, you can ask the AI to "plan this feature," which will trigger brainstorming and task breakdown. As you implement, it enforces TDD, and before merging, it initiates a rigorous code review.

Quick Start

Ask the AI to help you plan the implementation of a new feature.

Frequently Asked Questions about superpowers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce TDD and RED-GREEN-REFACTOR in my development workflow?

You can enforce RED-GREEN-REFACTOR in your development workflow by triggering automated task breakdown and policy execution during implementation. This structured methodology ensures you write failing tests first, implement minimal code, and then refactor to reduce complexity.

What is a two-stage code review process and how does it improve code quality?

A two-stage code review process evaluates code across design, implementation, and testing phases using configurable severity thresholds. It improves code quality by systematically blocking or flagging critical issues before merging, ensuring rigorous validation.

How do I plan a new feature using automated task breakdown and branch management?

To plan a new feature, prompt the AI to plan the implementation, which triggers brainstorming, automated task breakdown, and branch management. This process structures the feature from initial design through testing, enforcing YAGNI principles.

Can I configure severity thresholds to block critical issues during code review?

Yes, you can configure severity thresholds to block or flag critical issues during the two-stage code review. This policy enforcement ensures that severe problems are identified and prevented from merging without manual intervention.

When should I not use an AI-driven agile workflow for software engineering?

You should avoid an AI-driven agile workflow if your project lacks clear testing phases or requires ad-hoc implementation without structured branch management. This approach enforces strict RED-GREEN-REFACTOR methodologies that may not suit rapid prototypes.