Documentation
README
Create Notes
A good note answers three questions a future agent will actually ask:
- What did you do, and what happened? (concrete numbers, not adjectives)
- Why did it happen that way? (the mechanism, not just the result)
- 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.
This is the opening of the README. Read the full README on GitHub.