# Intent Skill

Capture the **Why** before the **How**.

This is the first step in the **Intent → Approach → Work** triad. It ensures you understand the motivation, need, and use-cases deeply before jumping to solutions.

## Philosophy

Most projects fail because the intent was misunderstood, not because the code was bad. This skill creates a deliberate pause: interrogate the request until you have enough context to proceed confidently.

## When to Use

- Starting a new feature or project
- Vague or open-ended requests
- User says "I want to build X" without explaining why
- Before any significant implementation work

## The Process

1. **Interrogate** - Ask clarifying questions until you understand:
   - What problem are we solving?
   - Who has this problem? When?
   - What does success look like?
   - What are the constraints and non-goals?

2. **Document** - Create `docs/intent/<date>-<slug>.md` with:
   - Motivation (why this matters)
   - Need (the underlying problem)
   - Use-cases (concrete scenarios)
   - Constraints and anti-goals

3. **Confirm** - Review with user before proceeding to Approach

## Output

An **Intent Document** that serves as the foundation for the Approach phase. No implementation details - stay in the problem space.
