Running Log

To persist ideas across sessions, you need a structured running log that captures consultations and process memory, enabling cross-session learning. This skill organizes entries with timestamps, tags, and cross-entry linking to retain reasoning over time.

You can capture a quick idea by typing /idea followed by a one-line description. This triggers the human quick-capture workflow, immediately saving your thought as a structured entry into the persistent backlog for later review.

Yes, AI auto-detection works during interactions to identify and log decisions automatically. It captures process memories into the structured backlog using deterministic entry fields and auto-tagging without requiring manual commands from the user.

The best way to review a cross-session decision backlog is using a librarian-backed review process. By running /review-backlog, you surface insights through post-processing links that connect related entries across your structured log history.

Yes, this cross-session memory log works for engineering teams and product development. It helps knowledge workers retain reasoning and decisions in a self-organizing backlog, ensuring structured context is preserved across collaborative project sessions.