goallisted

# Goal — IncredAgents Structured Execution Two-phase protocol: every new objective is **planned** before it is **executed**. State persists across turns in SQLite. Completion is gated by a real audit against evidence. ## Phase 0 — Parse the User's Intent What did the user actually type after `/goal`? | User Input | Action | |---|---| | `/goal` (no args) | Show current goal state → **Phase 3** | | `/goal status` | Show current goal state → **Phase 3** | | `/goal pause` | Pause active goal → **Phase 3** | | `/goal resume` | Resume paused goal → **Phase 3** | | `/goal clear` | Archive current goal → **Phase 3** | | `/goal complete` | Run completion audit, then complete → **Phase 4** | | `/goal <anything else>` | Treat as new objective → **Phase 1** | ## Phase 1 — Plan (New Objectives Only) Takes the raw objective and forces it through a structured planning pass BEFORE any execution begins. This is non-negotiable. Skipping this phase is how /goal runs burn 500 turns on an unbounded task with a vibe-word DoD. ### 1.1 — Extract the Core Reduce the user's words to: - **Outcome**: what is true when this is done (one sentence, no vibe words) - **Medium**: code, content, ops, design, research, or mix - **Urgency**: is there a hard deadline or is this exploratory If the objective is missing any of these, ask ONE tight question before drafting. ### 1.2 — Draft the Structured Plan Write a plan file to `./plans/{slug}_{YYYY-MM-DD}.md` (create the folder if needed). Slug = lowerc