Session Manager

Session Manager

Overview

This skill provides a standardized initialization routine for any Gemini project. It ensures that required background skills are active and that the agent has verified access to all critical directories before beginning work.

Commands

/start_session

Performs the "Executive Boot Sequence."

Workflow:

1. Activate Background Listeners:
   • Activate git-flow-automator.
   • Activate project-maintainer.
   • Activate session-tracker.
   • Activate session-chronicler.
2. Initialize Tracking & Narrative:
   • Call /session/start to generate a session_id.
   • Initialize the Activity Log in the Daily Note using session-chronicler.
   • Cross-Link: Ensure the session_id is included in the first Chronicler log entry, and the Daily Note link is added to the session manifest.
3. Verify Directory Access (Guard):
   • Logic: The agent reads the required directory list from the project's GEMINI.md or a provided configuration.
   • User Check: For this specific vault, verify access to:
     • Infrastructure
     • Meta
     • Vault
     • Skills
   • Prompt: If any directory is missing, inform the user and provide the instruction needed to load them.
4. Context Warm-up:
   • Read the project's primary TODO file (meta/PROJECT_TODO.md or README.md).
   • Read the most recent history entries (e.g., meta/SESSION_FLIGHT_RECORDER.md).
5. Initialize Session Log:
   • Create a "Session Started" entry in the flight recorder.
   • Capture the current Git state (SHA) if available.
6. Present Briefing:
   • Provide a concise "Welcome Back" summary:
     • "Current Goal: [Goal]"
     • "Last Action: [Action]"
     • "Status: Environment Verified."

Workflow & Constraints

• MANDATORY START: This command should be the very first action taken in a new session.
• PROACTIVE REMINDERS: If the agent detects it's a new session but /start_session hasn't been run, it MUST prompt the user to execute it.