← ClaudeAtlas

preflightlisted

Prove every env var, secret, and service the run will need is present and reachable BEFORE starting an unattended or overnight run. Use at the planning stage — after decompose, before /feature-implement — so the run never stalls at 3am on a missing variable or dead endpoint.
austinmao/feature-fix-swarm · ★ 3 · AI & Automation · score 72
Install: claude install-skill austinmao/feature-fix-swarm
# /preflight ## Host dispatch contract - Codex: `$skill`, Codex collaboration roles, and GPT-5.6 tiers. - Claude: `/skill`, Agent/Skill tools, and Claude aliases. - A bare `/skill` in this shared source denotes the Claude form; Codex dispatches the same named skill as `$skill`. ## Init gate Before any other step, run the advisory init guard and relay its output verbatim: ```bash bash "$(git rev-parse --show-toplevel)/scripts/gsd/init-guard.sh" || true ``` If it printed `INIT-GUARD:` warnings, offer `/ffs-init` before proceeding in interactive sessions (declining proceeds anyway); headless, spawned, and autonomous runs relay the warnings once and continue. Advisory only — never a block, never an exit-code change. At entry, make one opportunistic, fail-soft `bash scripts/gsd/reconcile.sh` pass; never block on its result. An unattended run that stops on a missing env var wasted the whole night. Requirements are proven at plan time — while the operator is still present — never discovered at run time. ## When to run - Before any `--auto` / `--autonomous` `/feature-implement` run. - Before an overnight or operator-absent run of any kind. - After decompose, when the task list makes the runtime footprint knowable. ## Procedure 1. **Author the manifest** — `specs/NNN/preflight.json`. Enumerate what the RUN will touch, not what the repo could touch: - every env var / secret name the tasks read (`process.env.*`, `os.environ`, `doppler secrets get` names) — scan th