← ClaudeAtlas

noteslisted

Implementation notes — log significant deviations from the plan while working. Use automatically when implementation hits an unknown the plan did not cover, and on "implementation notes", "record a deviation", "where did we diverge from the plan?".
ajitta/know-your-unknowns · ★ 1 · AI & Automation · score 77
Install: claude install-skill ajitta/know-your-unknowns
# Notes — Plan Deviation Log (Implementation Notes) When work hits a situation not in plan/spec (unknown), **do not decide arbitrarily and pass silently — log it**. Core device stopping agent from silently drifting off-plan. Origin: Implementation Notes — see skills/loop/references/talk-source.md. ## File Rules - Location: `IMPLEMENTATION_NOTES.md` at project root (create if missing). No project root but file writes work (Desktop/web chat, Cowork without a folder) → keep the same file in the session workspace and hand it to the user at every wrap-up. Nothing writable (mobile) → keep the log in the conversation, restated in full each time it grows. Either way the entry format and the escalation rule are unchanged. Details: skills/loop/references/surfaces.md - **Persistence**: once the file exists or `init` has been run, appending to the file is mandatory — a chat-only summary does not satisfy the rule (the reminder hook, buy-in and quiz all read the file). With no file, a chat summary is allowed, but the final message must then say there is no notes file, and where it lives instead. - **No reminder hook** in this session (hooks run only in Claude Code and Cowork) → re-read the logging criteria yourself at every natural break: before a commit, before handing work back, after roughly ten file edits. - Argument `init`: create the file — heading `# Implementation Notes — plan deviation log`, then a commented-out copy of Entry Format as the template. Then offer (never