mode-preflight

Validate proposal facts through three verification passes and output a GO or NO-GO verdict.

3|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/benegessarit/skill-composer --skill mode-preflight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mode-preflight
Source: https://github.com/benegessarit/skill-composer/tree/main/skills/mode-preflight
Command: npx skills add https://github.com/benegessarit/skill-composer --skill mode-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triple-checks proposals and claims before execution to prevent costly mistakes and missteps when acting on a prompt or plan.

Core Features & Use Cases

  • Pass 1: FACTS — Verify every factual claim in the proposal and record sources.
  • Pass 2: GAPS — Identify unverified assumptions, missing files or edge cases, and trace dependencies.
  • Pass 3: BLAST RADIUS — Assess consequences, rollback complexity, and safety implications if a claim is wrong.
  • PREFLIGHT VERDICT — Produce a GO or NO-GO decision with a concise rationale and next steps.

Quick Start

Submit a proposal and let the preflight mode return a GO or NO-GO verdict with a concise justification.

Frequently Asked Questions about mode-preflight

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

FAQPage Schema
How do I verify factual claims in a proposal before deployment?

To verify factual claims, you run a structured preflight workflow that checks proposal facts, identifies missing dependencies, and assesses blast radius to produce a GO or NO-GO verdict before deployment.

What is preflight verification for policy changes and major design decisions?

Preflight verification is a three-pass quality-assurance process that validates facts, identifies unverified assumptions, and assesses blast radius to prevent costly mistakes during policy changes or major design decisions.

How do I assess the blast radius and rollback complexity of a proposed plan?

Assess blast radius by applying Pass 3 of the preflight workflow, which evaluates consequences, rollback complexity, and safety implications if a proposal claim is wrong, resulting in a safer go-no-go decision.

How do I identify unverified assumptions and missing edge cases in a deployment plan?

Identify unverified assumptions and missing edge cases by running Pass 2 of the preflight workflow, which traces dependencies and highlights gaps in the proposal to ensure no hidden risks remain before execution.

When should I use a go-no-go decision workflow for prompt execution?

Use a go-no-go decision workflow when executing without thorough checks is risky or expensive, such as during deployments or major design decisions, to enforce structured verification and prevent costly missteps.