소스 정보
- 저장소
- benjam3n/reasoningtool
- 최근 소스 활동
- 2026년 3월 12일 17:48
- 감지된 SKILL.md 언어
- 영어
- 스타
- 9
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/benjam3n/reasoningtool --skill qg명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | qg |
| description | When you don't know something, the right question is worth more than hours of speculation. |
| output | {"format":"prose"} |
Input: $ARGUMENTS
When you don't know something, the right question is worth more than hours of speculation. This procedure provides a taxonomy of question types, each designed to resolve a specific kind of uncertainty.
Default: 2x. Parse depth from $ARGUMENTS if specified (e.g., "/qg 4x [input]").
| Depth | Min Questions Generated | Min Question Types | Min Depth Levels | Min Priority Rankings |
|---|---|---|---|---|
| 1x | 5 | 2 | 2 | 3 |
| 2x | 10 | 3 | 3 | 5 |
| 4x | 15 | 5 | 4 | 8 |
| 8x | 25 | 7 | 5 | 12 |
| 16x | 40 | 9 | 6 | 18 |
These are floors. Go deeper where insight is dense. Compress where it's not.
What don't you know? Classify the type:
| Uncertainty Type | Description | Example |
|---|---|---|
| Factual | Don't know what's true | "How many users do we have?" |
| Definitional | Don't know what something means | "What counts as 'active'?" |
| Causal | Don't know why something happens | "Why do users churn?" |
| Preferential | Don't know what someone wants | "Does the client prefer speed or quality?" |
| Conditional | Don't know what would happen if | "What if we raised prices 20%?" |
| Threshold | Don't know where the line is | "How much latency is too much?" |
| Priority | Don't know what matters most | "Which feature should we build first?" |
| Scope | Don't know what's included/excluded | "Does this apply to enterprise clients?" |
| Contradiction | Two things seem true but can't both be | "Users say they want X but behavior shows Y" |
Each uncertainty type has optimal question formats:
Factual → Direct questions:
Definitional → Boundary questions:
Causal → Mechanism questions:
Preferential → Trade-off questions:
Conditional → Scenario questions:
Threshold → Quantification questions:
Priority → Forced ranking questions:
Scope → Inclusion questions:
Contradiction → Reconciliation questions:
Before asking, improve the question:
Quality checklist:
Common question failures:
| Failure | Example | Fix |
|---|---|---|
| Too vague | "What do you think?" | Specify what dimension |
| Leading | "Don't you agree that...?" | Remove the suggested answer |
| Compound | "Do you like A and B?" | Split into two questions |
| Unanswerable | "What will happen in 5 years?" | Ask "what would need to be true for X?" |
| Unactionable | "Is the sky blue?" | Only ask if the answer changes behavior |
If multiple questions are needed:
For the input's uncertainty:
QUESTION SET:
Primary uncertainty: [type]
Questions (in order):
1. [question] — type: [type] — resolves: [what uncertainty]
2. [question] — type: [type] — resolves: [what uncertainty]
3. [question] — type: [type] — resolves: [what uncertainty]
If answer to Q1 is [A]: skip Q2, go to Q3
If answer to Q1 is [B]: ask Q2 next
After all questions answered:
- Uncertainty resolved: [what we now know]
- Remaining uncertainty: [what we still don't know]