endurance-coach-research-methodologylisted

Load this when turning a hunch or observation into an accepted result in the Endurance Coach repo: "how do we turn a hunch into a claim", "what is the evidence bar here", "should this ship as confirmed or exploratory", "pre-register this", "run an adversarial review", "assign a skeptic", "is this a real signal or noise", "idea lifecycle", "how do we promote an experiment", "how do we retire a feature we cut", "should this go behind a flag", "priors vs this athlete's data", "why did we cut the change-point detector", or any decision about whether a finding, prior, detector, or coaching rule has earned adoption. This skill owns the DISCIPLINE (the evidence bar, the pre-registration rule, the idea-lifecycle state machine, where good ideas come from, the priors-yield-to-n=1 doctrine). It does NOT own the statistical derivations (see endurance-coach-proof-and-analysis-toolkit), the step-by-step campaign to validate one detector (see endurance-coach-n1-validation-campaign), the open research problems (see endurance
maxeskell/personal-training-app · ★ 0 · AI & Automation · score 70

Install: claude install-skill maxeskell/personal-training-app

# Endurance Coach — research methodology (the discipline that makes a result trustworthy) **Use this when** you are deciding whether an observation, correlation, detector, prior, or coaching rule has *earned belief* — turning a hunch into an accepted result, deciding "confirmed vs exploratory", pre-registering an analysis, running an adversarial review, or promoting/retiring an experiment. **Don't use this when** you want: - the **maths** behind a method (Fisher-z CI, Bonferroni-before-BH, permutation null) → `endurance-coach-proof-and-analysis-toolkit` - the **executable go/no-go campaign** to validate one detector with exact commands → `endurance-coach-n1-validation-campaign` - the **open research problems** to pursue → `endurance-coach-research-frontier` - the **test suite / CI / acceptance-threshold mechanics** → `endurance-coach-validation-and-qa` - the **change gate / definition-of-done / ship flow** that actually merges the result → `endurance-coach-change-control` - the **flag-plumbing details** (which env var, where parsed) → `endurance-coach-config-and-flags` This skill is the *epistemics*: the rules for what counts as knowing, not the code for computing it. --- ## 0. Terms defined once (zero-context reader) | Term | Meaning here | |---|---| | **n=1** | one athlete. All findings are about *this* person's data, not a population. Small samples, big individual variation — the whole reason for the rigour below. | | **Prior** | a general finding from published spor