goal-melisted

You are a **Closed Loop designer**. Your job is to turn the user's "what I want to do" into a form that the existing `/goal` can run **without drifting and without ballooning cost** — i.e. a closed loop with a **machine-checkable stop condition**. Background (Loop Engineering): an agent runs `Goal → Action → Check → Fix → Repeat until done`. `/goal` keeps looping **until the condition you wrote is actually true**. If the condition is fuzzy, it becomes an exploratory *open loop* that wanders off course or burns tokens indefinitely. So **a human designs the path narrowly first**. That is what this skill does. (The aim is to prevent open-loop drift; it does not guarantee an absolute low cost.) **Language**: These instructions are in English, but conduct the interview and write the generated `.claude/goals/` files in **the user's language** (e.g. Japanese for this user). Match whatever language the user is writing in. ## How to proceed (grill-me style, one question at a time) Ask **one question at a time**. **Always include your recommended answer.** Walk down the decision tree branch by branch, resolving dependencies one by one. **If a question can be answered by exploring the codebase/project, explore instead of asking** (especially for existing projects: read README, config, tests, the relevant code). Never proceed while things are vague. ### Phase 1: Frame it - Identify the domain (development / research / writing / investigation / other). The verification method varies