AugmentClaude
EngineeringSpecsDocs

Implementation Notes

By Neeeophytee· Neeeophytee/finding-unknowns-skills· 0

Log deviations and edge cases discovered during development for future reference.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.
    Install
    Sign up to copy
    Sign up free to reveal

    This copies the whole skill folder into ~/.claude/skills/implementation-notes-neeeophytee/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
    Sign up free to reveal
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

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.

What this skill does

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, edge cases found, and what the next session should read first. Reference the file in the handoff or PR.

Guardrails

  • The notes file is temporary working memory, not documentation. Keep entries to 2-3 lines each.
  • Never let the notes drift from reality — an unlogged deviation is worse than no notes at all, because the file claims completeness.
  • "Conservative" means reversible, not necessarily simple.

Related skills

W

Word Document Editor

anthropics

Create, edit, and format Word documents with tables, images, and tracked changes.

OfficialProprietary. LICENSE.txt has complete terms
A

Ask Questions If Underspecified

trailofbits

Ask clarifying questions before starting work on ambiguous requests.

C

CLAUDE.md Optimizer

daymade

Optimize your CLAUDE.md file for clarity, efficiency, and maintainability.

C

Claude Skills Troubleshooter

daymade

Diagnose and fix plugin installation, enablement, and activation problems.