implementation-logger

# Implementation Logger ## When to Use Use this skill **during implementation** when: - Working on complex or uncertain changes - The implementation approach isn't fully defined - You want to track decisions for documentation - Building knowledge about unknowns for future work - Need to explain reasoning in PR descriptions ## What It Does Tracks **deviations from the original plan** and **decision rationale** during implementation. Helps identify where your mental model (map) differed from reality (territory). ## How to Execute ### Step 1: Set Up Logging At the start of implementation, create a log file: ```bash # Create implementation log echo "# Implementation Log: [Feature Name]" > .implementation-log.md echo "" >> .implementation-log.md echo "Started: $(date)" >> .implementation-log.md echo "" >> .implementation-log.md echo "## Original Plan" >> .implementation-log.md echo "[Brief summary of approach]" >> .implementation-log.md echo "" >> .implementation-log.md echo "## Deviations & Decisions" >> .implementation-log.md ``` ### Step 2: Log During Implementation Whenever reality differs from plan, log it: ```markdown ### [Timestamp] - [Decision Point Title] **Context**: What I encountered that wasn't in the plan **Original Assumption**: What I thought would work **Reality**: What I actually found **Decision**: What I decided to do instead **Rationale**: Why this approach is better/necessary **Impact**: What else this might affect ``` ### Step 3: Log Catego...