create-notes

# Create Notes A good note answers three questions a future agent will actually ask: 1. **What did you do, and what happened?** (concrete numbers, not adjectives) 2. **Why did it happen that way?** (the mechanism, not just the result) 3. **What should I do — or not do — given this?** (ordered next steps + things you tried that failed) A bad note is a wall of headings with empty bodies, or a final-design pitch with no record of the alternatives you rejected. The bad pattern shows up enough that this skill exists to prevent it. ## When to Use Each heartbeat that produces a note corresponds to one variant. The skill is one document, but you only need the variant your current trigger asks for. | Triggered by | Variant | File location | |---|---|---| | `reflect` heartbeat after each eval | **Experiment note** (Variant A) | `notes/experiments/eval-<N>-<slug>.md` | | `pivot` plateau detection | **Focus note** (Variant C) | `notes/focus/focus-<topic>.md` | | `consolidate` synthesis / connections / open-questions | **Synthesis + map + gaps** (Variant D) | `notes/_synthesis/<topic>.md`, `notes/_connections.md`, `notes/_open-questions.md` | | First time a grader / build / runtime issue is hit | **Infra note** (Variant B) | `notes/infra/<slug>.md` (or `notes/<slug>.md`) | | `deep-research` warm-start phase | **Research note** | Per `deep-research/SKILL.md` (not duplicated here) | If you are about to `Write` any file under `notes/`, stop and use this skill first — even if the promp...