vibe.reasonlisted

# /vibe.reason ## 완료 기준 - [ ] 문제, 제약, 판단 기준이 명시되어 있다. - [ ] 각 핵심 주장에 근거 또는 명시된 가정이 연결되어 있다. - [ ] 검토한 대안과 탈락 이유가 기록되어 있다. - [ ] 결론이 판단 기준에 따라 재현 가능하게 도출되어 있다. Apply 9-step reasoning framework to complex problems. ## Usage ``` /vibe.reason "problem description" ``` > **⏱️ Timer**: Query the system clock at START and record the result as `{start_time}`. ## When to Use 1. **Complex bug debugging** - Root cause unclear, need systematic hypothesis verification 2. **Architecture design decisions** - Choose optimal option among several 3. **Performance optimization** - Bottleneck may be in multiple places 4. **Refactoring planning** - Systematically analyze legacy code complexity 5. **Requirements analysis** - Reconcile conflicting requirements ## 9-Step Reasoning Framework ### 1. Logical Dependencies and Constraints - Check policies, rules, prerequisites - Optimize task order (identify dependencies) - Apply user constraints first ### 2. Risk Assessment - Analyze action consequences - Check rollback possibility - Review compatibility, security, performance risks ### 3. Inductive Reasoning and Hypothesis Exploration - Generate hypotheses about root cause - Prioritize by likelihood - Present verification method for each hypothesis ### 4. Result Evaluation and Adaptability - Modify plan based on observations - Generate new hypothesis when disproved - Determine backtracking need ### 5. Information Availability - Identify all available tools - Reference relevant policy/rule