← ClaudeAtlas

to-doclisted

Turn the current conversation into an experiment doc (hypothesis, premises, baseline, success metrics, experiment stories) and publish it to the project docs, with no new interview. Use after /hypothesys, or when the user says 'write the experiment doc', 'document this experiment' or 'turn this into a doc'.
samuhs/mad-science · ★ 3 · AI & Automation · score 80
Install: claude install-skill samuhs/mad-science
This skill takes the current conversation context and codebase understanding and produces documentation. Do NOT interview the user; just synthesize what you already know. ## Process 1- Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the docs. 2- Sketch out the validation checkpoints at which you're going to evaluate the experiment. Existing pipeline splits and validation metrics should be preferred to new ones. Evaluate at the highest level possible (e.g., end-to-end model performance or business metrics). If new checkpoints are needed, propose them at the highest point you can in the pipeline. The fewer disjointed evaluation scripts across the workflow, the better - the ideal number is one unified evaluation step. Check with the user that these seams match their expectations. 3- Write the doc using the template below, then publish it to the project documentation. ## Hypothesis The hypothesis that the user is facing, from the user's or business's perspective. ## Premises The premises to the problem and the underlying assumptions, from the user's perspective. ## Baseline & Current State What the experiment is trying to beat. Describe the current environment, whether it is an existing model, a manual human process, or hardcoded business rules (e.g., "if score > 50, approve"). ## Success Metrics & Goals The exact definition of how success will be measured. This should be d