pre-flight

Name: pre-flight
Availability: InStock
Author: gerardloupecyb

Assess architectural, security, and performance risks in GSD plans before execution.

Updated Mar 1, 2026

Search Tags:#architecture #performance #security #edge-cases #preflight #plan-review #gsd

Ready to run

npx skills add https://github.com/gerardloupecyb/claude-code-project-template --skill pre-flight-gerardloupecyb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pre-flight
Source: https://github.com/gerardloupecyb/claude-code-project-template/tree/main/.claude/skills/pre-flight
Command: npx skills add https://github.com/gerardloupecyb/claude-code-project-template --skill pre-flight-gerardloupecyb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-flight enables multi-agent review of GSD plans before execution, surfacing architecture, security, and performance risks to prevent flawed deployments and missed user flows.

Core Features & Use Cases

Parallel, four-agent analysis (Architecture Strategist, Security Sentinel, Performance Oracle, Spec Flow Analyzer) against PLAN.md, REQUIREMENTS.md, and related context to catch design flaws before coding.
Ensures comprehensive coverage of component boundaries, security gaps, data handling, and user-flow completeness, including edge cases and failure paths.
Use Case: A team reviews a new plan phase to surface architectural anti-patterns, authentication gaps, and performance bottlenecks prior to execution, reducing investigation time later.

Quick Start

Run a pre-flight review on the current PLAN.md to validate architecture, security, and user flows before execution.

Frequently Asked Questions about pre-flight

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

FAQPage Schema

How do I review a software architecture plan for security and performance risks before coding?▼

Plan review for security and performance risks involves analyzing PLAN.md and REQUIREMENTS.md to identify architectural anti-patterns, authentication gaps, and bottlenecks. Multi-agent pre-flight assessments evaluate component boundaries, data handling, and user-flow completeness prior to execution.

What is a pre-flight plan review and when do I need it?▼

A pre-flight plan review is a multi-agent analysis that surfaces architecture, security, and performance risks in GSD plans before execution. You need it when validating design boundaries, data handling, and user flows to prevent flawed deployments and reduce investigation time later.

How do I check my REQUIREMENTS.md for edge cases and failure paths?▼

Checking REQUIREMENTS.md for edge cases and failure paths requires evaluating spec flow completeness across user journeys. A spec flow analyzer reviews related context to catch potential user-flow issues, ensuring comprehensive coverage of failure paths before coding begins.

Can I assess architecture boundaries and data handling gaps in PLAN.md without writing code?▼

Yes, you can assess architecture boundaries and data handling gaps in PLAN.md before writing code. Parallel agent analysis evaluates component boundaries, security gaps, and data handling protocols directly against the plan, catching design flaws early in the development lifecycle.

What's the best way to catch authentication gaps and performance bottlenecks in a new plan phase?▼

The best way to catch authentication gaps and performance bottlenecks is running a parallel four-agent review on the new plan phase. This coordinates architecture, security, performance, and spec flow analysis against PLAN.md to surface risks prior to execution.

Why does my deployment fail due to missed user flows and design flaws?▼

Deployments fail due to missed user flows and design flaws when plans lack pre-execution review. Running a multi-agent pre-flight assessment on PLAN.md surfaces architectural anti-patterns, security gaps, and incomplete user flows, preventing flawed deployments before coding starts.