What problem does it solve? Engineering teams lose valuable context when sessions end without documenting why decisions were made, what failed, and what was learned. This Skill captures honest technical reflections in structured journal entries so future developers understand the real story behind the code. ## Core Features & Use Cases - Structured Journal Entries: Delegates to a journal-writer agent that creates dated entries in plans/journals/ following a fixed format with root cause, lessons learned, and next steps. - Honest Reflection: Enforces truthful documentation including emotions and unsanitized failure descriptions, unlike tickets or status reports. - Clear Boundaries: Distinguishes journal history from the decision ledger (docs/decisions.md) and restricts writes to plans/journals/. - Use Case: After shipping a feature or fixing a production bug, invoke the skill with a topic like "webhook timeout root cause" to produce a dated entry capturing what happened, what was tried, and actionable lessons. ## Quick Start Ask the assistant to write a journal entry about the bug fix or session topic you just completed.
