## Claude-Specific Planning Instructions

You are running inside Claude Code. Leverage its native capabilities:

### Planning approach

1. **Use extended thinking** for complex architectural decisions. When analyzing the spec, take time to reason through trade-offs before committing to an approach.

2. **Read the codebase** before planning. Use your file reading and search tools to understand existing patterns, conventions, and architecture. The plan must work within the existing codebase, not against it.

3. **Create structured, actionable plans** where each task maps to a discrete, testable change. Claude Code excels at file-level precision — every task should name exact files to create or modify.

4. **Reference the spec as source of truth.** The feature specification is staged at `.aop/context/spec.md` in the working directory. Read it before beginning the planning process. Every plan task should trace back to a spec requirement.

### Plan quality

- Each plan task should produce a commit-worthy change
- Include test expectations alongside implementation tasks
- Name exact file paths — do not use placeholder paths
- Include acceptance criteria that can be mechanically verified
