nexus-phase-preflight

Analyze SBFB phases against historical decisions, threat models, and wire format invariants.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/SBFB50/SBFB --skill nexus-phase-preflight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nexus-phase-preflight
Source: https://github.com/SBFB50/SBFB/tree/main/.claude/skills/nexus-phase-preflight
Command: npx skills add https://github.com/SBFB50/SBFB --skill nexus-phase-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a pre-implementation factual evolution check for SBFB phases, ensuring that the design aligns with historical decisions, threat models, and wire format invariants before coding begins.

Core Features & Use Cases

  • Factual Evolution Check: Runs four scans (S1 SOTA delta, S2 historical decisions, S3 threat model coverage, S4 wire format invariants) to emit a verdict.
  • Documentation Generation: Outputs a sprint-specific preflight document or pivot proposal based on the verdict.
  • Use Case: Before writing the first code line of a SBFB phase, run the nexus-phase-preflight skill to validate the design and avoid potential conflicts.

Quick Start

Run the 'preflight phase X' command to initiate the preflight check for phase X.

Frequently Asked Questions about nexus-phase-preflight

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

FAQPage Schema
What is a pre-implementation factual check for software design?

It validates a software design against historical decisions, threat models, and wire format invariants before coding begins, ensuring alignment and preventing potential conflicts.

How do I validate threat model coverage before starting to code a new phase?

Run a preflight check to scan threat model coverage alongside SOTA deltas, historical decisions, and wire format invariants, emitting a readiness verdict for the phase.

Does the preflight design review require access to planning documents?

Yes, the preflight design review requires access to SBFB planning documents and related memories to analyze historical data and output a phase readiness verdict.

How do I generate a sprint-specific preflight document for phase validation?

Execute the preflight command for the target phase to run four factual scans, which outputs a sprint-specific preflight document or pivot proposal based on the verdict.

What are the limitations of running an automated phase validation check?

The phase validation check is limited by its dependency on accessible SBFB planning documents and memories; without them, it cannot perform historical or threat model analysis.