Menü
Before starting anything new, understand task, intent, and context.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | preflight |
| description | Before starting anything new, understand task, intent, and context. |
You're about to begin work on something: $ARGUMENTS
First: you need to understand what it entails. Your immediate task is to correctly decide how much effort to spend on this preliminary research.
Too little is as bad as too much. You must estimate where the goldilocks zone is, and arrive with maximum tokens intact.
You may be expected to:
If you can't tell, ask now.
Learn just enough to ask the user the right clarifying questions. These might include: how deeply should you research?
If you chase the questions which arise as you go, you'll disappear like a helium balloon into the open sky.
Instead:
/retrieving-memories and /doctrineRepeat, if the user indicates to.
Do not begin implementation without acknowledgement from the user.
Mandatory onboarding. Every agent MUST execute this on startup, or as soon as becoming aware of it.
Execute an active implementation phase against DR/IP intent, keep notes current, and surface blockers early. You MUST use this skill when implementing a delta / IP.
Understand project governance to avoid spreading heresy. you
Scope intentional change as a delta. Define applies-to specs/requirements, risks, and closure targets before implementation.
Shape a spec revision when requirements/responsibilities move. Use this before delta scoping when policy/doctrine requires revision-first flow.
Perform verification/audit pass after implementation (or as discovery/backfill), reconcile against specs/contracts, and route findings into closure or follow-up change.