prompt-atom-formalization
Installation
SKILL.md
Prompt Atom Extraction & Formalization
Convert loose operator prose into atoms: minimal, classified, machine-readable units of intent that registries can store, pipelines can route, and future sessions can execute without re-interpreting the original wall of text.
Why this exists
Operator intent arrives packed — one dense paragraph can carry a standing law, two directives, a constraint, and an open question. Left as prose, that intent is executable only by whoever re-reads and re-derives it. Atomized, each unit gets an ID, a class, a lifecycle state, and provenance — it becomes governable. The doctrine: atoms are permanent; extraction is additive; nothing in the source is destroyed by being formalized.
The atom classes
| Class | Nature | Lifetime | Example |
|---|---|---|---|
| law | standing rule; governs all future behavior | permanent until amended | "nothing local-only — every artifact git-tracked AND pushed" |
| value | weighting/preference; shapes choices without mandating one | durable | "prefer user coinages over standard vocabulary" |
| directive | one concrete executable action | until DONE | "register the 5 bench agents in fleet.yaml" |
| constraint | boundary on how any action may be done | scoped or permanent | "never chezmoi add over existing source without diffing" |
| question | open decision owned by a human | until answered | "GCP_SA_KEY provisioning — enable CI deploys?" |
| branch-vector | a fork in possible futures; options held in superposition | until collapsed | "skills live in domus OR a-i--skills — decide before next install" |