note-it

# Implementation Notes After completing implementation and review/fix for an Issue, capture a running implementation notes file that documents how the implementation diverges from or interprets the spec. ## Triggers Use when: - After `/goal` implementation and `/review-it` are both complete - User says "记录笔记", "implementation notes", "note-it", "/note-it" - Before `/ship-it` (as a final checkpoint) - Any time the user wants to capture design rationale ## The Job 1. Determine the Issue number from context (branch name, `/goal` target, or user input) 2. Review the implementation against the Issue spec / PRD 3. Generate an HTML notes file at `docs/issue#XXXX.html` 4. Present a summary to the user ## Notes Structure The HTML file must cover these four categories. If a category has nothing to report, write "None" with a brief explanation. ### 1. Design Decisions Choices made where the spec was ambiguous or silent: - What was the ambiguity? - What choice did you make? - What was the rationale? ### 2. Deviations Places where you intentionally departed from the spec: - What did the spec say? - What did you implement instead? - Why was the deviation necessary or better? ### 3. Tradeoffs Alternatives you considered and why you picked what you did: - What were the viable alternatives? - What were the pros/cons of each? - Why did the chosen approach win? ### 4. Open Questions Anything you'd want confirmed or revised: - What assumption are you unsure about? - What should the us...