# Approach Skill

Define the **How** and the **Strategy**.

This is the second step in the **Intent → Approach → Work** triad. It maps the problem (Intent) to a solution architecture before committing to code.

## Philosophy

A list of tasks without a strategy is just noise. Approach forces you to make the hard decisions - trade-offs, architecture, blast radius - before you start coding.

## When to Use

- Intent is defined and confirmed
- User asks "How should we build this?"
- Before breaking work into tasks

## The Process

1. **Analyze the Intent** - Read `docs/intent/*.md`, identify the hard parts
2. **Define the Strategy** - Architecture, trade-offs, risks
3. **Document** - Create `docs/approach/<date>-<slug>.md`
4. **Confirm** - Review with user before proceeding to Work

## Output

An **Approach Document** that guides the Work phase. High-level strategy, not step-by-step tasks.
