Superpower

Name: Superpower
Availability: InStock
Author: Dmitriy

Orchestrate Brainstorm, worktree setup, planning, TDD execution, and review checkpoints.

9|2|Updated Jan 22, 2026

Search Tags:#tdd #code review #implementation planning #git worktrees #agentic workflow #test enforcement #module orchestration

Ready to run

npx skills add https://github.com/DmitriyPolukhin/antigravity-superpower --skill superpower-dmitriypolukhin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Superpower
Source: https://github.com/DmitriyPolukhin/antigravity-superpower/tree/main
Command: npx skills add https://github.com/DmitriyPolukhin/antigravity-superpower --skill superpower-dmitriypolukhin

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents low-discipline, high-randomness coding by forcing a rigorous workflow for implementing changes, including planning and test-driven execution.

Core Features & Use Cases

Meta-router to disciplined modules: Routes you through Brainstorm → Plan → Execute (TDD) → Review → Finish.
Isolation with Git worktrees: Creates a clean, separate workspace to avoid polluting your main branch.
Hard enforcement of TDD: Blocks implementation unless a failing test exists, using automation scripts.
Review checkpoints: Requires spec-compliance checks and code-quality review before completion.

Quick Start

Tell your AI to open the Superpower skill to build your change using Brainstorm, then a worktree, then an implementation plan, and finally a strict TDD loop.

Frequently Asked Questions about Superpower

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

FAQPage Schema

What is an agentic workflow for test-driven development?▼

An agentic workflow for test-driven development orchestrates phases like brainstorming, planning, and execution through specialized modules. It enforces TDD by blocking implementation unless failing tests exist, ensuring disciplined coding and verification before review.

How do I enforce TDD in my coding workflow?▼

You enforce TDD by using automation scripts that block implementation unless a failing test exists. This hard enforcement ensures code is only written to satisfy tests, maintaining strict test-driven development discipline throughout the implementation process.

How do I isolate feature development from my main branch using git worktrees?▼

You isolate feature development by creating a separate git worktree workspace. This avoids polluting your main branch, providing a clean environment for planning and executing changes before merging reviewed code back.

What's the best way to structure implementation planning and code review?▼

The best way to structure implementation planning and code review is through a phased workflow: Brainstorm, Plan, Execute with TDD, and Review. This approach routes tasks to specialized modules, ensuring spec-compliance and code-quality checks before completion.

Can I use this agentic workflow for bug fixes and feature work?▼

Yes, you can use this agentic workflow for both feature work and bug fixes. It handles tasks requiring requirements clarification, safe workspace isolation via git worktrees, and strict verification before implementation through enforced TDD.

Why should I not skip the review checkpoint in test-driven development?▼

Skipping review checkpoints in test-driven development removes required spec-compliance and code-quality checks. Without these mandatory review phases, the workflow cannot validate that the implementation meets the original requirements before completion.