preregisterlisted

# Preregistration A preregistration is a written commitment to hypotheses, design, and analysis made before the data exist or before the realized focal outcome has been seen. It separates confirmatory from exploratory work and closes off p-hacking, HARKing, and forking paths. This skill writes the document; the user submits it. To critique a preregistration that already exists, use the council skill; this one drafts. Structure and the MUST/SHOULD/MAY taxonomy adapted from `pedrohcgs/claude-code-my-workflow`. ## The refusal gate Check this before reading anything else, and check it again if new information arrives mid-draft. Refuse if the description contains realized results: "we found", "the estimate is", "p =", "the effect was significant", "condition A scored higher", a coefficient, a sample mean, or a figure of results. Say plainly that a preregistration is forward-looking, that writing one now would misrepresent the analysis order, and offer instead to write it up as an exploratory analysis or a methods section, clearly labeled as such. Refuse in the same way if the user has run the focal analysis on data they hold, even without stating the numbers. The gate is about analysis order, not about whether numbers appear in the prompt. Ask directly: has the focal outcome been analyzed on these data yet? If the answer is yes or evasive, do not write a preregistration. Two things are not refusals. Preregistering a new confirmatory test on data the user holds but has not e