challenge

Stress-test AI-generated plans with Opus reasoning and Gemini constraint checks.

3|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/martineserios/thebrana --skill challenge-martineserios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: challenge
Source: https://github.com/martineserios/thebrana/tree/main/system/skills/challenge
Command: npx skills add https://github.com/martineserios/thebrana --skill challenge-martineserios

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the risk of AI generating flawed plans, designs, or code by subjecting them to rigorous adversarial review, ensuring robustness and identifying potential failure points before they occur.

Core Features & Use Cases

  • Dual-Model Review: Leverages both Opus and Gemini models for comprehensive analysis, combining reasoning and grounded knowledge retrieval.
  • Automated Context Inference: Intelligently identifies the most critical decision or plan in the conversation to review, even without explicit user direction.
  • Configurable Challenge Flavors: Selects the most appropriate adversarial approach (pre-mortem, simplicity, assumption buster, adversarial reviewer) based on the context.
  • Use Case: Before committing to a complex new architecture, run /brana:challenge to have Opus simulate a production failure and Gemini check against documented constraints, surfacing potential issues like overlooked dependencies or performance bottlenecks.

Quick Start

Run the challenge skill on the current plan to identify potential flaws.

Frequently Asked Questions about challenge

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

FAQPage Schema
How do I stress-test AI generated plans for logical flaws?

To stress-test AI generated plans, you can run a dual-model adversarial review that simulates production failures and checks against documented constraints to surface logical flaws. It automatically infers the plan from your conversation context and applies reasoning-based stress-testing to identify potential failure points.

What is adversarial review for AI safety and risk assessment?

Adversarial review for AI safety is a risk assessment technique that subjects AI-generated architectures to rigorous constraint checking and pre-mortem analysis. It identifies overlooked dependencies and performance bottlenecks by combining reasoning-based stress-testing with grounded knowledge retrieval to ensure robustness.

Can I use dual-model review to validate code quality and architecture decisions?

Yes, you can use dual-model review to validate code quality and architecture decisions by leveraging Opus for reasoning-based stress-testing and Gemini for retrieving specific documented constraints. This combination ensures comprehensive analysis and compliance verification before you commit to complex designs.

How do I automatically infer the review target for plan validation without explicit direction?

You can automatically infer the review target for plan validation because the skill intelligently identifies the most critical decision or plan in your current conversation context. It then selects an appropriate challenge flavor, such as assumption buster or adversarial reviewer, without requiring explicit user direction.

What is the best way to perform a pre-mortem analysis on AI architecture designs?

The best way to perform a pre-mortem analysis on AI architecture designs is to use configurable challenge flavors that simulate production failures. This approach automatically applies adversarial reasoning to identify potential failure points and ensure compliance with documented constraints before implementation.

When should I not use adversarial reasoning for constraint checking?

You should avoid using adversarial reasoning for constraint checking when dealing with simple, low-risk tasks that do not require rigorous plan validation or risk assessment. It is specifically designed for complex architectures where identifying overlooked dependencies and performance bottlenecks is critical before commitment.