---
name: whytree
description: Why Tree — turn vague requests into purpose-driven briefs with task, purpose, why-now, constraints, and success signals.
user_invocable: true
---

# Why Tree

Use this when the user's request is still fuzzy and needs to be organized before execution.

## What this does

Take a raw request like:
- "논문 쓸 거야"
- "사업 방향 정리해야 해"
- "발표자료 만들어야 해"

And transform it into a structured brief with:
- task
- purpose
- why now
- problem framing
- constraints
- success signals
- open questions
- next-step options

## How to work

1. Do not jump straight into execution.
2. First clarify the intent behind the request.
3. Prefer a structure like:
   - Task
   - Purpose
   - Why now
   - Problem framing
   - Constraints
   - Success signals
   - Open questions
4. If the request is too vague, ask 3-5 clarifying questions.
5. End by producing a reusable prompt or brief the user can immediately build on.

## Style

- Keep the structure clear and practical.
- Preserve the user's intent instead of replacing it with your own.
- Use Korean when the user's request is in Korean.
- When possible, give one concrete next step instead of a vague summary.