session-begin

Environment validation and context loading for AI work sessions are handled by reading SESSION_CONTEXT.md, checking the current branch, and surfacing hook warnings before proceeding. This pre-flight process ensures blockers and goals are identified upfront.

A pre-flight checklist for session initialization orients your workspace by loading context, validating the environment, and surfacing warnings. It prevents duplicate work and ensures the session starts with a structured goal-selection prompt.

Checking blockers and tracking session count is done by reading SESSION_CONTEXT.md to determine project status and goals. The session counter is incremented automatically, announcing the start while surfacing any hook-state warnings.

Environment validation and hook-state checks apply to initial AI work sessions across projects. The pre-flight setup validates the current branch and working state universally, requiring no project-specific dependencies to function.

The best way to structure goal selection after loading session context is through a pre-flight checklist that presents structured goals for the next work phase. This approach hands off to the user with next-step prompts after warnings are surfaced.

Session context loading requires validating the current branch and working state before proceeding. If the environment validation fails, the pre-flight checklist surfaces warnings and blockers from SESSION_CONTEXT.md to prevent starting in an unclean state.