rai-session-diary

What problem does it solve?

Preserve the narrative context and decision rationale of a development session so teammates and future-you understand not just what changed but why those choices were made. The diary prevents loss of tacit reasoning, documents pivots and mistakes honestly, and makes session memory actionable for follow-up work and governance.

Core Features & Use Cases

• Narrative entry authored in Rai's first-person voice that highlights opening questions, tensions, turning points, and resolutions.
• Integrates conversation context, git commits, and session artifacts to compile evidence and quotes for an accurate, reviewable record.
• Publishable to Confluence or filesystem via the docs adapter with a quality checklist and review step before publishing.
• Use case: after a design-heavy session, produce a single-page diary that explains the decision arc, includes direct developer quotes, and lists next actions for the team.

Quick Start

Ask Rai to draft and publish a session diary for the current session that summarizes the narrative arc, key decisions, and next steps.