빠른 시작

의도에서 시작하세요. 나머지는 모두 선택입니다.

현실에 맞는 상태를 선택하세요.

seed        "아이디어는 있지만 구체적인 것은 없다"
exploring   "방향은 있지만 검증이 필요하다"
clarified   "무엇을 만들어야 하는지 정확히 안다"

프로젝트 루트에 INTENT.md를 놓으세요. 해당하는 템플릿을 채우세요.

seed 또는 exploring의 경우:

# INTENT — [Project Name]

> status: seed

## Why

Problem: [Who is suffering, and how?]
Hypothesis: [What do you think will fix it? It's OK to be wrong.]
Validation: [How will you know if the hypothesis is right?]

## What

[Leave empty if seed. Write what you want to verify if exploring.]

- [ ] [Feature 1 — one line]
- [ ] [Feature 2 — one line]

## Not

[Write whatever comes to mind. Add (?) if unsure.]

- [e.g., No mobile app for now]
- [e.g., Never send user data to third parties]

## Learnings

[Empty for now. You'll fill this as you explore.]

clarified의 경우:

# INTENT — [Project Name]

> status: clarified

## Why

Problem: [Who is suffering, and how?]
Goal: [What does success look like?]
Metric: [How do you measure it? Use numbers.]
Customer quote: [What would a happy user tell a friend? One sentence.]

## What

- [ ] [Feature 1 — one line]
- [ ] [Feature 2 — one line]
- [ ] [Feature 3 — one line]

User flow:
1. User does [A]
2. System does [B]
3. Result: [C]

Edge cases:
- [Case 1]
- [Case 2]

## Not

- Forbidden: [Hard security/ethical lines]
- Tech constraints: [e.g., no `any` types, TypeScript only]
- Out of scope: [What we're explicitly not building]
- Quality bar: [e.g., response time under 200ms]

## Learnings

- [Date] [What you tried] — [What you learned]

의도는 고정되어 있지 않습니다. 실험한 뒤 갱신하세요.

유용한 결과를 Learnings에 기록하세요:

## Learnings

- [2026-04-01] Built prototype v1 — users ignored the dashboard, went straight to export
- [2026-04-03] Interviewed 5 SMBs — the real pain is invoice tracking, not analytics
- [2026-04-05] Found existing tool X — covers 80% of what we planned. Pivot to the 20% gap.

그런 다음 Why / What / Not을 갱신하세요.

증거가 뒷받침하면 진행하세요. 그렇지 않으면 폐기하세요.

seed → exploring
  When: You start your first experiment.

exploring → clarified
  When: Why/What/Not are all filled with conviction. No (?) marks remain.

any state → killed
  When: Evidence shows this isn't worth building,
        or an existing solution covers it.
  Action: Record why in Learnings. This is valuable knowledge.

의도가 clarified 상태가 되면, INTENT.md만으로 AI에 충분한 컨텍스트가 됩니다.

Claude Code를 사용한다면, Not의 제약 조건을 CLAUDE.md로 옮기세요:

# CLAUDE.md

## Intent Constraints
- TypeScript only, no `any` types
- Never modify user data without explicit confirmation
- Response time under 200ms for all API endpoints

AI가 작업을 도출하고, 코드를 작성하고, 리뷰하고, 배포하게 하세요. 현실이 바뀌면 의도를 갱신하세요.