preflight

Validate a preflight plan against the repository surface for mismatches.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/saajunaid/junai --skill preflight-saajunaid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preflight
Source: https://github.com/saajunaid/junai/tree/main/.github/skills/workflow/preflight
Command: npx skills add https://github.com/saajunaid/junai --skill preflight-saajunaid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan-vs-codebase validation detects mismatches between a proposed project plan and the actual repository surface to prevent wasted engineering effort.

Core Features & Use Cases

  • Systematic validation across 8 check categories (API contract, type identity, field accuracy, dependencies, path existence, data shape, transform correctness, output decay) to ensure alignment before implementation.
  • Structured, multi-pass methodology that records findings and surfaces actionable fixes, helping teams de-risk plan execution.
  • Flexible usage during planning, gating, onboarding, and mid-implementation to re-validate as the codebase evolves.

Quick Start

Run the preflight plan against your repository to surface API, type, and path discrepancies before coding begins.

Frequently Asked Questions about preflight

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

FAQPage Schema
How do I validate a project plan against my codebase before implementation?

You can validate a plan against your repository surface using a preflight check, which requires the plan document and read access to the codebase. It systematically verifies API contracts, types, field names, dependencies, and file paths to prevent wasted engineering work.

What is plan-vs-codebase validation and when should I use it?

Plan-vs-codebase validation detects mismatches between a proposed plan and the actual repository. Apply this validation during planning, gating, onboarding, and mid-implementation to verify API contracts, types, dependencies, and file paths before executing the plan.

Can I check for API contract and type mismatches mid-implementation?

Yes, you can check for API contract and type mismatches mid-implementation by re-running preflight validation against the codebase. This de-risks plan execution by verifying data shapes, dependencies, and type identity as the repository evolves.

What categories does codebase validation cover to prevent wasted engineering work?

Codebase validation covers eight systematic check categories: API contract, type identity, field accuracy, dependencies, path existence, data shape, transform correctness, and output decay. It records findings and surfaces actionable fixes to prevent wasted engineering effort.

What do I need to provide to run a preflight check on my repository?

To run a preflight check, you need to provide the plan document and grant read access to the repository. The validation tool then reports findings with severity classifications and recommended fixes across API, type, and path discrepancies.