rad

Identify and verify implicit assumptions in AI-generated code.

Updated Nov 24, 2025
One-click install
npx skills add https://github.com/ByronWilliamsCPA/.claude --skill rad-byronwilliamscpa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rad
Source: https://github.com/ByronWilliamsCPA/.claude/tree/main/.claude/skills/rad
Command: npx skills add https://github.com/ByronWilliamsCPA/.claude --skill rad-byronwilliamscpa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI-generated code often contains implicit assumptions that pass initial testing but fail catastrophically in production under real-world conditions like high load, concurrency, or edge cases. This Skill systematically identifies and verifies these hidden assumptions before they reach deployment.

Core Features & Use Cases

  • Multi-Model Verification: Routes assumptions to appropriate AI models based on risk level—premium models for critical production risks and free models for standard and edge cases.
  • Assumption Tagging: Enables systematic tagging of assumptions during development with #CRITICAL, #ASSUME, and #EDGE markers.
  • Workflow Automation: Provides slash commands for verification, inventory listing, and system testing integrated with pre-commit hooks.

Quick Start

Use the rad skill to verify all hidden assumptions in your current project by running the assumption verification workflow on your recently changed files.

Frequently Asked Questions about rad

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

FAQPage Schema
How do I verify hidden assumptions in AI-generated code before production deployment?

Verify hidden assumptions in AI-generated code by systematically identifying and validating timing dependencies, external resource availability, data integrity, concurrency, and security risks before production deployment. This process uses multi-model AI routing to evaluate critical production risks and standard edge cases.

What causes AI-generated code to pass initial testing but fail under high load in production?

AI-generated code fails in production under high load due to implicit assumptions about concurrency, timing dependencies, and edge cases that pass initial testing but break under real-world conditions. Systematic assumption verification identifies these hidden failures before deployment.

How do I tag code assumptions for systematic verification during development?

Tag code assumptions during development using #CRITICAL, #ASSUME, and #EDGE markers to categorize production risks, standard assumptions, and edge cases. This enables systematic verification through automated workflows and pre-commit hooks.

What is the best way to check AI-generated code for timing and concurrency issues?

Check AI-generated code for timing and concurrency issues by running an assumption verification workflow that routes critical production risks to premium AI models and standard assumptions to free models for comprehensive multi-model validation.

Can I integrate assumption verification into my existing pre-commit hooks?

Integrate assumption verification into pre-commit hooks using provided slash commands for verification, assumption inventory listing, and system testing. This automates validation of recently changed files directly within your development workflow.

When should I use multi-model verification for production code risks?

Use multi-model verification for production code risks when validating critical assumptions that could cause catastrophic failures under real-world conditions. Route critical production risks to premium models and standard edge case assumptions to free models for cost-effective validation.