## Logging Throughout this entire operation, maintain a detailed log of everything that happens. At the **end** of the operation, write the full log to a file in the `logs/` directory (create it if it doesn't exist). **Log file path:** `logs/--.md` — use the skill name from this file's name (e.g. `recipe-check`, `recipe-deploy`), the recipe name from `$ARGUMENTS` (omit if there is no recipe argument), and today's date. The log file must include: - A header with the skill name, recipe name (if applicable), and timestamp - Every shell command that was run, in fenced code blocks - The full output of each command (truncate excessively long output but keep enough to be useful) - Any decisions made, errors encountered, or notable observations - The final summary/result Format the log as readable markdown with clear section headers for each step.