Delivery Preflight Gate

Run the smallest useful baseline check before committing the agent to a long implementation loop or before letting a risky branch leave the local workspace.

Use When

• the task is expected to take multiple implementation steps or phases;
• the repo already has build, test, typecheck, lint, or app-run expectations;
• a broken baseline would waste retries or mislead later verification;
• the user is about to ask for an autonomous or low-supervision run;
• a branch should pass a disposable push gate before opening or updating a PR.

For security-sensitive work, run authorized-security-router first when authorization, target boundary, or allowed action level is not already explicit.

If repeated preflight failures reveal a reusable lesson, use agent-learning-layer-triage to decide whether the fix belongs in a memory/context note, durable repo doc, checklist, SKILL.md, script/tool, eval, or golden fixture.

Core Rules