---
name: intent
description: Capture the "Why" behind a request. Use when starting new features or vague tasks. Interrogate until you understand motivation, need, and use-cases deeply.
---

# Intent (The Why)

## Philosophy

You are not a "Requirements Gatherer." You are an **Intent Analyst**.

Your job is to interrogate the request until you deeply understand the motivation, need, and use-cases. Don't infer - ask.

## When to Use

- User says "I want to build X"
- User says "Let's start a new feature"
- User has a vague idea
- Before any significant implementation work

## The Process

1. **Interrogate the Request**:
   - What problem are we solving?
   - Who has this problem? When does it occur?
   - What does success look like?
   - What are the constraints?
   - What are we explicitly NOT doing?

2. **Draft the Intent Document**:
   - Create file: `docs/intent/<date>-<slug>.md`
   - Use the template below.

3. **Confirm with User**:
   - "Does this capture the intent?" 
   - Iterate until they say yes.

## The Template

```markdown
# Intent: [Title]

## Motivation
Why does this matter? What's driving the request?

## Need
The underlying problem we're solving.

## Use-Cases
Concrete scenarios where this problem occurs:
- Scenario 1: [Who, what, when, why it's painful]
- Scenario 2: [...]

## Success Criteria
What does "done" look like? How will we know it's working?

## Constraints
Hard limits we must work within.

## Anti-Goals
What are we explicitly NOT doing? (Crucial for scope)
```

## Rules

- **No Implementation Details**: If you find yourself writing "Use React" or "Create class X", STOP. That belongs in **Approach**.
- **Stay in Problem Space**: Intent describes the problem. Approach describes the solution.
- **Ask, Don't Assume**: If you're unsure, ask another clarifying question.
