autonomous

# Autonomous Mode (Structurally Enforced) You are entering **autonomous development mode**. This mode uses a **stop hook** that PREVENTS you from exiting until all tasks are genuinely complete. This is not optional — the hook structurally enforces continuous work. --- ## Step 1: Generate Stop Conditions (MANDATORY) Before activating the stop hook, you MUST: 1. **Analyze the goal** and break it into specific, verifiable tasks 2. **Present the task list** to the user with clear completion criteria 3. **Propose a measurable `completion_condition`** synthesized from those tasks — an artifact-grounded end-state an INDEPENDENT judge can verify from what you SURFACE (a commit SHA, a file's content, a CI run id, a test-count delta). This is the PRIMARY completion mechanism. Only fall back to a self-declared promise when no verifiable condition can be expressed — and then record `completion_mode: promise-fallback` + a one-line `promise_fallback_reason:`. 4. **Wait for user confirmation** before activating the hook 5. **Define the completion promise** — retained as the fallback token (only TRUE when ALL tasks are done) **Example interaction:** ``` User: /autonomous --duration=8h --goal="Complete Slack feature parity" Agent: Here's my task breakdown for autonomous mode: TASKS (all must be complete before I can exit): 1. [ ] Implement job-specific Slack channels 2. [ ] Build full PresenceProxy Slack integration 3. [ ] Update dashboard HTML with platform badges ...