craft-critiquelisted

# craft-critique ## Purpose Diagnose a prompt or skill — surface ambiguity, hidden assumptions, weak structure, over-specification, portability issues, and likely failure modes — and say what to do about it, in priority order. The default is read-only: findings and recommendations, no edits. Critiquing before rewriting matters because most "make this better" requests are better served by structural fixes — often by cutting — than by new wording. A short diagnostic pass exposes what's actually broken, or merely bloated, so the next edit can be surgical. ## Use this when - a prompt feels messy but the problem is unclear - a skill works sometimes but not consistently - a repo asset needs review before being generalized or shipped - a large rewrite is tempting and a critique should come first If the user also wants the fixes applied, apply them guided by the findings — smallest diff first, preserving the artifact's intent. No separate protocol is needed; the critique is the plan. (If the ask is purely "make this smaller," that's a simplify pass — same subtractive lens, no findings ceremony.) ## Inputs - the current prompt or skill - the desired outcome - any important constraints - optional examples of failure (specific outputs the artifact produced that were wrong) ## Steps 1. Identify the artifact's real job. If you can't state it in one sentence, that's already a finding. 2. Check whether each part earns its place — sections, rules, or detail that don't carry weight