simulate-failure

Simulates Non-Normal procedures to validate agent responses and avoidance of production file modification.

3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ArtemioPadilla/agent-triforce --skill simulate-failure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simulate-failure
Source: https://github.com/ArtemioPadilla/agent-triforce/tree/main/.claude/skills/simulate-failure
Command: npx skills add https://github.com/ArtemioPadilla/agent-triforce --skill simulate-failure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps validate AI agent workflows by safely simulating Non-Normal procedures to ensure correct invocation of escalation procedures and proper labeling of outputs.

Core Features & Use Cases

  • Generates controlled Ambiguous Spec, failing-tests, and security-finding scenarios to exercise NON-NORMAL checklists.
  • Creates training artifacts in docs/training/ for auditability and learning, and provides scoring of checklist items.
  • Supports safe isolation and guarantees no modification to production files during simulations.

Quick Start

Run a Non-Normal simulation to verify agent responses.

Frequently Asked Questions about simulate-failure

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

FAQPage Schema
How do I simulate non-normal failure scenarios to test AI agent responses safely?

Simulating non-normal failure scenarios involves generating controlled Ambiguous Spec, failing-tests, and security-finding procedures within a safe isolation context to validate agent responses without modifying production files.

What is a non-normal checklist and how does it validate escalation paths?

A non-normal checklist defines procedures for handling ambiguous specs, failing tests, and security findings. This skill simulates these procedures to ensure agents correctly follow escalation paths and label outputs as SIMULATION MODE.

How do I generate training artifacts for QA auditing without affecting production files?

You generate training artifacts by running non-normal simulations that write auditability outputs to the docs/training/ directory. The strict isolation context guarantees no modification to production files during the process.

Can I use this for QA training on security findings and ambiguous specs?

Yes, you can use this for QA training by generating controlled security-finding and Ambiguous Spec scenarios. It scores checklist items and creates training artifacts in docs/training/ for learning and auditability.

What are the limitations of simulating failure scenarios in isolation?

The primary limitation is that simulations operate within a strict isolation context and cannot modify production files. Agents must follow escalation paths and label all outputs as SIMULATION MODE for auditability.