in20-antigoals-and-anti-patterns-catalog

Document failure modes and anti-patterns to avoid in plans.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/hummbl-dev/hummbl-agent --skill in20-antigoals-and-anti-patterns-catalog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: in20-antigoals-and-anti-patterns-catalog
Source: https://github.com/hummbl-dev/hummbl-agent/tree/main/skills/IN-inversion/in20-antigoals-and-anti-patterns-catalog
Command: npx skills add https://github.com/hummbl-dev/hummbl-agent --skill in20-antigoals-and-anti-patterns-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps users proactively identify and document potential failure modes and undesirable patterns, rather than focusing solely on success strategies, leading to more robust planning and risk mitigation.

Core Features & Use Cases

  • Failure Mode Documentation: Explicitly outlines what not to do or what to avoid.
  • Risk Identification: Helps in stress-testing plans by considering negative outcomes.
  • Use Case: When planning a new product launch, use this Skill to document potential pitfalls like market rejection, technical failures, or logistical nightmares, ensuring contingency plans are in place.

Quick Start

Apply the IN20 transformation to document failure modes to avoid for the upcoming project launch.

Frequently Asked Questions about in20-antigoals-and-anti-patterns-catalog

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

FAQPage Schema
What is an antigoals catalog and how does it help with project planning?▼

An antigoals catalog documents failure modes and anti-patterns to avoid, rather than success patterns to emulate. It helps with project planning by proactively identifying risks and reversing assumptions to stress-test your strategy.

How do I document anti-patterns for a new product launch?▼

To document anti-patterns for a product launch, you define a focus like market rejection or technical failure, apply the IN20 transformation model to imagine failure states, and synthesize outcomes to establish clear contingency plans.

Can I use failure mode documentation to simplify project outcomes?▼

Yes, failure mode documentation simplifies project outcomes by identifying and removing unnecessary elements. By imagining negative outcomes and applying the IN20 model, you can streamline deliverables and avoid logistical nightmares.

What is the best way to identify risk management anti-patterns in documentation?▼

The best way to identify risk management anti-patterns is to stress-test your existing plans by reversing assumptions. Documenting what not to do ensures you catch potential failure modes before they occur.

When should I not use antigoals for risk identification?▼

You should not rely on antigoals for risk identification when you lack a clearly defined project focus. The process requires a specific target to reverse assumptions and effectively synthesize failure states.