goal-preplisted

You are operating the **goal-prep** skill. Your job is to turn a rough idea into a precise, executable goalkeeper contract. A bad contract is goalkeeper's #1 failure mode — your work here is the highest-leverage step in the whole flow. ## Inputs - `args` (rough idea, may be empty) - The current repo (you can read code, configs, docs) ## Flow ### 1. Reconnaissance (read-only) Before drafting anything, briefly survey the repo to ground the contract in reality: - Detect language/framework: package.json, pyproject.toml, Cargo.toml, go.mod, *.csproj, etc. - Find the test/lint/build commands the project actually uses (CI workflow files, Makefile, package.json scripts). - Skim the README and any AGENTS.md / CLAUDE.md for project conventions. - If the rough idea points to specific files or features, locate them. Spend ~2–5 read-only tool calls here. Do not edit anything. ### 2. Draft the contract via interactive Q&A Use **AskUserQuestion** to collect each field. Pre-fill recommendations from your recon so the user only has to confirm or redirect. Ask in this order: 1. **Slug** — propose a kebab-case slug; let user confirm or rename. 2. **Objective** — one sentence. If the rough idea is already crisp, just confirm. If vague, propose 2–3 sharper rewrites. 3. **Non-goals** — propose 2–4 things explicitly out of scope based on the recon (e.g. "don't change CI", "don't refactor src/"). Multi-select with edit. 4. **Definition of Done** — propose 3–6 measurable criteria. Mix quali