One-click install
npx skills add https://github.com/Pyl-Tech/stream-coding --skill experiment-pyl-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: experiment
Source: https://github.com/Pyl-Tech/stream-coding/tree/main/.agents/skills/experiment
Command: npx skills add https://github.com/Pyl-Tech/stream-coding --skill experiment-pyl-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents speculative or opinion-based decisions by providing a repeatable workflow to test claims with real, falsifiable experiments.

Core Features & Use Cases

  • Hypothesis-first design: Forces decisions into falsifiable, measurable claims so outcomes can confirm or disprove the premise.
  • Controlled execution and record-keeping: Tracks control versus experiment results across cases to surface contradictions and estimate effect size.
  • Evidence-driven decision output: Produces a clear confirmation status with confidence and action guidance, including what to adopt, constrain, or reject.
  • Use cases: Architecture trade-offs (latency, cost, reliability), performance comparisons (caching/query strategies), and methodology improvements (whether a rule reduces bugs or verification bypasses).

Quick Start

Ask an AI agent to produce an experiment report for whether a proposed change improves system performance, using a falsifiable hypothesis, an explicit control baseline, and a results table across real test cases.

Frequently Asked Questions about experiment

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

FAQPage Schema
How do I use falsifiable hypotheses to resolve architecture debates?▼

Falsifiable hypotheses resolve architecture debates by structuring claims into controlled experiments that test independent and dependent variables, producing measurable evidence rather than opinion-based arguments to confirm or reject design decisions.

What is evidence-based architecture decision making?▼

Evidence-based architecture decision making replaces speculative choices by tracking control versus experiment results across real test cases, analyzing confirmation status with confidence, and producing actionable guidance on what to adopt, constrain, or reject.

How do I design a controlled experiment to evaluate performance comparisons?▼

To evaluate performance comparisons, design a controlled experiment by defining explicit control baselines and independent variables, collecting results across real test cases, and analyzing effect size to surface contradictions between caching or query strategies.

Can I use ablation testing to validate methodology improvements?▼

Yes, ablation testing validates methodology improvements by applying controlled experiments to verify whether a specific rule reduces bugs or bypasses, using documented reports to track confirmation status and confidence across tested cases.

What is the best way to report evidence for architecture trade-offs like latency and cost?▼

The best way to report evidence for architecture trade-offs is producing an experiment report that documents falsifiable hypotheses, control baselines, and a results table across real test cases to guide measurable adoption or rejection decisions.

When should I not use controlled experiments for architecture decisions?▼

Controlled experiments for architecture decisions are unsuitable when outcomes cannot be measured or when defining independent and dependent variables is impossible, as the workflow requires real test cases to estimate effect size and surface contradictions.