implementation-notes
Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case. Use whenever implementing against an agreed plan or spec, especially in long autonomous sessions.
npx skills add Neeeophytee/finding-unknowns-skills --skill implementation-notes --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Implementation notes No amount of planning removes every unknown; some only appear once the code is open. When the territory disagrees with the plan, don't stop and don't silently improvise — take the conservative option, write it down, and keep going. The notes file is how the next attempt learns from this one. ## Steps 1. At the start of the build, create `implementation-notes.md` with three headings: **Deviations**, **Discovered edge cases**, **Questions for review**. 2. Whenever reality forces a choice the plan didn't cover: - pick the conservative option (the one that's easiest to reverse), - log it under Deviations: what the plan said, what was done instead, why, and what it would take to revisit, - continue working. Do not block on the user for reversible decisions. 3. Log edge cases as they're found, even ones handled cleanly — they are exactly the unknowns the next plan should account for. 4. Anything irreversible or scope-changing goes under Questions for review AND stops the work at a safe checkpoint. Deviating conservatively is fine; deviating expensively needs a human. 5. At the end, append a five-line summary: deviations count, the one most likely to be revisited, e
- Steps
- Guardrails
What does the implementation-notes skill do?
Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case. Use whenever implementing against an agreed plan or spec, especially in long autonomous sessions.
How do I install it?
Run `npx skills add Neeeophytee/finding-unknowns-skills --skill implementation-notes --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Neeeophytee/finding-unknowns-skills, a repository with 298 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.