operation-logger

Maintain cross-session continuity for multi-file refactoring by creating a durable operation-log.md at your project root. It chronologically records sessions, operations, and running summaries, capturing every step and rationale to prevent context loss across long conversations.

Trace decisions and errors during debugging by logging into a structured operation-log.md file using DECISION, ERROR, and PLAN hooks. This provides a durable, searchable audit trail that prevents forgotten context and duplicated work across long coding sessions.

Track infrastructure migration progress by maintaining an operation-log.md with structured sections for Running Summary, Session Entries, and Operation Entries. It logs meaningful actions after they occur, providing a durable on-disk record of every step and outcome.

Yes, you can document a security review across multiple files using an operation-log.md file. By placing it at the project root, you chronologically capture every operation and decision, ensuring traceability and auditability for complex tasks spanning three or more files.

You need a dedicated operation log file for coding sessions involving multi-file refactors, migrations, debugging, or infrastructure setup. When operations scatter across long sessions, a persistent log prevents context loss, repeated work, and forgotten decisions.