obra/superpowers@writing-skills

Enforce a RED-GREEN-REFACTOR cycle for AI agent skill documentation.

2.0k|267|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/openakita/openakita --skill obra-superpowers-writing-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obra/superpowers@writing-skills
Source: https://github.com/openakita/openakita/tree/main/skills/superpowers-writing-skills
Command: npx skills add https://github.com/openakita/openakita --skill obra-superpowers-writing-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that documentation (Skills) is created and maintained with the same rigor as code, preventing common pitfalls and ensuring discoverability.

Core Features & Use Cases

  • Test-Driven Documentation: Applies the RED-GREEN-REFACTOR cycle to skill creation.
  • Rationalization Prevention: Provides strategies to counter common excuses for skipping testing or documentation rigor.
  • Use Case: When creating a new skill for an AI agent, use this skill to guide the process from initial testing (watching the agent fail without the skill) to writing the skill documentation and refactoring it to be bulletproof against loopholes.

Quick Start

Follow the RED-GREEN-REFACTOR cycle when creating or updating any skill documentation.

Frequently Asked Questions about obra/superpowers@writing-skills

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

FAQPage Schema
How do I apply test-driven development to AI agent skill documentation?

Apply test-driven development to skill documentation by enforcing a RED-GREEN-REFACTOR cycle: establish baseline testing, write minimal skill instructions, and refactor to close loopholes. This ensures AI agent behavior is thoroughly tested before documentation is finalized.

What is the RED-GREEN-REFACTOR cycle for writing AI skills?

The RED-GREEN-REFACTOR cycle for AI skills is a documentation process where you first watch the agent fail without the skill, write minimal instructions to make it pass, then refactor to eliminate loopholes. It treats skill documentation with code-level testing rigor.

How do I prevent rationalizations when testing agent behavior documentation?

Prevent rationalizations in agent behavior testing by mandating rigorous baseline tests before writing documentation. Counter common excuses for skipping test coverage by requiring a passing GREEN state that proves the skill instructions actually resolve the targeted agent failure.

Why does my AI agent fail to follow skill documentation consistently?

AI agents fail to follow skill documentation consistently due to loopholes in the instructions. Refactoring skill documentation through a rigorous testing cycle closes these loopholes, preventing rationalizations and ensuring the agent behavior remains predictable and effective.

Can I use TDD principles to maintain existing AI agent skills?

Yes, you can use TDD principles to maintain existing AI agent skills by applying the RED-GREEN-REFACTOR cycle during updates. Re-establish baseline testing for current agent behavior, modify the skill documentation, and refactor to ensure updates do not introduce new loopholes.

What is the best way to ensure new AI agent skills are discoverable and effective?

The best way to ensure new AI agent skills are discoverable and effective is to mandate a rigorous test-driven development cycle. By testing baseline agent failures and refactoring minimal skill writing to close loopholes, documentation remains bulletproof and highly functional.