preflight

Detects and installs optional enrichment tooling for codebase audits before they run.

3|5|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill preflight-bensheridanedwards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preflight
Source: https://github.com/BenSheridanEdwards/ArchitectPlaybook/tree/main/preflight
Command: npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill preflight-bensheridanedwards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a codebase audit only to discover that its optional enrichment tooling (bundle analyzers, Lighthouse, security lint plugins) is missing wastes an entire audit cycle. This Skill consolidates that discovery into one pre-audit readiness check, reporting which development dependencies and configuration files each audit needs, and optionally installing or scaffolding them with explicit prompts. ## Core Features & Use Cases - Read-only status detection: Prints a sorted status table (missing, installed-but-not-wired, built-in, present) for every audit enrichment flag, covering bundle-build, typescript, testing, dependency, performance, security, and linting audits. - Gated mutation: Installs missing development dependencies with --install and scaffolds minimal configuration files with --scaffold-configs, prompting before every change and refusing to run in CI environments. - Findings artefacts: Writes findings.md, findings.json, and metadata.json to .architect-audits/preflight/ following the playbook's findings-file contract. - Use Case: Before launching parallel security and performance audits on a new client repository, run the preflight check to confirm eslint-plugin-security and lighthouse are installed and wired, then install whatever is missing in one pass. ## Quick Start Run the preflight check on my project to report which audit enrichment tools are missing, then install them with prompts.

Frequently Asked Questions about preflight

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

FAQPage Schema
How do I check which audit dependencies are missing in my project?

Run the preflight check in its default read-only mode. It scans your package.json and configuration files, then prints a status table sorted with missing dependencies first, covering bundle analyzers, Lighthouse, security ESLint plugins, and test coverage tooling.

How do I install missing dev dependencies for audit enrichment flags?

Re-run the preflight check with the install flag enabled. It prompts per package before running the correct install command for your detected package manager (npm, pnpm, yarn, or bun), and records failures verbatim in findings.json without retrying.

Does the preflight check work in a monorepo?

It refuses to run at a monorepo workspace root detected via pnpm-workspace.yaml, workspaces fields, nx.json, or turbo.json. You must point it at a specific workspace package using the target path option.

Can the preflight check modify my project in CI?

No. When a CI environment or non-writable target is detected, install and scaffolding flags are forced off. Detection and findings output still run, but no mutation occurs.

Why won't the preflight check scaffold my ESLint flat config?

Flat eslint.config.* edits are deliberately not scaffolded because they are too project-specific to automate safely. The check prints the recommended plugin snippet for you to paste manually instead.

What are the limitations of automated audit tooling setup?

It does not install global CLIs, configure external services like Snyk or Sentry, pick a bundle analyzer automatically among build-tool-specific candidates, or edit build configuration files. Those steps remain manual.