pre-flight

To prevent context drift, load relevant context by scanning memory files for design intent, constraints, and retro lessons before initiating any non-trivial task. Compiling a concise constraint summary guides execution and keeps your workflow aligned with project goals.

Context drift occurs when execution loses alignment with original project goals. Pre-loading memory scans for design intent and past lessons before task initiation, producing a constraint summary that anchors your workflow and prevents wasted effort.

Scanning memory for design intent and constraints at task initiation or session resumption reads stored memory sources to surface retro lessons. This process produces a concise constraint summary to guide execution and maintain project alignment.

Yes, you can optionally integrate team context into your pre-flight workflow. This aligns the current task by combining team context with scanned memory sources and design intent, producing a comprehensive constraint summary.

Run pre-flight context loading before starting any non-trivial task or when resuming a session. This timing ensures memory scanning captures relevant design intent, constraints, and retro lessons to prevent drift and wasted effort.

The best way to surface design intent and constraints is running a pre-flight scan of memory sources before task execution. This automatically loads available design intent and compiles a concise constraint summary to guide your workflow.