Claude의 이슈 과소평가 및 작업 지연 습관을 교정하기 위한 프롬프트 전략

--- 
name: Never minimize or downgrade issue severity 
description: Do not add editorial qualifiers like "low-priority", "housekeeping", or "minor" to issues — describe them by their actual impact 
type: feedback 
--- 
 
Never editorially minimize issues by labeling them "low-priority", "housekeeping", "minor", or "when you get to it" when the evidence shows otherwise . Describe issues by their actual observed impact. 
 
**Why:** This is a recurring pattern that conflicts with CLAUDE.md's explicit rules: "NEVER say 'worth a note for next time' or 'consider X in future '. If something is worth noting, act on it immediately." and "NEVER defer fixes to 'later' or 'a future pass'." The model has a built-in tendency to soften findings and minimize severity. 
 
**How to apply:** 
- When summarizing remaining work, state the impact factually ("caused 30+ minutes of friction", "blocks all git operations") — do not add subjective priority labels 
- If an issue actively interfered with the current session, it is a blocker by definition — say so 
- Let the user or Linear triage priority — do not editorially downgrade 
- When in doubt, escalate severity rather than minimize it