preflight

Validate tooling and onboarding readiness before Pulse runs, writing status artifacts.

Updated Mar 27, 2026

Search Tags:#automation #onboarding #tooling #readiness #preflight #gating #pulse

Ready to run

npx skills add https://github.com/quanpersie2001/pulse --skill preflight-quanpersie2001

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: preflight
Source: https://github.com/quanpersie2001/pulse/tree/main/plugins/pulse/skills/preflight
Command: npx skills add https://github.com/quanpersie2001/pulse --skill preflight-quanpersie2001

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Pulse workflows stall when tooling readiness and onboarding state block planning or execution; preflight provides a gate to verify these prerequisites before any work begins.

Core Features & Use Cases

Verifies core tooling availability (git, br, bv) and onboarding state for the current repo.
Writes artifacts such as .pulse/tooling-status.json and updates .pulse/STATE.md to reflect the latest preflight result.
Enforces one of three outcomes (PASS, DEGRADED, or FAIL) and surfaces the next step via pulse:using-pulse when ready.

Quick Start

Run the preflight skill before starting or resuming Pulse to validate tooling and onboarding readiness.

Frequently Asked Questions about preflight

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

FAQPage Schema

How do I validate tooling readiness before starting a Pulse planning session?▼

Preflight validates runtime readiness by checking core tooling availability such as git, br, and bv before a Pulse run. It enforces an outcome of PASS, DEGRADED, or FAIL to prevent execution stalls caused by missing prerequisites.

What happens when preflight tooling validation fails or detects a degraded state?▼

When preflight validation fails or detects a degraded state, it enforces a FAIL or DEGRADED outcome and surfaces a recommended next step. It writes the specific blocking conditions to a tooling status file to guide resolution before execution can proceed.

Do I need to run preflight checks every time I resume a Pulse session?▼

Yes, you should run preflight checks during any session resume or pre-execution phase. This verifies that onboarding state and tooling availability have not changed, preventing blocked progress when resuming Pulse planning or execution workflows.

What state files are generated when checking onboarding and tooling readiness?▼

Checking onboarding and tooling readiness generates a .pulse/tooling-status.json file capturing validation details and updates .pulse/STATE.md to reflect the latest preflight result. These artifacts track readiness across Pulse runs.

Why does my Pulse workflow stall during execution despite prior setup?▼

Pulse workflows stall when tooling readiness and onboarding state block planning or execution. Running a preflight gate beforehand validates these prerequisites, enforcing a PASS, DEGRADED, or FAIL state to surface blocking issues early.