stratified-sample-scope-discipline

What problem does it solve? When a fix is proven on one system, teams often rush to apply it everywhere at once, turning a 30-minute fix into a multi-day debugging session. This Skill enforces a disciplined rollout process that prevents scope creep, limits blast radius, and ensures unsampled systems are never silently treated as verified. ## Core Features & Use Cases - Scope Declaration Templates: Provides a structured format for declaring which systems are in the sample, which are unsampled, and what stop conditions apply before any work begins. - Sample Selection Guidance: Defines criteria for choosing representative samples based on variation in complexity, branch names, size, and known issues. - Unverified Reporting: Enforces explicit UNVERIFIED marking for all unsampled systems in every status report, preventing false confidence. - Use Case: After fixing a bug in one repository, use this Skill to declare a 2-repo sample, verify the fix there, report remaining repos as UNVERIFIED, and expand only after explicit user approval. ## Quick Start Apply this fix to the other repositories using stratified sampling with a declared scope and sample before expanding.