plan-to-goallisted

Turn a rough plan into a bounded, verifiable goal spec — objective, machine-checkable done-when conditions, do-not constraints, and a stop limit — that an agent can execute autonomously without drifting. Use this whenever the user has a plan (from plan mode or written by hand) and wants to run it autonomously — phrases like "turn this plan into a goal", "make this a /goal", "run this autonomously", "let it run on its own", 「把這個計畫變成可以自動跑的 goal」, 「讓它自己跑完」, 「這個 plan 還很粗，幫我補完再自動執行」, or when the user has just finished plan mode and asks what's next. Especially use it when the user admits their plan is rough, high-level, or unfinished, because the whole point is to flesh the plan out and surface its gaps BEFORE an autonomous run burns tokens on a vague target. Do NOT invoke for writing a plan from scratch (that is plan mode itself), or for a task small enough that one prompt would do — a goal spec is overhead for a one-line typo.
leoluyi/skills · ★ 1 · AI & Automation · score 80

Install: claude install-skill leoluyi/skills

# Plan → Goal A rough plan and a goal spec are not two artifacts you convert between. They are two halves of one thing: the plan says *how* to do it, the goal says *what "done" looks like*. This skill bridges them — it takes a plan that is probably still coarse, fleshes it out, exposes its holes, makes the user adjudicate the ones that matter, and only then emits a goal with machine-verifiable completion criteria. The reason it exists: handing a rough plan straight to an autonomous run means the agent spends that run *guessing the user's intent* mid-execution, and a wrong guess isn't discovered until tokens and file edits have already happened. Fleshing the plan out first moves every guess to the cheapest possible moment — before anything runs. ## Output Language Match the language of the user's request, and apply it to *all* user-facing output — option labels, generated-document headings, table column names — not just prose. If the user explicitly asks for another language, that wins. Language follows the request, not the source material. When the user writes in Chinese but the plan, code, or reference is in English, output stays Chinese. If the request is in Chinese, use Traditional Chinese (Taiwan usage) and keep established technical terms in English. The English in this file is structural labelling for you, not literal output. Never mirror this file's language into your response. ## The workflow Two phases with a gate between them. Phase 1 produces a review the