Plan

Design a feature or behavior change through dialogue. The plan emerges from the conversation, not in isolation.

If an issue number is given, fetch it with gh issue view $ARGUMENTS and use it as the starting point.

Have a design conversation about this task. Read the relevant code, share what you find, say what you think, and let the user shape the direction. The plan emerges from the dialogue — do not build it in isolation.

If a question can be answered by reading the code, read the code instead of asking.

Ground every recommendation in current code, docs, and project rules.

Task sizing

• Small (1-2 files): single endpoint, component, or utility
• Medium (3-5 files): one feature slice through the stack
• Large (5-8 files): multi-component feature — consider splitting

Anything larger needs further decomposition. Slice vertically (complete paths through the stack), not horizontally (all types, then all implementations, then all tests).