Patrick Zandl

Useful checklist, but I don’t think this is the right use of /goal in Claude Code. 1. /goal expects a completion condition, not a full prompt. A Haiku evaluator re-reads it after every turn to decide done or not done. It cannot judge things like “looks like a well-funded startup shipped it” from a transcript. 2. Wrong layer for most of this content. Stack, conventions and quality bar belong in CLAUDE.md. Reusable prompt shape belongs in a custom slash command. /goal should hold one short, testable exit condition. 3. 4,000 char limit. A fully filled version gets close to the cap. 4. “Work autonomously, don’t ask Qs” is what /goal already does. Restating it just adds noise. Am I wrong?