Record context
Start with the environment, including system versions, tool versions, goals, and constraints. A conclusion without context is hard to reuse.
Keep key steps
The note does not need every click, but it should keep the key commands, configuration locations, and verification method.
Write a clear conclusion
Each note should leave at least one actionable conclusion: what solution was chosen, why another one was not used, and what risks remain.
Revise regularly
Technical notes expire. When a version changes or a conclusion becomes invalid, update the note directly and record the reason when needed.