EDD Experiment Skill
When to Use
Activate when the user wants to:
- •Try multiple approaches to solve a tricky problem
- •Document experimental iterations with structured learnings
- •Run an experiment-driven development workflow
User Preferences
- •Check for
.github/copilot-preferences.ymlor.vscode/copilot-preferences.ymlfor custom experiment conventions.
Steps
- •Create or update
experiments/YYYY-MM-DD-<slug>.md. - •For each attempt:
- •PLAN → what will be tried and why
- •Patch (diff) → the code change
- •Verify (commands or TODOs) → how to validate
- •Result → what happened
- •Learnings → what was learned
- •Next Step → what to try next
- •Stop after two failed attempts without new info; add one question to the issue's
## Missingand stop. - •Print a change summary.
Guardrails
- •Do not call CLIs or the network.
- •Document every attempt — never silently discard a failed experiment.
- •Stop early if stuck rather than repeating the same approach.