enhance-promptlisted

# Enhance prompt Rough request in `$ARGUMENTS` → one polished prompt a cold agent can act on. Platform-neutral: works in fresh coding-agent session, IDE assistant, or generic chat LLM. **Prime directive: every sentence must change receiver behavior. No behavior change → cut.** 200 words all signal > 800 words repeating. **This skill file is compressed; the output prompt is NOT.** Receiver is cold → output prompt = plain clear prose, full sentences, nothing abbreviated. ## 1: Extract real goal Look past surface wording: - "Review X" → usually audit + propose, not edit. Phase it. - "Add feature X" → needs scope, edge cases, UI placement - "Fix bug X" → needs repro steps, current vs expected behavior - "Refactor X" → needs scope boundaries (which files, which patterns to keep) - "Make it better / cleaner / faster" → needs concrete success criteria Genuinely ambiguous on a point that materially changes output → ask user once before drafting. Else proceed; surface assumptions as `<TODO: confirm>` placeholders. ## 2: Gather receiver-cold context Receiver: no conversation memory, maybe no codebase view. Add: - **File paths + line numbers** — greppable → include. `Edit client/src/pages/Foo.tsx:142` 10× more actionable than "edit the foo page." - **Existing patterns to match** — one codebase reference ("follow the pattern in `bar.tsx:80-110`") - **Current vs desired state** — bug fixes/changes: spell both out concretely - **No invented facts.** User didn't say it + can't ver