asis-tobe-decisionlisted

# ASIS→TOBE Decision Presentation A presentation **format**, not a heavy process. It fires at the moment you would otherwise ask "should I do this?" or "A or B?" and turns that question into a one-screen artifact the user can approve, question, or push back on in a single pass. This codifies the user's standing rule in `.claude/CLAUDE.md`: > **의사결정 및 컨펌 요청 시** > 1. 이해가 쉽도록 전후 맥락과 함께 상세하게 설명 > 2. 추천하는 제안과 그 이유를 설명 > 3. UI/UX 형태로 이해할 수 있도록 설명 > 4. ASIS TOBE 형태로 설명 The rule exists but does not reliably self-trigger — the user has had to demand it mid-task ("구체적으로 화면으로 ASIS TOBE로 설명", "다음 진행할 것들 ASIS-TOBE로 알려줘"). This skill makes it an **active default** so the user never has to ask. ## When to use Fire whenever you are about to: - ask for approval before doing something ("이거 이렇게 진행할까요?") - offer the user a choice between two or more approaches - propose a change to architecture, config, scope, or plan - recommend one option over others Softer/secondary trigger: reporting "next steps" the user must sign off on ("다음 진행할 것들"). Use judgment — render it in this format when a real yes/no is needed. Do **not** fire for pure information with no decision in it, or for trivial reversible actions you'd just do. This is for moments where a human "yes / no / which one" is genuinely needed. ## The four slots (= the four CLAUDE.md items) The four slots map 1:1 to the user's rule. Cover all four, but **lead with the recommendation** — readers decide off the conclusion, so put it up t