superpowers-patterns

Enforce quality controls on multi-step AI tasks with gates and checklists.

1|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/iAMv1/agent-os --skill superpowers-patterns-iamv1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-patterns
Source: https://github.com/iAMv1/agent-os/tree/main/skills/superpowers-patterns
Command: npx skills add https://github.com/iAMv1/agent-os --skill superpowers-patterns-iamv1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Non-negotiable quality enforcement for AI tasks, preventing skipped steps and ensuring verifiable results.

Core Features & Use Cases

  • Iron Laws: absolute rules that cannot be bypassed
  • Hard Gates: checkpoints that block progress until conditions are met
  • Anti-Slop Rules: explicit patterns to avoid vague or unfounded claims
  • Rationalization Tables: preempt self-justification with reality checks
  • Red Flag Lists: indicators to halt progress when quality is at risk
  • Checklist Enforcement: mandatory completion and verification of steps

Quick Start

Apply iron-law enforcement to the current task by outlining gates, laws, and a completion checklist.

Frequently Asked Questions about superpowers-patterns

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

FAQPage Schema
How do I enforce quality controls and prevent skipped steps in AI task execution?

To enforce quality controls in AI task execution, apply configurable iron laws and hard gates that block progress until conditions are met. This prevents skipped steps and ensures verifiable results for complex workflows.

What are hard gates and iron laws for multi-step task integrity?

Hard gates and iron laws are non-negotiable quality controls for multi-step task integrity. Iron laws are absolute rules that cannot be bypassed, while hard gates act as checkpoints blocking progress until specific conditions are verified.

How do I stop AI from rationalizing shortcuts during complex coding or planning tasks?

To stop AI from rationalizing shortcuts, use rationalization tables and anti-slop rules that preempt self-justification with reality checks. These explicitly define patterns to avoid vague claims and halt progress when quality is at risk.

Can I use checklist enforcement for complex research and planning workflows?

Yes, you can use checklist enforcement for complex research and planning workflows. It mandates completion and verification of steps, applying red-flag checks to guard against shortcuts where step integrity matters.

Does enforcing anti-slop rules work without external dependencies?

Yes, enforcing anti-slop rules works without external dependencies. The enforcement mechanism relies entirely on internal configurable rules, rationalization tables, and checklist verification to maintain step integrity.

When should I not use iron-law quality enforcement for AI tasks?

You should not use iron-law quality enforcement for simple, single-step tasks. It is designed for complex, multi-step coding, research, and planning workflows where hard gates and step integrity are necessary to prevent shortcuts.