logmind: log decisions as you work

If the current project contains .logmind/config.yml or its AGENTS.md mentions logmind, this skill applies. Log a decision before writing non-trivial code, not after.

When to log

Log a decision whenever you:

• Make an architectural or design choice
• Choose between alternative approaches
• Write significant new code (> 20 lines or a new module)
• Modify existing functionality in a non-obvious way
• Add or remove a dependency
• Make a security or performance decision

When in doubt, log it. A short decision entry is cheap; recovering missing context months later is not.