obra

A comprehensive guide to Test-Driven Development (TDD) that enforces the red-green-refactor cycle. Provides strict workflows for writing tests before implementation, common rationalizations to avoid, and testing anti-patterns to watch for when creating mocks or test utilities.

This skill teaches a rigorous 4-phase debugging methodology: Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. It includes practical utilities for condition-based test waiting and test pollution detection, along with documentation on root cause tracing and defense-in-depth validation strategies.

Guides the creation of well-structured Claude Code skills by applying Test-Driven Development principles to documentation. Includes templates for SKILL.md structure, testing methodologies using subagents with pressure scenarios, and optimization techniques for skill discovery (Claude Search Optimization).

Superpowers is a complete software development workflow library for AI coding assistants. It provides structured skills for test-driven development, systematic debugging, brainstorming, implementation planning, code review, and subagent-driven development. The skills enforce disciplined practices through mandatory workflows and integrate with Claude Code, OpenCode, and Codex platforms.

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

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

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

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when executing implementation plans with independent tasks in the current session

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

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.

Skills wiki intro - mandatory workflows, search tool, brainstorming triggers

Use when you need to run interactive CLI tools (vim, git rebase -i, Python REPL, etc.) that require real-time input/output - provides tmux-based approach for controlling interactive sessions through detached sessions and send-keys

Use MCP servers on-demand via the mcp CLI tool - discover tools, resources, and prompts without polluting context with pre-loaded MCP integrations