slice-stress-test

Generate 20 boundary stress-test scenarios for CALLSHEET slices against interface specs.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Rwb3n/callsheet --skill slice-stress-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slice-stress-test
Source: https://github.com/Rwb3n/callsheet/tree/main/.claude/skills/slice-stress-test
Command: npx skills add https://github.com/Rwb3n/callsheet --skill slice-stress-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stress-testing CALLSHEET slices against upstream interface specifications to identify gaps, ambiguities, and boundary risks before deployment.

Core Features & Use Cases

  • Generate 20 boundary scenarios across the interfaces a slice touches.
  • Produce structured findings with severity, references, and actionable fix instructions.
  • Verify downstream flag resolutions and schema consistency by comparing against prior findings.
  • Use case: validate a new slice's resilience and compatibility with partner specs.

Quick Start

Invoke the stress-test workflow on your target slice to generate 20 boundary scenarios and review the findings.

Frequently Asked Questions about slice-stress-test

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

FAQPage Schema
How do I stress-test API slices against upstream interface specs?

Boundary stress testing targets gaps, ambiguities, and correctness risks at the slice/interface boundary. It verifies downstream flag resolutions and schema consistency by comparing slices against upstream interface specs and prior findings to ensure compatibility.

What is the best way to find interface ambiguities in a CALLSHEET slice?

Generating a 20-scenario boundary stress test is the best way to find interface ambiguities. It targets correctness risks across all touched interfaces and produces structured findings complete with severity, references, and actionable fix instructions.

How do I verify downstream flag resolutions and schema consistency?

Verify downstream flag resolutions and schema consistency by comparing your slice against prior findings. This cross-reference ensures accurate flag resolution and validates that your interface specs align correctly during boundary stress testing.

Do I need prior findings to run a boundary stress test on a slice?

Yes, prior findings are required to run a boundary stress test. Access to prior findings ensures accurate cross-reference, scenario formatting, and flag resolution when validating the slice content against upstream interface specifications.

What limitations exist when stress-testing CALLSHEET slices against interface specs?

A key limitation is the requirement for complete input data. Accurate cross-reference and scenario formatting require full access to slice content, interface specs, and prior findings, meaning incomplete upstream documentation will limit boundary test coverage.