preflight

Load project context and validate workspace readiness from status files and git.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/LadderChaos/tora-skills --skill preflight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preflight
Source: https://github.com/LadderChaos/tora-skills/tree/main/preflight
Command: npx skills add https://github.com/LadderChaos/tora-skills --skill preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the initial context load and validation of a clean workspace at the start of a development session, reducing surprises and misaligned work.

Core Features & Use Cases

  • Load context and apply project state to the current workspace.
  • Validate status files (lessons, STATUS.md, DECISIONS.md) and detect uncommitted changes.
  • Provide a concise readiness summary to inform next steps.
  • Guard deployment tasks by early checks.

Quick Start

Use preflight at the start of a development session to load context, check for stale state, and prepare for deployment tasks.

  • Review lessons and project status to confirm readiness by inspecting ./.claude/rules/lessons.md and STATUS.md.
  • Check decisions and uncommitted changes to avoid surprises before starting work.

Frequently Asked Questions about preflight

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate project status and load context at the start of a development session?

To validate project status at session start, the preflight skill automates loading context by checking critical files like lessons, STATUS.md, DECISIONS.md, and git status to determine readiness and surface any stale state.

What is the best way to check for blockers and uncommitted changes before deploying?

To check for blockers before deploying, use preflight to guard deployment tasks by early checks, verifying status files and detecting uncommitted changes to provide a concise readiness summary and avoid surprises.

How do I automatically surface stale state and project blockers after a long break?

To surface stale state after a long break, preflight applies automated context loading to inspect critical project files and git status, identifying blockers and guiding subsequent actions to realign your workspace.

Do I need specific status files like STATUS.md or DECISIONS.md to run a workspace readiness check?

Yes, preflight validates workspace readiness by inspecting specific status files including STATUS.md, DECISIONS.md, and lessons, using them to detect uncommitted changes and confirm project alignment.

Can I use preflight to load project context without manually running git status commands?

Yes, preflight automates the initial context load and checks git status automatically, applying project state to the current workspace and providing a readiness summary without manual git commands.

Why does my development workflow need a session start context loading check?

A session start context loading check reduces surprises and misaligned work by validating a clean workspace, ensuring that stale state, blockers, and uncommitted changes are surfaced before development begins.