behavioral-proof

Select proportionate evidence for material behavior changes and bug fixes.

2|Updated May 5, 2026
One-click install
npx skills add https://github.com/OrestesK/pi --skill behavioral-proof
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: behavioral-proof
Source: https://github.com/OrestesK/pi/tree/main/skills/behavioral-proof
Command: npx skills add https://github.com/OrestesK/pi --skill behavioral-proof

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents disproportionate or ineffective testing by helping you choose evidence that directly proves the observable behavior being changed.

Core Features & Use Cases

  • Evidence Selection: Choose among test-first, characterization, reproduction, existing coverage, integration, live, or manual proof.
  • Risk-Based Verification: Match evidence to the behavior boundary, canonical owner, and potential regression risk.
  • Verification Reporting: Document the changed claim, exercised files or flows, commands and results, broader checks, and unavailable boundaries.
  • Use Case: When fixing a production bug, establish the root cause, capture a narrow reproduction, verify the canonical fix, and run broader checks only when shared risk justifies them.

Quick Start

Use the behavioral-proof skill to select and document the smallest reliable evidence plan for the behavior change I am about to make.

Frequently Asked Questions about behavioral-proof

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

FAQPage Schema
How do I choose the right integration testing strategy for a behavior change?

Integration testing strategy for a behavior change requires selecting proportionate evidence that directly proves the observable claim. You match the proof method to the behavior boundary, identify the canonical owner, and run focused verification before broader checks.

What is the best way to verify regression proof for legacy code changes?

Regression proof for legacy code changes involves capturing a narrow reproduction of the root cause, verifying the canonical fix, and running broader checks only when shared regression risk justifies them. It prioritizes evidence that proves the observable behavior being changed.

When do I need characterization testing for bug fixes?

Characterization testing for bug fixes is needed when establishing the root cause of a production issue. You capture the existing behavior as a baseline, verify the canonical fix against that boundary, and document any unavailable boundaries that prevent broader validation.

Does test strategy need to cover non-behavioral work and runtime boundaries?

Test strategy must cover non-behavioral work and runtime boundaries when they require validation. You identify the observable claim, select an appropriate proof method, execute focused verification, and document any unavailable boundary that limits broader checks.

How do I document verification reporting for integration testing?

Verification reporting for integration testing documents the changed claim, exercised files or flows, commands and results, broader checks, and unavailable boundaries. It ensures the selected evidence directly proves the observable behavior change and its associated regression risk.