What problem does it solve?
Helps you avoid solving the wrong problem, using the wrong method, or claiming completion without the proof needed to support it.
Core Features & Use Cases
- Distinguishes the user’s real outcome from a merely prescribed action or proxy metric.
- Detects when a requested route is weak, contradictory, underpowered, ambiguous, or blocked by authorization.
- Separates component evidence from whole-outcome proof so you do not overclaim on partial results.
- Keeps reversible drafting separate from irreversible sending, deleting, renaming, or other external actions.
- Example use cases include deciding whether to follow a requested workflow, ask one gating question, hold for approval, or hand off to a downstream skill.
Quick Start
Use the starting-point skill to evaluate the user’s goal, identify the proof threshold, and choose the safest valid next step.