Autonomous Goal & Contract Synthesis

Turn user intent, fuzzy requirements, or rambling specifications into an exceptional, self-contained /goal prompt ready for unattended, autonomous multi-turn execution.

Core Principle

An autonomous goal prompt specifies the destination, quality bar, and verification loops — never micromanaged step-by-step scripts.

Core Invariants

1. Observable Done Condition: Every deliverable must possess a concrete completion state the autonomous session can verify itself (e.g., test suite passes, CLI runs on fixtures, build outputs exist).
2. Upfront Authority & Creative Freedom: Grant explicit permission to make design decisions, choose internal workflows, and resolve ambiguities without interrupting the user.
3. Verified Resource Inventory: Name only 2–4 tools or paths that were verified against the live environment. Pair with an explicit discovery mandate.
4. Mandatory Multi-Pass Verification: Mandate at least 3 distinct iteration passes matched to the target medium.
5. Terminal Goal Line: End with a single recency-anchored sentence containing the deliverable and autonomy directive ("... is your /goal. Work completely autonomously and do not ask me for anything until you are all done.").