FAILURE CONDITIONS
A required final section in Orbit prompts listing specific, verifiable, binary criteria that constitute prompt failure. Catches incomplete or wrong implementations.
What it is
Every Orbit prompt ends with a FAILURE CONDITIONS section listing specific things that mean "this prompt didn't actually ship correctly." They're binary (did X happen, yes or no), specific, and verifiable. They catch the case where an agent claims success but skipped or partially-implemented work.
When you would use it
You write FAILURE CONDITIONS into every prompt you queue. Prompt review verifies they're present and adequate.
Common operations
- Ensuring agent self-verification on completion
- Catching skip behavior post-execution
- Building test criteria into the prompt itself
Related terms
Where this is taught
No learning path uses this term yet. Browse the Learning Atlas for guided sequences through related ideas.