agent-impl-notes-loglisted

# Agent Implementation Notes — Running Log ## Purpose The phase meeting log (`meetings/{date}_{topic}.md`) is summative — written after work completes. By that point, dozens of micro-decisions made mid-flight are already lost to the commit diff. An impl-notes log fills that gap: a **concurrent record** of decisions, deviations, tradeoffs, and unresolved questions, written as they happen. The user explicitly asked for this: > 在你進行工作的同時，維護一個名為 implementation-notes.md 的持續更新檔案，記錄任何我應該知道的，關於實作如何偏離或詮釋規格的事項。 ## When to invoke Subagent MUST invoke this skill at the start of any dispatch matching ANY of: - Touches more than 3 files in production code. - Implements behavior whose spec has known ambiguity (e.g., `// UNCONFIRMED` markers, "Unconfirmed ?" prerequisites). - Introduces a new dependency, target, or module. - Refactors existing code beyond a one-line fix. - Any task with a `PROPOSAL_DRAFT` step in the AI Collaboration Mode workflow. Subagent MAY skip this skill for trivial one-line fixes, pure typo corrections, or documentation copy edits. ## File layout Path: `meetings/{YYYY-MM-DD}_{topic}.impl-notes.md` Paired naming with the phase meeting log. If the phase log is `meetings/2026-05-20_phase-11-foo.md`, the impl-notes is `meetings/2026-05-20_phase-11-foo.impl-notes.md`. If multiple subagents work on the same topic on the same day, append a numeric suffix: `meetings/2026-05-20_topic.impl-notes.2.md`. ## File format ```markdown # Impl Notes — {topic} ({date}) St